Skip to content
https://bundesfinanzministerium.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
Redirect Chain
2 redirect(s), 465 ms total
REVIEW
2 redirect(s), 465 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.bundesfinanzministerium.de/

https://bundesfinanzministerium.de

120 ms · HTTP/1.1

301

https://www.bundesfinanzministerium.de/

239 ms · HTTP/1.1

302

https://www.bundesfinanzministerium.de/W...

106 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bundesfinanzministerium.de301120 msHTTP/1.1
2https://www.bundesfinanzministerium.de/302239 msHTTP/1.1
3https://www.bundesfinanzministerium.de/W...200106 msHTTP/1.1Varnish

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
TLS Certificate Expiry & Recommendations
216 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

216
days left
0d 30d 60d 90d+

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 Records
1 A records, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.6.22.209
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: d.ns14.net, b.ns14.net, a.ns14.net, c.ns14.net
Info::
No MX records — email not configured via DNS
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: 45 ms
Got: 45 ms
A66.6.22.209
AAAA—
CNAME—
NSd.ns14.net, b.ns14.net, a.ns14.net, c.ns14.net
MX—
TXT
apple-domain-verification=oS7m84rozZNt16BV
_telesec-domain-validation=354858_2026-01-15_6EwuuVrNsnCqaFHSzGeT4qvjXiBfuSe7bGR...
SPF v=spf1 mx include:_spf1.bund.de include:spf.init.de -all
CAALookup not available with standard resolver
Resolved in 45 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+
Crawlability
robots.txt present, sitemap with 2168 URLs
PASS
robots.txt present, sitemap with 2168 URLs
Info::
robots.txt is present
Got: 2226 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2168 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2226 B Sitemaps referenced 1 User-agents YandexMobileBot, TweetmemeBot, SafeDNSBot, yacybot, SemrushBot-BA, SemrushBot-BM, Mega-Index, jobs.de-Robot, JobboerseBot, Baiduspider, SEOkicks-Robot, MojeekBot, wonderbot, YandexAntivirus, Pinterestbot, Clewwa-Bot, MJ12bot, Cliqzbot, Mediatoolkitbot, SemrushBot-SA, Grobbot, AhrefsBot, Flamingo_SearchEngine, SemrushBot, SeznamBot, YandexImages, Yeti, Baiduspider-render, changedetection, SMTBot, rogerbot, vebidoobot, YaK, spbot, trendictionbot, Mail.RU_Bot, Wotbox, AlphaBot, Buck, *, Exabot, linkdexbot, MegaIndex.ru Blocking No — crawling allowed
User-agent: Clewwa-Bot
Disallow: */SiteGlobals
Disallow: */SharedDocs/ExterneLinks
Disallow: */Content/FR
Disallow: */Web/FR
Allow: */SiteGlobals/Forms/_components/Buttons/
Allow: */SiteGlobals/Functions/JavaScript/
Allow: */SiteGlobals/Functions/SocialBookmarks/
Allow: */SiteGlobals/StyleBundles/Bilder/
Allow: */SiteGlobals/StyleBundles/CSS/
Crawl-delay: 15

User-agent: *
Disallow: */SiteGlobals
Disallow: */SharedDocs/ExterneLinks
Disallow: */Content/FR
Disallow: */Web/FR
Allow: */SiteGlobals/Forms/_components/Buttons/
Allow: */SiteGlobals/Functions/JavaScript/
Allow: */SiteGlobals/Functions/SocialBookmarks/
Allow: */SiteGlobals/StyleBundles/Bilder/
Allow: */SiteGlobals/StyleBundles/CSS/
Crawl-delay: 180

User-agent: MJ12bot
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: jobs.de-Robot
Disallow: /
User-agent: spbot
Disallow: /
User-agent: JobboerseBot
Disallow: /
User-agent: trendictionbot
Disallow: /
User-agent: Cliqzbot
Disallow: /
User-agent: SeznamBot
Disallow: /
User-agent: Exabot
Disallow: /
User-agent: Mediatoolkitbot
Disallow: /
User-agent: Mail.RU_Bot
Disallow: /
User-agent: Wotbox
Disallow: /
User-agent: AlphaBot
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: YandexMobileBot
Disallow: /
User-agent: SMTBot
Disallow: /
User-agent: rogerbot
Disallow: /
User-agent: YandexImages
Disallow: /
User-agent: Yeti
Disallow: /
User-agent: linkdexbot
Disallow: /
User-agent: SEOkicks-Robot
Disallow: /
User-agent: YaK
Disallow: /
User-agent: MojeekBot
Disallow: /
User-agent: wonderbot
Disallow: /
User-agent: YandexAntivirus
Disallow: /
User-agent: vebidoobot
Disallow: /
User-agent: Pinterestbot
Disallow: /
User-agent: TweetmemeBot
Disallow: /
User-agent: changedetection
Disallow: /
User-agent: SafeDNSBot
Disallow: /
User-agent: yacybot
Disallow: /
User-agent: Buck
Disallow: /
User-agent: SemrushBot-SA
Disallow: /
User-agent: SemrushBot-BA
Disallow: /
User-agent: SemrushBot-BM
Disallow: /
User-agent: Grobbot
Disallow: /
User-agent: Baiduspider-render
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: Flamingo_SearchEngine
Disallow: /
User-agent: MegaIndex.ru
Disallow: /
User-agent: Mega-Index
Disallow: /

Sitemap: http://www.bundesfinanzministerium.de/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 2168 entries Valid XML Yes
Sample URLs:
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.bundesfinanzministerium.de/
200https://bundesfinanzministerium.de/

Preferred variant: non-www

HTTP → HTTPS

302http://bundesfinanzministerium.de/ → https://bundesfinanzministerium.de:443/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
bundesfinanzministerium.de — hosted on RADWARE, IL
PASS
bundesfinanzministerium.de — hosted on RADWARE, IL
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: RADWARE, IL
Got: AS48851
Domain expiry

Unknown

SSL certificate

216 days

Issued by Deutsche Telekom Security GmbH

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

RADWARE, IL

ASN AS48851

66.6.22.209

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 66.6.22.209
ASN AS48851 (RADWARE, IL)
Provider RADWARE, IL
Data source: whois (0.9s)

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

Connection waterfall

DNS Lookup 54 ms TCP Connect 29 ms TLS Handshake 39 ms Server Processing 114 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