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), 1406 ms totalREVIEW
https://auswaertiges-amt.de
605 ms · HTTP/1.1
https://www.auswaertiges-amt.de/
801 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://auswaertiges-amt.de | 301 | 605 ms | HTTP/1.1 | |
| 2 | https://www.auswaertiges-amt.de/ | 200 | 801 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations206 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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, 11 ms lookupPASS
| A | 46.243.125.53 |
| AAAA | — |
| CNAME | — |
| NS | d.babieldns.de, c.babieldns.de, b.babieldns.de, a.babieldns.de |
| MX | 10 mx1.bund.de 10 mx2.bund.de |
| TXT | globalsign-domain-verification=XFWoZAhHGQ7hNt61c0I4atFYw2DN2Zhp7cA-oQl9PI apple-domain-verification=Xmh9iwh9uvxZSScX google-site-verification=OvJ0rsPGeSA1HQULC6_RJ46ryyZx2QUaN7mPKSkSes8 SPF v=spf1 include:_spf1.bund.de ip4:46.243.125.204 -all google-site-verification=6G_NPTFWVzG_9BFrtTDtK1fqZZyB5F7tzig0wGGxaQk |
| 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.
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
User-agent: *
Disallow: /includes/
Disallow: /includes/
Disallow: /WEB-INF/
Disallow: /blueprint/WEB-INF/
Disallow: /static/appdata/
Sitemap: https://www.auswaertiges-amt.de/service-sitemap-de-sitemap_index.xml
Sitemap: https://www.auswaertiges-amt.de/service-sitemap-en-sitemap_index.xml
A+Domain Intelligenceauswaertiges-amt.de — hosted on BABIEL-NET, DEPASS
Unknown
206 days
Issued by GlobalSign nv-sa
Unknown
Status unknown
Protects against DNS spoofing
BABIEL-NET, DE
ASN AS198913
46.243.125.53
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