Skip to content
https://mdr.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from New York, United Stated
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1398 ms total
FIX
2 redirect(s), 1398 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://mdr.de
Warning::
Redirect overhead: 1398 ms total
Got: 1398 ms

https://mdr.de

502 ms · HTTP/1.1

302

https://www.mdr.de/

469 ms · HTTP/1.1

302

https://www.mdr.de/home/index.html

427 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mdr.de302502 msHTTP/1.1
2https://www.mdr.de/302469 msHTTP/1.1
3https://www.mdr.de/home/index.html200427 msHTTP/1.1Apache

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

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

C
TLS Certificate Expiry & Recommendations
Action
15 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

15
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 15 days remaining
  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 200 ms lookup
PASS
1 A records, 200 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.22.36.128
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: news.uni-leipzig.de, hinkelstein2.mdr.de, deneb.dfn.de, hinkelstein.mdr.de
Info::
1 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
Warning::
DNS resolution is slow (200 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 200 ms
A193.22.36.128
AAAA—
CNAME—
NSnews.uni-leipzig.de, hinkelstein2.mdr.de, deneb.dfn.de, hinkelstein.mdr.de
MX
50 mdr-de.mail.protection.outlook.com
TXT
MS=D52204395B54B8B5A318CD163CA4DE8AE0B9E95A
SPF v=spf1 include:spf.mailjet.com mx ip4:193.22.38.208 ip4:193.22.38.102 ip4:193.22...
apple-domain-verification=J0yuzFV6I1rnCIbz
HARICA-qKL8wXVW8e4dbSoJtqX
adobe-idp-site-verification=6cbe650e-3a64-4581-bdfc-9b3c7589a607
_skcm5cag6m61k9gssldv84mbdzze4mq
KbN5J07Yk+IXEgg7DjsDcS83C0a9erBXQQhWEX+r8+y6pC5plYzz2FQBPX0Na1mXurfKQYgBx3+GdXn+...
google-site-verification=Qhbbe-tipZqafNBwnrP3D5P0odm3vI4c0Lj6VaKzwLY
CAALookup not available with standard resolver
Resolved in 200 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 20 URLs
PASS
robots.txt present, sitemap with 20 URLs
Info::
robots.txt is present
Got: 2927 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
Sitemap index with 20 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2927 B Sitemaps referenced 2 User-agents anthropic-ai, Claude-SearchBot, DiffBot, DuckAssistBot, Meta-ExternalFetcher, ChatGPT-User, Scrapy, Amazonbot, Applebot-Extended, PetalBot, meta-externalagent, FacebookBot, omgilibot, Webzip, HTTrack, CCBot, Google-Extended, PerplexityBot, Webwhacker, WebSauger, claude-web, cohere-ai, Teleport, Net Attache, WebCapture, TikTokSpider, PanguBot, Webzio-Extended, YouBot, Claude-User, Bytespider, cohere-training-data-crawler, SiteSnagger, *, ClaudeBot, MistralAI-User, GPTBot, OAI-SearchBot, ChatGPT-User/2.0, Perplexity-User, omgili Blocking No — crawling allowed
############ Liste der geblockten KI-Bots
# Stand: 13.05.2025
# Liste an Crawler (Modul SEO ARD)
# Amazon
User-agent: Amazonbot
Disallow: /
# Anthropic
User-agent: anthropic-ai
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-User
Disallow: /
User-agent: Claude-SearchBot
Disallow: /
User-agent: claude-web
Disallow: /
# Apple
User-agent: Applebot-Extended
Disallow: /
# ByteDance
User-agent: Bytespider
Disallow: /
User-agent: TikTokSpider
Disallow: /
# Cohere
User-agent: cohere-ai
Disallow: /
User-agent: cohere-training-data-crawler
Disallow: /
# Common Crawl
User-agent: CCBot
Disallow: /
# Diffbot
User-agent: DiffBot
Disallow: /
# DuckDuckGo
User-agent: DuckAssistBot
Disallow: /
# Google
User-agent: Google-Extended
Disallow: /
# Huawei
User-agent: PetalBot
Disallow: /
User-agent: PanguBot
Disallow: /
# Meta
User-agent: meta-externalagent
Disallow: /
User-agent: Meta-ExternalFetcher
Disallow: /
User-agent: FacebookBot
Disallow: /
# Mistral
User-agent: MistralAI-User
Disallow: /
# OpenAI
User-agent: ChatGPT-User
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: OAI-SearchBot
Disallow: /
User-agent: ChatGPT-User/2.0
Disallow: /
# Perplexity
User-agent: PerplexityBot
Disallow: /
User-agent: Perplexity-User
Disallow: /
# Webz.io
User-agent: omgili
Disallow: /
User-agent: omgilibot
Disallow: /
User-agent: Webzio-Extended
Disallow: /
# You.com
User-agent: YouBot
Disallow: /
# Zyte
User-agent: Scrapy
Disallow: /
############
User-agent: Teleport
Disallow: /
User-agent: Webwhacker
Disallow: /
User-agent: Webzip
Disallow: /
User-agent: Net Attache
Disallow: /
User-agent: SiteSnagger
Disallow: /
User-agent: HTTrack
Disallow: /
User-agent: WebCapture
Disallow: /
User-agent: WebSauger
Disallow: /
User-agent: *
Disallow: /*.xml$
Disallow: /404/
Disallow: /administratives/
Disallow: /export/
Disallow: /forum/
Disallow: /kultur/rueckblick/
Disallow: /medienproduktion/
Disallow: /schulung/
Disallow: /test/
Disallow: /*-shorturl.json$
Disallow: /*-shorturl*.json$
Disallow: /*~fbia.html$
Disallow: /mediathek/mediathek-suche--100_zc-*.html*
Disallow: /mediathek/suche/mediathek-suche--100-default.html?*
Disallow: /mediathek/audio-app/
Disallow: /video/audio-app/
Disallow: /resources/global/player/embed/
Disallow: /mediathek/verbreitung/portal/
Disallow: /video/verbreitung/portal/
Disallow: /yourls/
Disallow: /scripts4/
Disallow: /chat/login.php
Disallow: /CONT/teletext/*
Disallow: /quizzes/
Allow: /scripts4/tippspiel/$
Allow: /*-podcast.xml$
Allow: /*-rss.xml$
Allow: /*-avFeed.xml$
Allow: /*-sitemap.xml$
Allow: /video/administratives/newestvideositemap-100-mediaRss.xml$
Allow: /video/administratives/newestaudiositemap-100-mediaRss.xml$
Allow: /sitemap-index-100.xml
Allow: /administratives/*.css
Allow: /administratives/*.js
Allow: /administratives/*.png
Allow: /administratives/*.jpg
Sitemap: https://www.mdr.de/news-sitemap.xml
Sitemap: https://www.mdr.de/sitemap-index-100.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 20 entries Valid XML Yes
Child Sitemaps:
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
mdr.de — hosted on DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
PASS
mdr.de — hosted on DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., 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: DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
Got: AS680
Domain expiry

Unknown

SSL certificate

15 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE

ASN AS680

193.22.36.128

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 193.22.36.128
ASN AS680 (DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE)
Provider DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
Data source: whois (0.6s)

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

Connection waterfall

DNS Lookup 241 ms TCP Connect 99 ms TLS Handshake 202 ms Server Processing 99 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