mohamadhalabi.com valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot / ✔
BingBot / ✔
BaiduSpider / ✔
YandexBot / ✔ 
# If you are regularly crawling WordPress.com sites, please use our firehose to receive real-time push updates instead. # Please see https://developer.wordpress.com/docs/firehose/ for more details. Sitemap: https://mohamadhalabi.com/sitemap.xml Sitemap: https://mohamadhalabi.com/news-sitemap.xml User-agent: * Disallow: /wp-admin/ Allow: /wp-admin/admin-ajax.php Disallow: /wp-login.php Disallow: /wp-signup.php Disallow: /press-this.php Disallow: /remote-login.php Disallow: /activate/ Disallow: /cgi-bin/ Disallow: /mshots/v1/ Disallow: /next/ Disallow: /public.api/ # This file was generated on Wed, 01 Feb 2023 08:29:17
Meta Tags
Title mohamad halabi’s blog | My thoughts on Enterprise Solution Architecture and
Description My thoughts on Enterprise Solution Architecture and
Keywords N/A
Server Information
WebSite mohamadhalabi faviconmohamadhalabi.com
Host IP 192.0.78.25
Location United States
Related Websites
Site Rank
More to Explore
mohamadhalabi.com Valuation
US$513,019
Last updated: 2023-05-16 20:38:11

mohamadhalabi.com has Semrush global rank of 20,631,428. mohamadhalabi.com has an estimated worth of US$ 513,019, based on its estimated Ads revenue. mohamadhalabi.com receives approximately 59,195 unique visitors each day. Its web server is located in United States, with IP address 192.0.78.25. According to SiteAdvisor, mohamadhalabi.com is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$513,019
Daily Ads Revenue US$474
Monthly Ads Revenue US$14,207
Yearly Ads Revenue US$170,480
Daily Unique Visitors 3,947
Note: All traffic and earnings values are estimates.
DNS Records
Host Type TTL Data
mohamadhalabi.com. A 299 IP: 192.0.78.25
mohamadhalabi.com. A 299 IP: 192.0.78.24
mohamadhalabi.com. NS 86400 NS Record: ns2.wordpress.com.
mohamadhalabi.com. NS 86400 NS Record: ns3.wordpress.com.
mohamadhalabi.com. NS 86400 NS Record: ns1.wordpress.com.
mohamadhalabi.com. MX 3600 MX Record: 32767 ms16982012.msv1.invalid.
HtmlToTextCheckTime:2023-05-16 20:38:11
mohamad halabi’s blog My thoughts on Enterprise Solution Architecture and more… Menu Home About Contact Me Azure App Service Introduction Series – Securing Web API with Azure AD Leave a reply In this post I will extend the previous example, by making the web application call a web api secured using Azure AD. Now let me clarify this: the user will use OpenID Connect to authenticate to the web application, exactly as we saw in the previous post – in fact I’m reusing the same exact sample. However, the web application at some point needs to call a web api which itself is protected using Azure AD and OAuth2. In this case the web application is the client and it will ask Azure AD for an access token to access the web api (using the OAuth2 Client Credential Flow); and this access token has nothing to do with the id token which was issued to the user to log in to the web application. Here is a simplified conceptual illustration showing the main artifacts (not showing the protocol dance):
Ads.txtCheckTime:2023-05-16 20:38:11
#Rev - 20230503 OwnerDomain=pubmine.com #WordPress pubmine.com, 3, DIRECT #WordPress - AppNexus appnexus.com, 7766, DIRECT #WordPress - Pubmatic pubmatic.com, 156204, DIRECT, 5d62403b186f2ace #WordPress - Verizon Display adtech.com, 9534, DIRECT, e1a5b5b6e3255540 adtech.com, 12089, DIRECT coxmt.com, 2000067907202, RESELLER pubmatic.com, 156078, RESELLER, 5d62403b186f2ace openx.com, 537143344, RESELLER, 6a698e2ec38604c6 #WordPress - Oath One Mobile aol.com, 47425, DIRECT pubmatic.com, 156138, RESELLER coxmt.com, 2000067997102, RESELLER indexexchange.com, 184110, RESELLER, 50b1c356f2c5c8fc yahoo.com, 47425, DIRECT, e1a5b5b6e3255540 yahoo.com, 57079, DIRECT, e1a5b5b6e3255540 #WordPress - Amazon aps.amazon.com,6fb17607-32fb-47ed-b920-df44722f6475,DIRECT pubmatic.com,160006,RESELLER,5d62403b186f2ace pubmatic.com,160096,RESELLER,5d62403b186f2ace rubiconproject.com,18020,RESELLER,0bfd66d529a55807 pubmatic.com,157150,RESELLER,5d62403b186f2ace openx.com,540191398,RESELLER,6a698e2ec38604c6
HTTP Headers
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sat, 12 Feb 2022 10:00:08 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://mohamadhalabi.com/
X-ac: 3.arn _dca 

HTTP/2 200 
server: nginx
date: Sat, 12 Feb 2022 10:00:09 GMT
content-type: text/html; charset=UTF-8
strict-transport-security: max-age=31536000
vary: Accept-Encoding
vary: Cookie
x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
host-header: WordPress.com
link: ; rel=shortlink
x-ac: 3.arn _dca
mohamadhalabi.com Whois Information
Domain Name: MOHAMADHALABI.COM
Registry Domain ID: 1853092507_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.wildwestdomains.com
Registrar URL: http://www.wildwestdomains.com
Updated Date: 2021-03-03T02:35:45Z
Creation Date: 2014-04-02T18:14:00Z
Registry Expiry Date: 2022-04-02T18:14:00Z
Registrar: Wild West Domains, LLC
Registrar IANA ID: 440
Registrar Abuse Contact Email: abuse@wildwestdomains.com
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.WORDPRESS.COM
Name Server: NS2.WORDPRESS.COM
DNSSEC: unsigned
>>> Last update of whois database: 2022-02-12T07:29:21Z <<<

Copyright © 2022 WebZZ.US 0.0206