Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1134 ms totalREVIEW
https://heise.de
663 ms · HTTP/1.1
https://www.heise.de/
470 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://heise.de | 301 | 663 ms | HTTP/1.1 | nginx |
| 2 | https://www.heise.de/ | 200 | 470 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations48 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
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 DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records1 A records, 353 ms lookupPASS
| A | 193.99.144.80 |
| AAAA | 2a02:2e0:3fe:1001:302:: |
| CNAME | — |
| NS | ns2.pop-hannover.net, ns.heise.de, ns.plusline.de, ns.pop-hannover.de, ns.s.plusline.de |
| MX | 10 mx01.hornetsecurity.com 20 mx02.hornetsecurity.com 30 mx03.hornetsecurity.com 40 mx04.hornetsecurity.com |
| TXT | docusign=b14b0107-39e4-44c2-b48f-944859786474 wUIdRqARf1uNkZkPoWGdYvEmK408vvKC3HKme1h/rnswYDphj9Ytgwt6K1Df1PQnW64Oi3t9c9uKoo98... google-site-verification=7CvE9FRS3zv0wnl8KzLmVw0TSlQay6qOX_zGFm2wzWw c3ViZG9tYWlu brevo-code:3022b29c6069a0b2ab4ad1eae06d06df kT2+bTXGMSIudHQATflucV7vjLhdq9Y18pKTKJxs0O2IebE8seBu4vCAe9MBHYehuRJWwKKt1klytxF4... apple-domain-verification=m53iQZB4O1uMxDGR tollbit-domain-verification=6fd594c990db1742b6cb34f3699d3944885e664c32333cf8cb17... google-site-verification=8kcKAZp-IbbJG7FQzRxIaUXv9Ku4qX0wgMrm_hx_L2s SPF v=spf1 ip4:193.99.144.0/24 ip4:193.99.145.0/24 ip6:2a02:2e0:3fe:1001::/64 ip6:2a... miro-verification=601d1e3e9623fe2102de9d6d215a2380ae5c69bd |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+IPv6 ReadinessIPv6 reachable (152 ms)PASS
ACrawlabilityno robots.txt, sitemap with 4736 URLsPASS
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
- https://www.heise.de/news/KI-Chatbots-auf-WhatsApp-Meta-muss-Konkurrenten-zulassen-11259699.html
- https://www.heise.de/news/Kostensenkung-und-Profitsteigerung-Snap-baut-1-000-Stellen-ab-11259675.html
- https://www.heise.de/news/Bericht-Grok-stand-angeblich-kurz-vor-App-Store-Rauswurf-11259603.html
- https://www.heise.de/news/Lithografie-Systeme-Speicherhersteller-machen-den-meisten-ASML-Umsatz-aus-11259535.html
- https://www.heise.de/hintergrund/Private-Energiewende-fuer-Skeptiker-Praxisbericht-Wenn-es-nur-ums-Geld-geht-11247011.html
A+Domain Intelligenceheise.dePASS
Unknown
48 days
Issued by Let's Encrypt
Unknown
Status unknown
Protects against DNS spoofing
Unknown
2a02:2e0:3fe:1001:302::
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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