Skip to content
https://hotmail.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
2 redirect(s), 341 ms total
REVIEW
2 redirect(s), 341 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://outlook.live.com/owa/
Info::
Cross-domain redirect detected

https://hotmail.com

89 ms · HTTP/1.1

301

https://outlook.live.com/owa/

159 ms · HTTP/1.1

302

https://outlook.live.com/mail/

93 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hotmail.com30189 msHTTP/1.1
2https://outlook.live.com/owa/302159 msHTTP/1.1Microsoft-HTTPAPI/2.0
3https://outlook.live.com/mail/20093 msHTTP/1.1Microsoft-HTTPAPI/2.0

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 10240 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 10240 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!DOCTYPE html> <html dir=ltr xmlns=http://www.w3.org/1999/xhtml translate=no> <head> <meta charset=utf-8> <meta http-equiv=X-UA-Compatible content="IE=edge"> <meta http-equiv=pragma content=no-cache> <meta name=viewport content="width=device-width,initial-scale=1,user-scalable=0"> <meta name=google value=notranslate> <meta name=format-detection content="telephone=no"> <meta name=scriptVer content=20260410002.41> <meta name=hashedPath content=hashed-v1> <meta name=physicalRing content=WW> <meta name=environment content=Prod> <meta name=bootFlights content=auth-cacheTokenForMetaOsHub,auth-useAuthTokenClaimsForMetaOsHub,auth-codeChallenge,auth-msaljs-eventify,cal-store-NavBarData,auth-msaljs-newsletters,auth-msaljs-meet,auth-msaljs-places,auth-msaljs-bookings,auth-msaljs-findtime,auth-msaljs-landingpage,auth-msaljs-business,auth-msaljs-consumer,pe1416235c1,pe1444542c1,pe14456012,pr1539892c19,pr16347118,pr1759826c7,pr17636248,auth-naa-bookings,auth-unifiedCache,cal-reload-pause,workerAsyncLoad,auth-disableAnonymousTokenForHeader,msplaces-hosted-localsessiondata-v2,fwk-enable-default-trusted-types-policy,msplaces-app-boot-sequence,auth-msaljs-hostedplaces,fwk-enable-owa-loop-trusted-types-policy,fwk-init-acc-locstore,auth-msaljs-domainHint,auth-tokenCache-expiryDate,auth-mon-removeFallbackToGATFR,auth-hosted-removeFallbackToGATFR,cal-appCaching-ReloadOnError,auth-msaljs-consumer-boot-errorhandler,fwk-enforce-trusted-types,cal-enable-scheduling-poll,acct-icloudOAuthOobe,auth-mlp-redirect,nh-enableOutlookMigrationInteropRefactor,nh-enableDiagnosticsInteropRefactor> <meta name=cdnUrl content=//res.public.onecdn.static.microsoft/> <meta name=backupCdnUrl content=//res-1.cdn.office.net/> <meta name=cdnContainer content=owamail/> <meta name=devCdnUrl content=> <meta name=ariaUrl content=> <meta name=allowedTrustedTypesUrls content=https://*.public.onecdn.static.microsoft,https://*.cdn.office.net,https://content.lifecycle.office.net/dime/v1,https://ad.doubleclick.net/ddm/trackimpj> <meta name=webServerForest content=frap264> <meta name=webServerClique content=CLFRAP264MRS00> <meta name=wcssFrameUrls content={'DefaultUrl':'https://webshell.suite.office.com','WwdbUrl':'https://wwdb.webshell.suite.office.com','EudbUrl':'https://eudb.webshell.suite.office.com'}> <meta name=scriptPath content=scripts/> <meta name=owaIsAuthenticated content={{IsAuthenticated}}> <meta name=jsTimestamp content=1776814808260> <meta name=publicUrl content=https://outlook.office.com> <meta name=aadAuthorityUrl content=https://login.microsoftonline.com/> <meta name=businessCanonicalHostName content=outlook.office365.com> <meta name=isRPSAuthCookiePresent content=False> <meta name=mlpUrl content=https://www.microsoft.com/{0}/microsoft-365/outlook/email-and-calendar-software-microsoft-outlook?deeplink={1}&sdf={2}> <meta name=robots content=noindex> <meta name=isServerLocal content=False> <link rel=preconnect href=//res.public.onecdn.static.microsoft/ crossorigin=anonymous> <link rel=preconnect href=https://login.microsoftonline.com/ crossorigin=anonymous> <link rel="shortcut icon" href=/mail/favicon.ico type=image/x-icon> <link rel=apple-touch-icon href=//res.public.onecdn.static.microsoft/assets/mail/pwa/v4/pngs/apple-touch-icon.png crossorigin=anonymous> <noscript>JavaScript must be enabled.</noscript> <title>Outlook</title><link integrity="sha256-l7trx2j9hqF8WAshYvxr6tWOEAEH95sGGv0EsyQ4Txk=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mail.runtime.76677946.js" as="script" crossorigin="anonymous"/><link integrity="sha256-9FUvvpd75HPlA+f6z9Ay1UhJ5nv54L8Xp11YEBaWffU=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.7cad6afb.js" as="script" crossorigin="anonymous"/> <style>@font-face{font-family:FabricMDL2Icons;src:url('//res.public.onecdn.static.microsoft/owamail/20260410002.41/resources/fonts/o365icons-mdl2.woff') format('woff');font-weight:400;font-style:normal}@font-face{font-family:office365icons;src:url('//res.public.onecdn.static.microsoft/owamail/20260410002.41/resources/fonts/office365icons.woff?') format('woff');font-weight:400;font-style:normal}#loadingScreen{position:fixed;top:0;bottom:0;left:0;right:0;background-color:#fff}#loadingLogo{position:fixed;top:calc(50vh - 200px);left:calc(50vw - 200px);width:400px;height:400px}#MSLogo{position:fixed;bottom:36px;left:calc(50vw - 50px)}.dark #loadingScreen{background-color:#333}.darkNew #loadingScreen{background-color:#1f1f1f}</style> <script nonce=84yvzsmi6SCdJe00NbJuDA==>try{!function(){if("localStorage"in window){var e="UsersNormalizedTheme",t=window.localStorage,a=t.getItem("olk-"+e)||t.getItem(e);a&&/\.dark$/.test(a)&&document.documentElement.classList.add("dark"),a&&/\.dark\.new$/.test(a)&&document.documentElement.classList.add("darkNew");var n=t.getItem("PwaTheme");if(n){var o=document.getElementsByName("theme-color");o&&o.length&&o[0].setAttribute("content",n)}}}()}catch(e){}</script> <script nonce=84yvzsmi6SCdJe00NbJuDA==>function logError(o,n,r,e,a,s){window.owaErrorHandler?window.owaErrorHandler(o,n,r,e,a,s):window.owaBackfilledErrors.push(arguments)}function hashChangeHandler(){window.owaLocationHash=window.location?window.location.hash:void 0}function storePromptValue(){try{const o=new URLSearchParams(window.location.search);window.owaLocationSearchPrompt=o.get("prompt")}catch(o){}}window.FabricConfig={fontBaseUrl:"//res.public.onecdn.static.microsoft/assets/mail/fonts/v1",iconBaseUrl:"//res.public.onecdn.static.microsoft/assets/mail/fonts/v1/fonts/"},window.owaBackfilledErrors=[],window.onerror=logError,"onunhandledrejection"in window&&window.addEventListener("unhandledrejection",(function(o){var n=o&&o.reason||"[no reason given]";n instanceof Error?logError("Unhandled Rejection: "+n,"",0,0,n):n.responseErrorMessage&&n.callstackAtRequest&&n instanceof Response?logError(n.responseErrorMessage,"",void 0,void 0,void 0,n.callstackAtRequest):logError("Unhandled Rejection: "+("string"==typeof n?n:JSON.stringify(n)))})),window.onload=function(){var o=self.location;!self.Owa&&o&&void 0!==o.search&&-1==o.search.indexOf("gulp")&&-1==o.search.indexOf("branch")&&(-1==o.search.indexOf("bO=2")?o.search+=(o.search?"&":"?")+"bO=2":o.assign("/mail/olkerror.html?bret=fail&esrc=NoBootJs&app=Mail&bO=2"))},hashChangeHandler(),storePromptValue(),window.addEventListener("hashchange",hashChangeHandler)</script> <link integrity="sha256-1LT5Ri90zAVvAkDjuF9Vv+KKMgALxMEBOMJHbry1CZ0=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.shared.m.6963c5b9.css" as="style" crossorigin="anonymous"/><link integrity="sha256-OytGT6ny9BrkM/rbiJnoOL0ctKIzHSYDMDpfdrYD2Uc=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mail.m.d4755464.css" as="style" crossorigin="anonymous"/><link integrity="sha256-e6f/cQfQDvLN5FIMJNhg1Cq14oFr4I1Cnr+AfJ5PTuk=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.styles.m.d9131b0e.css" as="style" crossorigin="anonymous"/><link integrity="sha256-qJ0bqwWhC9h0UPNE+DQ6i/LO+Hw1C2S4V5VLDFm7N1Q=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.77555.m.5d03aec6.js" as="script" crossorigin="anonymous"/><link integrity="sha256-pZ0S5BzBqZrEKcgHHEfBBML6V4qZDb5DbwS17NC9oX8=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.26778.m.55d59f88.js" as="script" crossorigin="anonymous"/><link integrity="sha256-TvlshqPk5TxHhBN+v8NvXA2l+a/STFU6z+pAiutCt8U=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.AppBoot.m.5068bf7e.js" as="script" crossorigin="anonymous"/><link integrity="sha256-CkzNfejJ0wBDADhTgjKFtDRPJi59EIhlpMShZvf4nTg=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.57554.m.f3ec0b78.js" as="script" crossorigin="anonymous"/><link integrity="sha256-neItqPcTZvGa6zyG5hchwAOGIElIvcQiG44LAj746m0=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.71719.m.123fad49.js" as="script" crossorigin="anonymous"/><link integrity="sha256-694YdOUYtRspSd07CNxEgdD37lYGAUv8md3jZ032+dw=" rel="preload" href="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.MsalAuth.m.78480eba.js" as="script" crossorigin="anonymous"/><script integrity="sha256-l7trx2j9hqF8WAshYvxr6tWOEAEH95sGGv0EsyQ4Txk=" src="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mail.runtime.76677946.js" crossorigin="anonymous" defer></script><script integrity="sha256-9FUvvpd75HPlA+f6z9Ay1UhJ5nv54L8Xp11YEBaWffU=" src="//res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.7cad6afb.js" crossorigin="anonymous" defer></script></head> <body role=application class="ms-font-s disableTextSelection ms-Fabric--isFocusHidden"> <div id=app></div> <div id=loadingScreen> <div id=loadingLogo dir=ltr> <style>@keyframes pinchAndRelease{0%,100%,12.5%,25%,35.5%,50%{transform:scale(1,1) translateY(0)}30%,5%{transform:scale(.86,1.1) translateY(-10px)}}@keyframes documentOneScale{0%,100%,35%,50%{transform:translate(61px,82px) scale(0,0) rotateZ(20deg) rotateY(26deg)}12%,22%{transform:translate(0,0) scale(1,1) rotateZ(-18deg) rotateY(0)}}@keyframes documentTwoScale{0%,100%,33%,50%{transform:translate(44px,68px) scale(0,0) rotateZ(20deg) rotateY(26deg)}15%,19%{transform:translate(0,0) scale(1,1) rotateZ(-9deg) rotateY(0)}}@keyframes layersSlideIn{0%,23%{transform:translateY(74px) scale(0) rotateX(50deg) rotateZ(45deg)}100%,33%{transform:translateY(0) scale(1) rotateX(50deg) rotateZ(45deg)}}#container{width:400px;height:400px;display:flex;justify-content:center;align-items:center;position:relative;--duration:3000ms;--delay:0ms;--iterationCount:infinite;--direction:normal;--fillMode:forwards;--playState:running;--easing:ease-in-out}.foreground{width:164px;height:200px;border-radius:26px;overflow:hidden;position:absolute;z-index:100;animation:pinchAndRelease var(--duration) var(--easing) var(--delay) var(--iterationCount) var(--direction) var(--fillMode) var(--playState)}.background{width:164px;height:200px;border-radius:26px;overflow:hidden;position:relative;z-index:20;animatio
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
311 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

