Skip to content
https://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106?wt.mc_id=studentamb_575125

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
D
HTTP Probe Timing
Action
Total 2069 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 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.
19 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.92 s
Total Time Total request time from DNS lookup through full response.
2.07 s

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 19 ms Server Processing 1.85 s Content Transfer 147 ms
B
DNS Records
1 A records, 33 ms lookup
REVIEW
1 A records, 33 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 150.171.110.117
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2603:1061:14:174::1
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: gxcuf89792.lithium.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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: 33 ms
Got: 33 ms
A150.171.110.117
AAAA2603:1061:14:174::1
CNAMEgxcuf89792.lithium.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 33 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

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
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 150.171.110.117: lookup 150.171.110.117: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1061:14:174::1: lookup 2603:1061:14:174::1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Warning::
Trailing slash inconsistency — both versions serve content
Got: Both with/without trailing slash return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 307 Expected: 301 or 308 permanent redirect

www / non-www

https://www.techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106
200https://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106

Trailing Slash

200https://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106/
200https://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106?wt.mc_id=studentamb_575125

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106 → https://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106

Use a permanent redirect (301 or 308) instead of a temporary one

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

Certificate validity

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

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
B
CDN & Delivery
Azure CDN (PRIVATE_NOSTORE)
REVIEW
Azure CDN (PRIVATE_NOSTORE)
Info::
Document is served via Azure CDN CDN
Got: x-azure-ref: 20260930T014403Z-185c44b58859vzqfhC1PARw1tn0000001cyg0000000061eu
Info::
CDN cache status: PRIVATE_NOSTORE
Document served via CDN: Azure CDN
Provider Azure CDN Cache Status PRIVATE_NOSTORE Evidence x-azure-ref: 20260930T014403Z-185c44b58859vzqfhC1PARw1tn0000001cyg0000000061eu
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 22ms across 3 resolvers (spread 33ms)
PASS
Mean 22ms across 3 resolvers (spread 33ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 33ms
Got: 33ms via 8.8.8.8:53
Info::
Cloudflare: 34ms
Got: 34ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://techcommunity.microsoft.com/discussions/Azure/the-partition-count-you-picked-on-day-1-doesnt-have-to-follow-you-forever/4559106?wt.mc_id=studentamb_575125

https://techcommunity.microsoft.com/disc...

2225 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://techcommunity.microsoft.com/disc...2002225 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2603:1061:14:174::1
Got: 16 ms connect
IPv6 Ready
AAAA Records 2603:1061:14:174::1 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 607 URLs
PASS
robots.txt present, sitemap with 607 URLs
Info::
robots.txt is present
Got: 553 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 607 entries
Info::
Sitemap index with 607 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 553 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://techcommunity.microsoft.com/sitemap.xml
Disallow: /closedgrouphub/
Disallow: /users/
Disallow: /mysettings/
Disallow: /help
Disallow: /*?t:ac=
Disallow: /*&t:ac=
Disallow: /*:lightboxrendercomponent?
Disallow: /*:lightboxrendercomponent&
Disallow: /*:lightboxrendercomponent/
Disallow: /*?ticket=
Disallow: /*&ticket=
Disallow: /t5/notifications/notifymoderatorpage
Disallow: /gxcuf89792/rss
Disallow: /plugins/custom
Disallow: /t5/media/gallerypage/

Disallow: /privategrouphubs/
Disallow: /edit$
Disallow: /attachments/
sitemap.xml 200 OK
Type Sitemap Index URLs 607 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
microsoft.com — via MarkMonitor Inc., 35 years, 11 months old
PASS
microsoft.com — via MarkMonitor Inc., 35 years, 11 months old
Info::
Domain registered until May 3, 2027 (7 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.
Domain expiry

196 days

May 3, 2027

SSL certificate

35 days

Issued by DigiCert Inc

Domain age

35 years, 11 months

Registered May 2, 1991

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2603:1061:14:178::1

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, 11 months ago)
Expires May 3, 2027 (7 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 2603:1061:14:178::1
Data source: rdap (0.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

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+
CDN Cache Observability
Cache state: PRIVATE_NOSTORE
PASS
Cache state: PRIVATE_NOSTORE
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=PRIVATE_NOSTORE
A+
Health Check Endpoint
Health endpoint at https://techcommunity.microsoft.com/health (HTTP 200)
PASS
Health endpoint at https://techcommunity.microsoft.com/health (HTTP 200)
Info::
Public health endpoint at https://techcommunity.microsoft.com/health
Got: https://techcommunity.microsoft.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback