Skip to content
https://www.debian.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

86
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
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 76 ms lookup
PASS
2 A records, 76 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 194.177.211.216, 130.89.148.77
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2001:648:2ffc:deb:216:61ff:fe2b:6138, 2001:67c:2564:a119::77
Info::
3 nameserver(s) configured
Got: geo2.debian.org, geo1.debian.org, geo3.debian.org
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: 76 ms
Got: 76 ms
A194.177.211.216, 130.89.148.77
AAAA2001:648:2ffc:deb:216:61ff:fe2b:6138, 2001:67c:2564:a119::77
CNAME
NSgeo2.debian.org, geo1.debian.org, geo3.debian.org
MX
TXT
EU view
CAALookup not available with standard resolver
Resolved in 76 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.debian.org

https://www.debian.org

183 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.debian.org200183 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (56 ms)
PASS
IPv6 reachable (56 ms)
Info::
IPv6 is configured and reachable at 2001:648:2ffc:deb:216:61ff:fe2b:6138, 2001:67c:2564:a119::77
Got: 56 ms connect
IPv6 Ready
AAAA Records 2001:648:2ffc:deb:216:61ff:fe2b:6138, 2001:67c:2564:a119::77 Connection Reachable (56 ms)
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: www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.debian.org/
302https://debian.org/

Preferred variant: www

HTTP → HTTPS

302http://www.debian.org/ https://www.debian.org/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
debian.org — via Gandi SAS, 27 years, 5 months old
PASS
debian.org — via Gandi SAS, 27 years, 5 months old
Info::
Domain registered until Mar 10, 2027 (11 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Gandi SAS
Domain expiry

205 days

March 10, 2027

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

27 years, 5 months

Registered March 10, 1999

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:4e42:400::644

Registrar

Gandi SAS

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Gandi SAS
Created March 10, 1999 (27 years, 5 months ago)
Expires March 10, 2027 (11 months)
Last Updated January 14, 2026
Name Servers dns4.easydns.info, nsp.dnsnode.net, sec1.rcode0.net, sec2.rcode0.net
DNSSEC Enabled
Hosting
IP Address 2a04:4e42:400::644
Data source: rdap (0.2s)
A+
HTTP Probe Timing
Total 200 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
17 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
56 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
67 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
200 ms
Total Time Total request time from DNS lookup through full response.
200 ms

Connection waterfall

DNS Lookup 17 ms TCP Connect 56 ms TLS Handshake 67 ms Server Processing 59 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