Skip to content
https://sphinx-doc.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
4
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 474 ms total
REVIEW
2 redirect(s), 474 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.sphinx-doc.org/

https://sphinx-doc.org

60 ms · HTTP/1.1

301

https://www.sphinx-doc.org/

289 ms · HTTP/1.1

302

https://www.sphinx-doc.org/en/master/

125 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sphinx-doc.org30160 msHTTP/1.1cloudflare
2https://www.sphinx-doc.org/302289 msHTTP/1.1cloudflare
3https://www.sphinx-doc.org/en/master/200125 msHTTP/1.1cloudflare

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

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

302https://www.sphinx-doc.org/
200https://sphinx-doc.org/

Preferred variant: non-www

HTTP → HTTPS

301http://sphinx-doc.org/ http://www.sphinx-doc.org/

HTTP version does not redirect to HTTPS

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

Certificate validity

42
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9effab333a9919a5-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9effab333a9919a5-CDG
A+
DNS Records
2 A records, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.166.9, 104.21.11.126
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::ac43:a609, 2606:4700:3032::6815:b7e
Info::
2 nameserver(s) configured
Got: terin.ns.cloudflare.com, aurora.ns.cloudflare.com
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: 37 ms
Got: 37 ms
A172.67.166.9, 104.21.11.126
AAAA2606:4700:3037::ac43:a609, 2606:4700:3032::6815:b7e
CNAME
NSterin.ns.cloudflare.com, aurora.ns.cloudflare.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 37 ms

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)

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3037::ac43:a609, 2606:4700:3032::6815:b7e
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3037::ac43:a609, 2606:4700:3032::6815:b7e Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 551 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 551 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# This robots.txt file is autogenerated by Read the Docs.
# It controls the crawling and indexing of your documentation by search engines.
#
# You can learn more about robots.txt, including how to customize it, in our documentation:
#
# * Our documentation on Robots.txt: https://docs.readthedocs.com/platform/stable/reference/robots.html
# * Our guide about SEO techniques: https://docs.readthedocs.com/platform/stable/guides/technical-docs-seo-guide.html

User-agent: *

Disallow: # Allow everything

Sitemap: https://www.sphinx-doc.org/sitemap.xml

sitemap.xml 200 OK
Type URL Set URLs 1 entries Valid XML Yes
A+
HTTP Probe Timing
Total 96 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 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.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
96 ms
Total Time Total request time from DNS lookup through full response.
97 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 18 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback