Skip to content
https://support.microsoft.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
DNS Records
2 A records, 28 ms lookup
REVIEW
2 A records, 28 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.107.253.42, 13.107.226.42
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:1ec:48:1::42, 2620:1ec:29:1::42
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: emerald-prod-asgth3agbdfbhpgz.b02.azurefd.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 28 ms
Got: 28 ms
A13.107.253.42, 13.107.226.42
AAAA2620:1ec:48:1::42, 2620:1ec:29:1::42
CNAMEemerald-prod-asgth3agbdfbhpgz.b02.azurefd.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 28 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
TLS Certificate Expiry & Recommendations
168 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
B
CDN & Delivery
Azure CDN (CONFIG_NOCACHE)
REVIEW
Azure CDN (CONFIG_NOCACHE)
Info::
Site is served via Azure CDN CDN
Got: x-azure-ref: 20260421T184559Z-r1ff48f47d75n7pshC1PARfc3c00000004b000000000ge57
Info::
CDN cache status: CONFIG_NOCACHE
CDN Detected: Azure CDN
Provider Azure CDN Cache Status CONFIG_NOCACHE Evidence x-azure-ref: 20260421T184559Z-r1ff48f47d75n7pshC1PARfc3c00000004b000000000ge57
A
Redirect Chain
1 redirect(s), 139 ms total
PASS
1 redirect(s), 139 ms total
Info::
Single redirect
Got: https://support.microsoft.com → https://support.microsoft.com/en-us (301)

https://support.microsoft.com

88 ms · HTTP/1.1

301

https://support.microsoft.com/en-us

51 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://support.microsoft.com30188 msHTTP/1.1
2https://support.microsoft.com/en-us20051 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2620:1ec:48:1::42, 2620:1ec:29:1::42
Got: 17 ms connect
IPv6 Ready
AAAA Records 2620:1ec:48:1::42, 2620:1ec:29:1::42 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 640 URLs
PASS
robots.txt present, sitemap with 640 URLs
Info::
robots.txt is present
Got: 1080 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 640 entries
Info::
Sitemap index with 640 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1080 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *


Disallow: /default.aspx/kb/

Disallow: /default.aspx/ph/

Disallow: /mats/?diagid=100001&eulaaccept=yes*

Disallow: /mats/default.aspx?diagid=100001&eulaaccept=yes*

Disallow: /search/default.aspx?*


Disallow: /api/

Disallow: /app/

Disallow: /authoring/

Disallow: /common/

Disallow: /common/survey.aspx*

Disallow: /directory/

Disallow: /errors/

Disallow: /gethelp/

Disallow: /gp/gsshomepage/

Disallow: /gp/international_new/

Disallow: /hotfix/

Disallow: /oas/

Disallow: /search/

Disallow: /Search/

Disallow: /*/search/

Disallow: /*/Search/

Disallow: /ServiceDesks/

Disallow: /support/


Disallow: /contact/menu*

Disallow: /contact/partner*

Disallow: /contactus/mwaas*

Disallow: /*/contact/menu*

Disallow: /*/contact/partner*

Disallow: /*/contactus/mwaas*

Disallow: /*/home/contact*


Disallow: /authentication/signin

Disallow: /*/authentication/signin

Disallow: /signin-oidc

Disallow: /*/signin-oidc


Sitemap: https://support.microsoft.com/sitemap/collection.xml

Sitemap: https://support.microsoft.com/_sitemaps/sitemapindex.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 640 entries Valid XML Yes
Child Sitemaps:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.support.microsoft.com/
200https://support.microsoft.com/

HTTP → HTTPS

307http://support.microsoft.com/ → https://support.microsoft.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
microsoft.com — via MarkMonitor Inc., 35 years, 5 months old
PASS
microsoft.com — via MarkMonitor Inc., 35 years, 5 months old
Info::
Domain registered until May 3, 2027 (1 years 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.
Domain expiry

293 days

May 3, 2027

SSL certificate

168 days

Issued by Microsoft Corporation

Domain age

35 years, 5 months

Registered May 2, 1991

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:1ec:29:1::42

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 May 2, 1991 (35 years, 5 months ago)
Expires May 3, 2027 (1 years)
Last Updated January 29, 2026
Name Servers ns1-39.azure-dns.com, ns2-39.azure-dns.net, ns3-39.azure-dns.org, ns4-39.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 2620:1ec:29:1::42
Data source: rdap (0.1s)

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 147 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
53 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.
39 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
148 ms
Total Time Total request time from DNS lookup through full response.
148 ms

Connection waterfall

DNS Lookup 53 ms TCP Connect 17 ms TLS Handshake 39 ms Server Processing 38 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