Skip to content
https://www.hetzner.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
200 OK
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
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
HTTP Probe Timing
Total 982 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
177 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
201 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
203 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
982 ms
Total Time Total request time from DNS lookup through full response.
983 ms

Connection waterfall

DNS Lookup 177 ms TCP Connect 201 ms TLS Handshake 203 ms Server Processing 402 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
128 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

128
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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 187 ms lookup
PASS
1 A records, 187 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 213.133.116.44
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: 2a01:4f8:0:1::7:4
Info::
No NS records found
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: 187 ms
Got: 187 ms
A213.133.116.44
AAAA2a01:4f8:0:1::7:4
CNAME—
NS—
MX—
TXT
0b2d2q52nf7bhnbydc9v46761vcs6jbp
CAALookup not available with standard resolver
Resolved in 187 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

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.hetzner.com

https://www.hetzner.com

990 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.hetzner.com200990 msHTTP/1.1HeRay
A+
IPv6 Readiness
IPv6 reachable (207 ms)
PASS
IPv6 reachable (207 ms)
Info::
IPv6 is configured and reachable at 2a01:4f8:0:1::7:4
Got: 207 ms connect
IPv6 Ready
AAAA Records 2a01:4f8:0:1::7:4 Connection Reachable (207 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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.hetzner.com/
301https://hetzner.com/

Preferred variant: www

HTTP → HTTPS

301http://www.hetzner.com/ → https://www.hetzner.com/

Consistent

A+
Domain Intelligence
hetzner.com — via Hetzner Online GmbH, 29 years, 7 months old
PASS
hetzner.com — via Hetzner Online GmbH, 29 years, 7 months old
Info::
Domain registered until Jan 14, 2027 (9 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: Hetzner Online GmbH
Domain expiry

212 days

January 14, 2027

SSL certificate

128 days

Issued by DigiCert Inc

Domain age

29 years, 7 months

Registered January 15, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a01:4f8:0:1::7:4

Registrar

Hetzner Online GmbH

Lock status unknown 3 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
Registrar Hetzner Online GmbH
Created January 15, 1997 (29 years, 7 months ago)
Expires January 14, 2027 (9 months)
Last Updated March 13, 2026
Name Servers ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de
DNSSEC Not enabled
Hosting
IP Address 2a01:4f8:0:1::7:4
Data source: rdap (0.4s)

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

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

Send Feedback