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.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /*/sep$
Disallow: /*.json$
Disallow: /*?q
Disallow: /*?*cp=
Disallow: /*?*wcmmode=
Disallow: /*?*cooperation=
Disallow: /de/send-mail?
Disallow: /en/send-mail?
Disallow: /es/send-mail?
Disallow: /it/send-mail?
Disallow: /fr/send-mail?
Disallow: /ko/send-mail?
Disallow: /ja/send-mail?
Disallow: /pt/send-mail?
Disallow: /pl/send-mail?
Disallow: /zh/send-mail?
Disallow: /tr/send-mail?
Disallow: /hu/send-mail?
Disallow: /ar/send-mail?
Disallow: /executive-board-newsletter/
Disallow: /vorstandsnewsletter/
Disallow: /*?field
Disallow: /?refreshed=true
No sitemap found
Adding a sitemap helps search engines discover your pages.
CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BTLS Certificate Expiry & Recommendations182 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
A+DNS Records1 A records, 92 ms lookupPASS
| A | 192.102.162.236 |
| AAAA | — |
| CNAME | — |
| NS | ns3.fraunhofer.de, ns5.fraunhofer.de, ns2.fraunhofer.de, ns1.fraunhofer.de |
| MX | 10 edge01.mx.fraunhofer.de 20 edge02.mx.fraunhofer.de 30 edge03.mx.fraunhofer.de 40 edge04.mx.fraunhofer.de |
| TXT | docusign=f7c08718-890f-451e-aa82-7d3db4c851d2 SPF v=spf1 redirect=_spf.fraunhofer.de docusign=fb58bf6e-96a7-4a3d-a4fa-0c29fe17cb81 google-site-verification=z1G17QvtZcDqMwKHTtkHIzNH09MCtvywrBympNRxoSg mindmanager-verification=a2925bce5c46c7ee5b25314ba14dfde596b4705d789c71c556defd5... |
| 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.
ARedirect Chain1 redirect(s), 364 ms totalPASS
https://fraunhofer.de
147 ms · HTTP/1.1
https://www.fraunhofer.de/
217 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://fraunhofer.de | 308 | 147 ms | HTTP/1.1 | Apache |
| 2 | https://www.fraunhofer.de/ | 200 | 217 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencefraunhofer.de — hosted on DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DEPASS
Unknown
182 days
Issued by Hellenic Academic and Research Institutions CA
Unknown
Status unknown
Protects against DNS spoofing
DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
ASN AS680
192.102.162.236
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