Skip to content
https://telegraaf.nl

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 New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
Redirect Chain
Action
3 redirect(s), 248 ms total
FIX
3 redirect(s), 248 ms total
Warning::
3 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.telegraaf.nl/
Info::
Cross-domain redirect detected

https://telegraaf.nl

19 ms · HTTP/1.1

301

https://www.telegraaf.nl/

26 ms · HTTP/1.1

302

https://login.mediahuis.com/authorize?re...

168 ms · HTTP/1.1

302

https://www.telegraaf.nl/auth/callback/l...

35 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://telegraaf.nl30119 msHTTP/1.1cloudflare
2https://www.telegraaf.nl/30226 msHTTP/1.1cloudflare
3https://login.mediahuis.com/authorize?re...302168 msHTTP/1.1cloudflare
4https://www.telegraaf.nl/auth/callback/l...30235 msHTTP/1.1cloudflare

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
84 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

84
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9f07a4c65fa40aae-EWR
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07a4c65fa40aae-EWR
A+
DNS Records
2 A records, 15 ms lookup
PASS
2 A records, 15 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.34.171, 172.64.153.85
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: donna.ns.cloudflare.com, jeremy.ns.cloudflare.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: 15 ms
Got: 15 ms
A104.18.34.171, 172.64.153.85
AAAA—
CNAME—
NSdonna.ns.cloudflare.com, jeremy.ns.cloudflare.com
MX
100 telegraaf-nl.mail.protection.outlook.com
TXT
1password-site-verification=VH27YL5Q4FHLZOHF36KH4DIEIM
DomainVerification=R7F9QMM0W71A27HK5S6AKQNSS7HFIYXKSX15AQKBO4C0SLCO0UTBXBKKXOA6Q...
MS=ms22962864
adobe-idp-site-verification=2874515d68b0370803179f9e8d6698cb503e00756499a6e7a042...
apple-domain-verification=J8uVvtlYLm2snDYa
astro-domain-verification=cm03y1pyc02bw01m1qxb52ngg
atlassian-domain-verification=6pmXgwnFg97VcZymPBajXWMApgo0EvG3OatYXgfleuo44Klq2a...
google-site-verification=2Vck4Kbphdtv1fZz4vx5mYEwQScwk0GkNj9eylKY4qM
google-site-verification=2qDIwPgi0H5bx2gHtfOQnvuB7OVEE8rqPP6BUmftVY0
google-site-verification=aoLH9RW5wJul08g6VoK8l3u6Nq2CqFFKfhu4jDJZ1cM
google-site-verification=hMWxgzKsacgc6qfNRWaj7Qd0LtBwydNCxEZhSe57b2s
google-site-verification=tdMu6D27Hv8uUwFK_QmKBC3dOyrNitJJlulECchcbyo
ozYu2XydkIf3IGf3TlT1osDmWIAzyIlTEU2Cz7ePj3s=
SPF v=spf1 include:mailswitch.nl include:spf.anachron.com include:amazonses.com ip4:...
x#8YI5kjG7BjrCH9TEkSWkm@DyvROIMrWa%jbfN00z*V%!b4IIqNR6PWEn$8y38Qq#5VwE!5IgtCyUCg...
CAALookup not available with standard resolver
Resolved in 15 ms

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 241 URLs
PASS
robots.txt present, sitemap with 241 URLs
Info::
robots.txt is present
Got: 2024 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 241 entries
Info::
Sitemap index with 241 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2024 B Sitemaps referenced 4 User-agents magpie-crawler, omgili, omgilibot, PerplexityBot, anthropic-ai, ChatGPT-User, ClaudeBot, Diffbot, GPTBot, cohere-ai, meta-externalfetcher, *, Googlebot-News, Bytespider, CCBot, Claude-Web, FacebookBot, meta-externalagent, Amazonbot, Google-Extended Blocking No — crawling allowed
# All copyrights, neighbouring rights and database rights in the content and layout of this website/app are explicitly reserved and are for personal, non-commercial use only. 
# In accordance with Article  4 of the Directive on Copyright in the Digital Single Market (CDSM) and its transposition into the law of the applicable Member State,  
# all content of this website on which it is made available is not to be used for the purposes of text and data mining, extraction, scraping and/or the use of programs or robots
# for automatic data collection and/or extraction of digital data, whether for machine learning or artificial intelligence purposes or otherwise. 
# See also the Terms and Conditions of this website.

# robots.txt prod De Telegraaf
user-agent: *
Allow: /
Allow: /tags

# Disallow Internal Search
Disallow: /zoeken/ 

# Disallow bundle
Disallow: /*?bundle

# Disallow infront widgets
Disallow: /infront/widget/

# Disallow Sponsored Articles for Google News
User-agent: Googlebot-News
Disallow: /branded-content/
Disallow: /brandedcontent/

# Disallow Large Language Models
User-agent: Amazonbot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: PerplexityBot
Disallow: /

# User-agent: Google-CloudVertexBot
# Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: meta-externalfetcher
Disallow: /

#list sitemaps
Sitemap: https://www.telegraaf.nl/sitemap.xml
Sitemap: https://www.telegraaf.nl/sitemap-image.xml
Sitemap: https://www.telegraaf.nl/sitemap-news.xml
Sitemap: https://www.telegraaf.nl/sitemap-video.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 241 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.telegraaf.nl/
200https://telegraaf.nl/

Preferred variant: non-www

HTTP → HTTPS

301http://telegraaf.nl/ → https://www.telegraaf.nl/

Consistent

A+
Domain Intelligence
telegraaf.nl — via Mediahuis TPS, 30 years, 9 months old, hosted on Cloudflare
PASS
telegraaf.nl — via Mediahuis TPS, 30 years, 9 months old, hosted on Cloudflare
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Mediahuis TPS
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: Cloudflare
Got: AS13335
Domain expiry

Unknown

SSL certificate

84 days

Issued by Google Trust Services

Domain age

30 years, 9 months

Registered December 18, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.64.153.85

Registrar

Mediahuis TPS

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Mediahuis TPS
Created December 18, 1995 (30 years, 9 months ago)
Last Updated October 2, 2024
Name Servers donna.ns.cloudflare.com, jeremy.ns.cloudflare.com
DNSSEC Not enabled
Registrant TMG Landelijke Media B.V.
Hosting
IP Address 172.64.153.85
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 6 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 7 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