Skip to content
https://bitcoin.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
0
REVIEW
1
PASS
7
INFO
1
Probed from Madrid, Spain
302 Found
Checks
9
7 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
63 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

63
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
A+
DNS Records
2 A records, 49 ms lookup
PASS
2 A records, 49 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.9.86, 172.67.189.49
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::ac43:bd31, 2606:4700:3031::6815:956
Info::
2 nameserver(s) configured
Got: keanu.ns.cloudflare.com, meera.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 49 ms
Got: 49 ms
A104.21.9.86, 172.67.189.49
AAAA2606:4700:3034::ac43:bd31, 2606:4700:3031::6815:956
CNAME—
NSkeanu.ns.cloudflare.com, meera.ns.cloudflare.com
MX
10 mx.zoho.com
20 mx2.zoho.com
TXT
SPF v=spf1 mx include:zoho.com -all
google-site-verification=HQ6n1bD-lkg0C8_rr6GYh1LXqaY4wspMvxv4fYVW4N4
CAALookup not available with standard resolver
Resolved in 49 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.

A
Redirect Chain
1 redirect(s), 435 ms total
PASS
1 redirect(s), 435 ms total
Info::
Single redirect
Got: https://bitcoin.org → https://bitcoin.org/en/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://bitcoin.org

https://bitcoin.org

212 ms · HTTP/1.1

302

https://bitcoin.org/en/

223 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bitcoin.org302212 msHTTP/1.1cloudflare
2https://bitcoin.org/en/200223 msHTTP/1.1cloudflare

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 (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3034::ac43:bd31, 2606:4700:3031::6815:956
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3034::ac43:bd31, 2606:4700:3031::6815:956 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 1022 URLs
PASS
robots.txt present, sitemap with 1022 URLs
Info::
robots.txt is present
Got: 43 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1022 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 43 B Sitemaps referenced 1 User-agents Blocking No — crawling allowed

Sitemap: https://bitcoin.org/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 1022 entries Valid XML Yes
Sample URLs:
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.bitcoin.org/
200https://bitcoin.org/

Preferred variant: non-www

HTTP → HTTPS

301http://bitcoin.org/ → https://bitcoin.org/

Consistent

A+
HTTP Probe Timing
Total 263 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
50 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 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.
263 ms
Total Time Total request time from DNS lookup through full response.
263 ms

Connection waterfall

DNS Lookup 50 ms TCP Connect 16 ms TLS Handshake 23 ms Server Processing 174 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff734f88679eca-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9eff734f88679eca-CDG
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