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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
6 PASS 3 REVIEW
B
DNS Records
1 A records, 140 ms lookup
REVIEW
1 A records, 140 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.15.142.68
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1417:8400:28e::3544, 2600:1417:8400:284::3544
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: e13636.dscb.akamaiedge.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: 140 ms
Got: 140 ms
A23.15.142.68
AAAA2600:1417:8400:28e::3544, 2600:1417:8400:284::3544
CNAMEe13636.dscb.akamaiedge.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 140 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

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
250 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
REVIEW
Azure CDN
Info::
Site is served via Azure CDN CDN
Got: x-azure-ref: 20260404T182804Z-r1c6f98c89d8pfhfhC1HKGggns0000000ca000000000357d
CDN Detected: Azure CDN
Provider Azure CDN Evidence x-azure-ref: 20260404T182804Z-r1c6f98c89d8pfhfhC1HKGggns0000000ca000000000357d
A
Redirect Chain
1 redirect(s), 384 ms total
PASS
1 redirect(s), 384 ms total
Info::
Single redirect
Got: https://learn.microsoft.com → https://learn.microsoft.com/en-us/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://learn.microsoft.com

https://learn.microsoft.com

339 ms · HTTP/1.1

302

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

45 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://learn.microsoft.com302339 msHTTP/1.1
2https://learn.microsoft.com/en-us/20045 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

A+
IPv6 Readiness
IPv6 reachable (34 ms)
PASS
IPv6 reachable (34 ms)
Info::
IPv6 is configured and reachable at 2600:1417:8400:28e::3544, 2600:1417:8400:284::3544
Got: 34 ms connect
IPv6 Ready
AAAA Records 2600:1417:8400:28e::3544, 2600:1417:8400:284::3544 Connection Reachable (34 ms)
A+
Crawlability
robots.txt present, sitemap with 5148 URLs
PASS
robots.txt present, sitemap with 5148 URLs
Info::
robots.txt is present
Got: 765 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5148 entries
Info::
Sitemap index with 5148 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 765 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# learn.microsoft.com
# 08/19/2022

User-agent: *

Sitemap: https://learn.microsoft.com/_sitemaps/sitemapindex.xml
Sitemap: https://learn.microsoft.com/answers/sitemaps/sitemap.xml

Disallow: /*/answers/accounts/
Disallow: /*/answers/users/
Disallow: /*/answers/revisions/
Disallow: /*/answers/search
Disallow: /*/answers/*sort=newest
Disallow: /*/answers/*sort=hottest
Disallow: /*/answers/*sort=votes
Disallow: /*/answers/commands/
Disallow: /*/answers/badges/
Disallow: /*/answers/comments
Disallow: /*/answers/*?*sort=
Disallow: /*/answers/*?*topics=
Disallow: /*/answers/*?*pagesize=
Disallow: /*/answers/*?*orderby=
Disallow: /*/answers/*?*filterby=
Disallow: /*/opbuildpdf/
Disallow: /*/search/?*terms
Disallow: /api/nextsteps/*
Disallow: /api/attachments/*
sitemap.xml 200 OK
Type Sitemap Index URLs 5148 entries Valid XML Yes
Child Sitemaps:
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.learn.microsoft.com/
200https://learn.microsoft.com/

Preferred variant: non-www

HTTP → HTTPS

301http://learn.microsoft.com/ → https://learn.microsoft.com/

Consistent

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, 1 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.
Domain expiry

323 days

May 3, 2027

SSL certificate

250 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::39

Registrar

MarkMonitor Inc.

Lock status unknown 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
Registrar MarkMonitor Inc.
Created May 2, 1991 (35 years, 5 months ago)
Expires May 3, 2027 (1 years, 1 months)
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::39
Data source: rdap (6.2s)

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

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

Connection waterfall

DNS Lookup 211 ms TCP Connect 34 ms TLS Handshake 38 ms Server Processing 201 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