Skip to content
https://hetzner.de

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
301 Moved Permanently
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
169 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

169
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
A+
DNS Records
1 A records, 39 ms lookup
PASS
1 A records, 39 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::
3 nameserver(s) configured
Got: ns.second-ns.com, ns3.second-ns.de, ns1.your-server.de
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: 39 ms
Got: 39 ms
A213.133.116.44
AAAA2a01:4f8:0:1::7:4
CNAME—
NSns.second-ns.com, ns3.second-ns.de, ns1.your-server.de
MX
10 mail.hetzner.company
TXT
Trustpilot-Verification-kqvVskCm6JQ9Vg1qAmahpBSJ5tvZORbriFyVIk4E
SPF v=spf1 include:_spf.hetzner.com include:spf.nl2go.com include:spf.brevo.com -all
google-site-verification=5VJIPcjFAogQCwZoXgwmymUwf6fLylQYFzt_yo8fwWw
_p4irzib9mg6l3pqb9n7z5je690hoyrm
MS=28BE46DF2C2D9EE896CCCC268DC6CBD9FE32E2D9
CAALookup not available with standard resolver
Resolved in 39 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.

A
Redirect Chain
1 redirect(s), 260 ms total
PASS
1 redirect(s), 260 ms total
Info::
Single redirect
Got: https://hetzner.de → https://www.hetzner.com/de/ (301)
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://hetzner.de

106 ms · HTTP/1.1

301

https://www.hetzner.com/de/

154 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hetzner.de301106 msHTTP/1.1HeRay
2https://www.hetzner.com/de/200154 msHTTP/1.1HeRay

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (28 ms)
PASS
IPv6 reachable (28 ms)
Info::
IPv6 is configured and reachable at 2a01:4f8:0:1::7:4
Got: 28 ms connect
IPv6 Ready
AAAA Records 2a01:4f8:0:1::7:4 Connection Reachable (28 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
hetzner.de
PASS
hetzner.de
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

Unknown

SSL certificate

169 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

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

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 2a01:4f8:0:1::7:4
Data source: whois (0.5s)

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 28 ms TLS Handshake 47 ms Server Processing 28 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