311
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 27 ms lookup
PASS
1 A records, 27 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 204.79.197.212
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3-205.azure-dns.org, ns4-205.azure-dns.info, ns1-205.azure-dns.com, ns2-205.azure-dns.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 27 ms
Got: 27 ms
A204.79.197.212
AAAA
CNAME
NSns3-205.azure-dns.org, ns4-205.azure-dns.info, ns1-205.azure-dns.com, ns2-205.azure-dns.net
MX
2 hotmail-com.olc.protection.outlook.com
TXT
google-site-verification=gqFmgDKSUd3XGU_AzWWdojRHtW3_66W_PC3oFvQVZEw
google-site-verification=VdfSHp3aOmiGxd6jcbkRPFy6EERzln_hMR3byLjU__w
SPF v=spf1 include:spf2.outlook.com -all
CAALookup not available with standard resolver
Resolved in 27 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.hotmail.com/
200https://hotmail.com/

Preferred variant: non-www

HTTP → HTTPS

301http://hotmail.com/ https://outlook.live.com/owa/

Consistent

A+
Domain Intelligence
hotmail.com — via MarkMonitor Inc., 30 years, 6 months old, hosted on Microsoft Azure
PASS
hotmail.com — via MarkMonitor Inc., 30 years, 6 months old, hosted on Microsoft Azure
Info::
Domain registered until Mar 28, 2027 (11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Microsoft Azure
Got: AS8068
Domain expiry

252 days

March 28, 2027

SSL certificate

311 days

Issued by Microsoft Corporation

Domain age

30 years, 6 months

Registered March 27, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8068

204.79.197.212

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created March 27, 1996 (30 years, 6 months ago)
Expires March 28, 2027 (11 months)
Last Updated January 29, 2026
Name Servers ns1-205.azure-dns.com, ns2-205.azure-dns.net, ns3-205.azure-dns.org, ns4-205.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 204.79.197.212
ASN AS8068 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 122 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
52 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
123 ms
Total Time Total request time from DNS lookup through full response.
123 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 17 ms TLS Handshake 52 ms Server Processing 19 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback