Skip to content
https://bundesgesundheitsministerium.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
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.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://bundesgesundheitsministerium.de/ → https://www.bundesgesundheitsministerium.de//

Consistent

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

Certificate validity

91
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, 60 ms lookup
PASS
1 A records, 60 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.85.0.195
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3-any.123ns.eu, ns1-any.123ns.eu, ns4-any.123ns.de
Info::
2 mail exchanger(s) configured
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: 60 ms
Got: 60 ms
A185.85.0.195
AAAA—
CNAME—
NSns3-any.123ns.eu, ns1-any.123ns.eu, ns4-any.123ns.de
MX
20 mx02.pixelpark.com
20 mx01.pixelpark.com
TXT
did=did:plc:5lvu24jrpdv3upba4zi2gwj7
HARICA-MGcsJuSY6djq4UNdmjN
HARICA-TweoPMLVINLu7TKp7YN
google-site-verification=KJAYLLCiArN_v6deJkReVcWRY_zTSkhBsSBwzLU6JAQ
SPF v=spf1 ip4:45.144.132.136 ip6:2a06:2380:2:1:283d:5aff:feba:4401 include:_spf.pix...
HARICA-QZXxV4uB2ljTS45e42j
CAALookup not available with standard resolver
Resolved in 60 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
Redirect Chain
1 redirect(s), 244 ms total
PASS
1 redirect(s), 244 ms total
Info::
Single redirect
Got: https://bundesgesundheitsministerium.de → https://www.bundesgesundheitsministerium.de// (301)
Info::
WWW normalization redirect

https://bundesgesundheitsministerium.de

101 ms · HTTP/1.1

301

https://www.bundesgesundheitsministerium...

143 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bundesgesundheitsministerium.de301101 msHTTP/1.1myracloud
2https://www.bundesgesundheitsministerium...200143 msHTTP/1.1myracloud

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 815 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 815 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# We do not distinguish between the browsers.

User-agent: *

Allow: /


# Only allow URLs generated with frontend routing

Disallow: /*?id=*

Disallow: /*&id=*


# L=0 is the default language

Disallow: /*?L=0*

Disallow: /*&L=0*


# Should always be protected, but you know...

Disallow: /*/Private/*

Disallow: /*/Configuration/*


# Disallow all files in /typo3/

Disallow: /typo3/


# Disallow all kind of sql files

Disallow: *.sql

Disallow: *.sql.gz


# Folders

Disallow: /fileadmin/BMG_Secure/

Disallow: /typo3conf/

Allow: /typo3conf/ext/*/Resources/Public/

Allow: /typo3temp/


# Parameters

# no cHash

Disallow: /*cHash

# no forms

Disallow: /*tx_form_formframework

# no search result pages

Disallow: /*tx_solr


# Sitemap

Sitemap: https://www.bundesgesundheitsministerium.de/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
bundesgesundheitsministerium.de — hosted on SOPRADO-ANY, DE
PASS
bundesgesundheitsministerium.de — hosted on SOPRADO-ANY, DE
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: SOPRADO-ANY, DE
Got: AS20546
Domain expiry

Unknown

SSL certificate

91 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

SOPRADO-ANY, DE

ASN AS20546

185.85.0.195

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 185.85.0.195
ASN AS20546 (SOPRADO-ANY, DE)
Provider SOPRADO-ANY, DE
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 147 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
30 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
40 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
147 ms
Total Time Total request time from DNS lookup through full response.
147 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 30 ms TLS Handshake 40 ms Server Processing 30 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