Skip to content
https://torproject.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 54 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 54 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /javascript
Disallow: /scss
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.torproject.org/
200https://torproject.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://torproject.org/ → https://www.torproject.org/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
5 A records, 63 ms lookup
PASS
5 A records, 63 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 95.216.163.36, 116.202.120.165, 204.8.99.144, 204.8.99.146, 116.202.120.166
Info::
Has 5 IPv6 (AAAA) record(s)
Got: 2620:7:6002:0:466:39ff:fe32:e3dd, 2620:7:6002:0:466:39ff:fe7f:1826, 2a01:4f8:fff0:4f:266:37ff:fe2c:5d19, 2a01:4f9:c010:19eb::1, 2a01:4f8:fff0:4f:266:37ff:feae:3bbc
Info::
6 nameserver(s) configured
Got: ns5.torproject.org, nsp.dnsnode.net, ns2.torproject.org, ns1.torproject.org, ns4.torproject.org, ns3.torproject.org
Info::
1 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: 63 ms
Got: 63 ms
A95.216.163.36, 116.202.120.165, 204.8.99.144, 204.8.99.146, 116.202.120.166
AAAA2620:7:6002:0:466:39ff:fe32:e3dd, 2620:7:6002:0:466:39ff:fe7f:1826, 2a01:4f8:fff0:4f:266:37ff:fe2c:5d19, 2a01:4f9:c010:19eb::1, 2a01:4f8:fff0:4f:266:37ff:feae:3bbc
CNAME—
NSns5.torproject.org, nsp.dnsnode.net, ns2.torproject.org, ns1.torproject.org, ns4.torproject.org, ns3.torproject.org
MX
10 mx-dal-01.torproject.org
TXT
_dpwm8776gpzbj9ttd4teweyhomh2ove
SPF v=spf1 a:crm-int-01.torproject.org a:submit-01.torproject.org a:rdsys-frontend-0...
google-site-verification=YeQsuz0lo1q00m6KE1lpJX7hHBzriDpcMHr_f9q2Ag8
CAALookup not available with standard resolver
Resolved in 63 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), 292 ms total
PASS
1 redirect(s), 292 ms total
Info::
Single redirect
Got: https://torproject.org → https://www.torproject.org/ (301)
Info::
WWW normalization redirect

https://torproject.org

97 ms · HTTP/1.1

301

https://www.torproject.org/

195 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://torproject.org30197 msHTTP/1.1Apache
2https://www.torproject.org/200195 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (109 ms)
PASS
IPv6 reachable (109 ms)
Info::
IPv6 is configured and reachable at 2620:7:6002:0:466:39ff:fe32:e3dd, 2620:7:6002:0:466:39ff:fe7f:1826, 2a01:4f8:fff0:4f:266:37ff:fe2c:5d19, 2a01:4f9:c010:19eb::1, 2a01:4f8:fff0:4f:266:37ff:feae:3bbc
Got: 109 ms connect
IPv6 Ready
AAAA Records 2620:7:6002:0:466:39ff:fe32:e3dd, 2620:7:6002:0:466:39ff:fe7f:1826, 2a01:4f8:fff0:4f:266:37ff:fe2c:5d19, 2a01:4f9:c010:19eb::1, 2a01:4f8:fff0:4f:266:37ff:feae:3bbc Connection Reachable (109 ms)
A+
Domain Intelligence
torproject.org — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 19 years, 9 months old
PASS
torproject.org — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 19 years, 9 months old
Info::
Domain registered until Oct 17, 2027 (1 years, 6 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: CSL Computer Service Langenbach GmbH d/b/a joker.com
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

459 days

October 17, 2027

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

19 years, 9 months

Registered October 17, 2006

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2620:7:6002:0:466:39ff:fe7f:1826

Registrar

CSL Computer Service Langenbach GmbH d/b/a joker.com

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSL Computer Service Langenbach GmbH d/b/a joker.com
Created October 17, 2006 (19 years, 9 months ago)
Expires October 17, 2027 (1 years, 6 months)
Last Updated January 8, 2026
Name Servers ns4.torproject.org, ns5.torproject.org, ns1.torproject.org, ns3.torproject.org, nsp.dnsnode.net, ns2.torproject.org
DNSSEC Enabled
Hosting
IP Address 2620:7:6002:0:466:39ff:fe7f:1826
Data source: rdap (0.2s)

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 130 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
30 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
35 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
130 ms
Total Time Total request time from DNS lookup through full response.
130 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 30 ms TLS Handshake 35 ms Server Processing 30 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