Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FCrawlabilityActionrobots.txt present, sitemap with 0 URLsFIX
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# Robots.txt file for http://go.microsoft.com
#
User-agent: *
Allow:/fwlink/p/
Disallow:/
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations271 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BCDN & DeliveryAkamaiREVIEW
A+DNS Records1 A records, 6 ms lookupPASS
| A | 23.45.137.145 |
| AAAA | — |
| CNAME | — |
| NS | asia1.akam.net, eur2.akam.net, asia3.akam.net, ns1-132.akam.net, ns1-191.akam.net, usw1.akam.net, use9.akam.net, usc4.akam.net |
| MX | — |
| TXT | SPF v=spf1 -all google-site-verification=_GQK9-TxtgH2f9HIVswdbMDlU0tPtbFlU52rwj3Zfhc google-site-verification=hmJHeHI5g2xahyeorI05Mp8n3Q5uuxJVYzgoiR3heXk google-site-verification=OLIev-Dhm_GjGnF_5WElcY1g9Y0tGBgfqDJeePQPy0k akaprodcs.azurewebsites.net google-site-verification=HZlxQO87rQMu1JifSu8YrFxfNSRmLPxjCSYMH9Sv2mU google-site-verification=K1RiUqmDiLrkprOC6Au9x2jpqtLRfe1GBS4RnHKOSls google-site-verification=Xwu-AiYLjcs965PJQuNABfnosFgzJjYXpyrca73p6mY google-site-verification=4tHGSXxDCXQBLZs7xyGJFLLocgHDg2_UkWzCSgr6RcE google-site-verification=V5Rw20DBVKp5R9C3B3lua8ucBMWdn1_pbMNQzb0YRFQ google-site-verification=cQ5sq03lw0OzN4SppJPr8x42KZc55dSQq7ZPSoG6j1A facebook-domain-verification=m6bk15w3gdsau9c5kfjw2a9dyg3321 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 132 ms totalPASS
https://aka.ms
12 ms · HTTP/1.1
https://witty-sand-06796de1e.2.azurestat...
120 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://aka.ms | 302 | 12 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://witty-sand-06796de1e.2.azurestat... | 200 | 120 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceaka.ms — via CSC Corporate Domains, 15 years, 5 months old, hosted on AkamaiPASS
156 days
January 20, 2027
271 days
Issued by Microsoft Corporation
15 years, 5 months
Registered January 20, 2011
Not enabled
Protects against DNS spoofing
Akamai
ASN AS16625
23.45.137.145
CSC Corporate Domains
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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