Skip to content
https://deutschlandfunkkultur.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
43 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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, 56 ms lookup
PASS
1 A records, 56 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.117.206.250
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: ns2.vodafone-ip.de, ns1.vodafone-ip.de, auth2.dns.cogentco.com, auth1.dns.cogentco.com
Info::
4 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: 56 ms
Got: 56 ms
A34.117.206.250
AAAA
CNAME
NSns2.vodafone-ip.de, ns1.vodafone-ip.de, auth2.dns.cogentco.com, auth1.dns.cogentco.com
MX
10 mx01.hornetsecurity.com
20 mx02.hornetsecurity.com
30 mx03.hornetsecurity.com
40 mx04.hornetsecurity.com
TXT
MS=ms26464237
cgzwffgs4s8y3xlxzkh6hy263sclq37x
google-site-verification=l7MEE4WhhShq_MYkLlN56aa0csfqijf8NnP_FChT7Lk
facebook-domain-verification=nsm1tvo8x4fb1xlgjwuw0q2si1yieu
SPF v=spf1 ip4:194.31.115.21 ip4:194.45.37.19 mx include:antispameurope.com ~all
5c2t7dn8f6y4kgs9z5xgmcgtkwjfbwvb
rwj582d7plgvp17k4nv6wkzf3k19gqxm
CAALookup not available with standard resolver
Resolved in 56 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), 160 ms total
PASS
1 redirect(s), 160 ms total
Info::
Single redirect
Got: https://deutschlandfunkkultur.de → https://www.deutschlandfunkkultur.de:443/ (301)
Info::
WWW normalization redirect

https://deutschlandfunkkultur.de

69 ms · HTTP/1.1

301

https://www.deutschlandfunkkultur.de:443...

91 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://deutschlandfunkkultur.de30169 msHTTP/1.1
2https://www.deutschlandfunkkultur.de:443...20091 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 100 URLs
PASS
robots.txt present, sitemap with 100 URLs
Info::
robots.txt is present
Got: 335 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 100 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 335 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed
User-agent: *
# print pages always have parameters
Disallow: /*.print?
Disallow: /*play=1
sitemap: https://www.deutschlandfunkkultur.de/filter-heute-neu-104.sitemap
sitemap: https://www.deutschlandfunkkultur.de/filter-heute-neu-audios-102.sitemap
sitemap: https://www.deutschlandfunkkultur.de/podcast-filter-116.sitemap
Crawl-delay: 5

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.deutschlandfunkkultur.de/
200https://deutschlandfunkkultur.de/

HTTP → HTTPS

301http://deutschlandfunkkultur.de/ https://www.deutschlandfunkkultur.de:443/

Consistent

A+
Domain Intelligence
deutschlandfunkkultur.de — hosted on Google Cloud
PASS
deutschlandfunkkultur.de — hosted on Google Cloud
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: Google Cloud
Got: AS396982
Domain expiry

Unknown

SSL certificate

43 days

Issued by Google Trust Services

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.117.206.250

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 34.117.206.250
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (0.7s)

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

Connection waterfall

DNS Lookup 49 ms TCP Connect 17 ms TLS Handshake 32 ms Server Processing 18 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