Skip to content
https://hornbach.de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 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
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 151.101.1.91: lookup 151.101.1.91: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.193.91: lookup 151.101.193.91: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.129.91: lookup 151.101.129.91: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.65.91: lookup 151.101.65.91: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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.hornbach.de/
200https://hornbach.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://hornbach.de/ https://hornbach.de/

Consistent

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

Certificate validity

73
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
4 A records, 27 ms lookup
PASS
4 A records, 27 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.1.91, 151.101.193.91, 151.101.129.91, 151.101.65.91
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-c.eurodns.eu, ns-d.eurodns.biz, ns-a.eurodns.com, ns-b.eurodns.org
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 27 ms
Got: 27 ms
A151.101.1.91, 151.101.193.91, 151.101.129.91, 151.101.65.91
AAAA
CNAME
NSns-c.eurodns.eu, ns-d.eurodns.biz, ns-a.eurodns.com, ns-b.eurodns.org
MX
20 mx-in01.eu.retarus.com
20 mx-in02.eu.retarus.com
TXT
apple-domain-verification=Zn0wjdX_iPjv9CmH2E6E74WldzYBiwz7q5usMbaqV7Q
MS=ms69565756
_globalsign-domain-verification=OiMLz9t0gLMSiBHtlW7QhBy3ONiAXNgZzv9xA9P0KV
globalsign-domain-verification=OFAs510r87I0qTTcc0IGvMhgqF7EUks5v-SKPK3mOC
_globalsign-domain-verification=nVeYNZLNys7KwLHTRZIfQGBrb7sswF-nZE8tWFTanP
apple-domain-verification=2rk4GnKtxkyVu8mX
_globalsign-domain-verification=xPRBPl3IM-0hinp4o6s7olnShBwj3hbSBRt3H1HQjS
SPF v=spf1 mx include:_spf.retarus.com include:_spf.general.transactional-mail-a.com...
_globalsign-domain-verification=ru5zUNbnv5d7hQS4oC-XyB0W0cAKD9oU1Z-SPzrRaa
_globalsign-domain-verification=HFUcCHGKOzZ6JBJj586lvE_2dX6qHrWpaC-kzFD4P0
b/pgghX1YEZ8K/ZR0tsQz5Q2HnWQYSoXomOGeknDaIc=
_globalsign-domain-verification=pJQqqs7ym8yh3yCJREpttQEH0Oh6pF-J8-CATOo3gn
google-site-verification=O6IN1i_8Wnc13XhQYAutvHAysMGODoqD2of2itZLjlA
NyS3LiCehfAB/lfjOy7Q2mInpsRG3amsvZI1Ph2Fmyk=
CAALookup not available with standard resolver
Resolved in 27 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
CAA Records
issue: amazon.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog, sectigo.com | issuewild: globalsign.com, letsencrypt.org, pki.goog, sectigo.com | iodef configured
PASS
issue: amazon.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog, sectigo.com | issuewild: globalsign.com, letsencrypt.org, pki.goog, sectigo.com | iodef configured
Info::
CAA issue tag present — authorized CA(s): amazon.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog, sectigo.com
Info::
CAA iodef tag present (failed-issuance notifications enabled)
A+
Multi-Resolver DNS Speed
Mean 31ms across 3 resolvers (spread 36ms)
PASS
Mean 31ms across 3 resolvers (spread 36ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
Info::
Quad9: 53ms
Got: 53ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 137 ms total
PASS
1 redirect(s), 137 ms total
Info::
Single redirect
Got: https://hornbach.de → https://www.hornbach.de/ (301)
Info::
WWW normalization redirect

https://hornbach.de

5 ms · HTTP/1.1

301

https://www.hornbach.de/

131 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hornbach.de3015 msHTTP/1.1Varnish
2https://www.hornbach.de/200131 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 20 URLs
PASS
robots.txt present, sitemap with 20 URLs
Info::
robots.txt is present
Got: 427 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
Sitemap index with 20 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 427 B Sitemaps referenced 1 User-agents BLEXbot, *, SemrushBot, proximic Blocking No — crawling allowed
User-agent: *
Disallow: /checkout
Disallow: /customer/
Disallow: /cart/
Disallow: /wishlist/
Disallow: /contact/
Disallow: /comparison/
Disallow: /hornbach/cms/
Disallow: /ordertracking/
Disallow: /customer-purchases/


User-agent: SemrushBot
Disallow: /

# comScore: (https://www.comscore.com/Web-Crawler)
User-agent: proximic
Disallow: /

User-agent: BLEXbot
Disallow: /

Sitemap: https://www.hornbach.de/sitemap/sitemap.xml

A+
Domain Intelligence
hornbach.de — hosted on Fastly
PASS
hornbach.de — hosted on Fastly
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.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

Unknown

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.129.91

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 151.101.129.91
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: whois (0.8s)

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

Connection waterfall

DNS Lookup 27 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 1 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