Skip to content
https://ndr.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 Singapore, Singapore
302 Found
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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.ndr.de/
200https://ndr.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://ndr.de/ https://www.ndr.de:443/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

66
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, 8 ms lookup
PASS
1 A records, 8 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.120.212.72
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: ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com
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
Info::
DNS resolution time: 8 ms
Got: 8 ms
A34.120.212.72
AAAA
CNAME
NSns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com
MX
0 ndr-de.mail.protection.outlook.com
TXT
facebook-domain-verification=x159mgan9crfavdpk2v0vce38bb9lg
MS=ms28619877
d365mktkey=gi5K6PQgXGwAfsO5aS9FPtcm7QzvPsJ4Pl6ehbLikIQx
NhQ/677HBcNBEIR+gnl++KRSuwpmDhYJRxM7/mUzghCZiapJrmMU+qMdBfDhNcxtCNRrgLByw3+dXUFN...
SPF v=spf1 ip4:194.113.141.20 include:spf.protection.outlook.com include:spf.ndr.de ...
miro-verification=ed3cad95eac9bbd2580e05f99d4c5d8586c1dda4
atlassian-domain-verification=gkV/MyNeBulRCud7iJVxcnS8Je9mui6WRp25WLobRklwp48gzl...
google-site-verification=iwVoxBMq7hRa0iYCxPieWtC-s7fyJGBT3fWvIxGUe1M
CAALookup not available with standard resolver
Resolved in 8 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), 612 ms total
PASS
1 redirect(s), 612 ms total
Info::
Single redirect
Got: https://ndr.de → https://www.ndr.de:443/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://ndr.de
Info::
Redirect overhead: 612 ms total
Got: 612 ms

https://ndr.de

12 ms · HTTP/1.1

302

https://www.ndr.de:443/

600 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ndr.de30212 msHTTP/1.1
2https://www.ndr.de:443/200600 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

A+
Crawlability
robots.txt present, sitemap with 359 URLs
PASS
robots.txt present, sitemap with 359 URLs
Info::
robots.txt is present
Got: 2494 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 359 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2494 B Sitemaps referenced 12 User-agents CCBot, meta-externalagent, Meta-ExternalFetcher, ChatGPT-User, OAI-SearchBot, Scrapy, DuckAssistBot, Google-Extended, PanguBot, claude-web, omgili, *, Amazonbot, GPTBot, omgilibot, YouBot, ChatGPT-User/2.0, Claude-SearchBot, Bytespider, DiffBot, PetalBot, MistralAI-User, Perplexity-User, anthropic-ai, ClaudeBot, FacebookBot, PerplexityBot, Webzio-Extended, Claude-User, Applebot-Extended, TikTokSpider, cohere-ai, cohere-training-data-crawler Blocking No — crawling allowed
Sitemap: https://www.ndr.de/news-102~news.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--info--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--niedersachsen--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--schleswig--holstein--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--mecklenburg--vorpommern--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--hamburg--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--ratgeber--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--sport--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--kultur--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--geschichte--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--fernsehen--100.xml
Sitemap: https://www.ndr.de/index~sitemap_f-sitemap--ndr--weitere--100.xml

User-agent: *
Disallow: /n-joy/appmedien
Disallow: /*ut*.xml
Disallow: /*podcast5654.xml
Disallow: /*.json
Disallow: /ratgeber/*?filter=
Disallow: /*~player.html
Disallow: /*~ardplayer.html

############

# 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: /


A+
Domain Intelligence
ndr.de — hosted on Google Cloud
PASS
ndr.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

66 days

Issued by Google Trust Services

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.120.212.72

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

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 2 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