Skip to content
https://rtl.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
4 PASS 4 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.

B
Redirect Chain
1 redirect(s), 1445 ms total
REVIEW
1 redirect(s), 1445 ms total
Info::
Single redirect
Got: https://rtl.fr → https://www.rtl.fr/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1445 ms total
Got: 1445 ms

https://rtl.fr

1014 ms · HTTP/1.1

301

https://www.rtl.fr/

432 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rtl.fr3011014 msHTTP/1.1
2https://www.rtl.fr/200432 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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.rtl.fr/
200https://rtl.fr/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://rtl.fr/ → https://www.rtl.fr/

Consistent

B
HTTP Probe Timing
Total 814 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
196 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
205 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
208 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
815 ms
Total Time Total request time from DNS lookup through full response.
815 ms

Connection waterfall

DNS Lookup 196 ms TCP Connect 205 ms TLS Handshake 208 ms Server Processing 206 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
50 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

50
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, 504 ms lookup
PASS
1 A records, 504 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.151.191.59
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a0a:1580:2000:4f00::14
Info::
2 nameserver(s) configured
Got: ns.rtl.fr, ns.rtlnet.fr
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
Warning::
DNS resolution is slow (504 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 504 ms
A185.151.191.59
AAAA2a0a:1580:2000:4f00::14
CNAME—
NSns.rtl.fr, ns.rtlnet.fr
MX
10 mx1.m6.fr
10 mx2.m6.fr
TXT
miro-verification=f8df0dbc9f605186abedb068447f67bf4c5325b2
atlassian-domain-verification=RwLwFNtxmrmLKeaZHXL6LKiinX15a5z6rvepLQXJECQlWPmDR8...
perplexity-ai-domain-verification-7eys3n=NauOcuept35tRN8wDLBfzjm83
8p768gypxtj7qdklnjfr9j20dwyr729r
A08MC7F4Ige4mFo+PDAgo6/RxsqRIutD8aazSzGfUgYMTVCAiT7kaeBImYgoFnl19vt5+zrV2BPmK+kX...
MS=ms67132451
google-site-verification=WLS8-hk17p-AWjE0m4mB4PoCb0q4Bmds8eo8J6uGpCA
google-site-verification=ihI_PJrF5TpzKAyfInJXtxpxdhOEhnELX4SWlngHqjw
_globalsign-domain-verification=16aKJufSrMKbcCAKCXzVC4PbCHEMl2CuparSiVEdN9
MS=FAC5D6138683B3405A10BD64C2B90ACFE1357160
cSC0TshaWqMQ9TtYDbM1+wVQRwwTkyH2hlQDTViBdj2Mka9Yh2MD1kdYAEnI2vKysviSuaZJHQ3sFRIZ...
adobe-idp-site-verification=1ab58e56a7c5cfcf85df9cf0e34dc26505b7982a08fd338b7024...
SPF v=spf1 mx ip4:91.208.209.111 ip4:91.208.209.112 ip4:92.61.161.45 include:spf.pro...
CAALookup not available with standard resolver
Resolved in 504 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+
IPv6 Readiness
IPv6 reachable (187 ms)
PASS
IPv6 reachable (187 ms)
Info::
IPv6 is configured and reachable at 2a0a:1580:2000:4f00::14
Got: 187 ms connect
IPv6 Ready
AAAA Records 2a0a:1580:2000:4f00::14 Connection Reachable (187 ms)
A+
Crawlability
robots.txt present, sitemap with 103 URLs
PASS
robots.txt present, sitemap with 103 URLs
Info::
robots.txt is present
Got: 892 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 103 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 892 B Sitemaps referenced 2 User-agents ChatGPT-User, GPTBot, CCBot, Google-Extended, * Blocking No — crawling allowed
# Disable OpenAI bots
User-agent: ChatGPT-User
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: CCBot
Disallow: /
# Disable Google AI bot
User-agent: Google-Extended
Disallow: /

User-agent: *
Disallow: /_header_nav_ajax.html 
Disallow: /emission/laurent-gerra/ecouter/*2010
Disallow: /emission/laurent-gerra/ecouter/*2011
Disallow: /emission/laurent-gerra/ecouter/*janvier-2012
Disallow: /3338/
Disallow: /recherche*
Disallow: /archive/
Disallow: /vote/
Disallow: /partager/
Disallow: /ajax/
Disallow: /outils/
Disallow: /recherche*
Disallow: /connect/
Disallow: /resultats-examens/
Disallow: /widgets*
Disallow: /emploi*
Disallow: /code-promo*
Disallow: */amp
Disallow: /elections-regionales/
Disallow: /elections-departementales/
Disallow: /election-presidentielle/
Disallow: /presidentielle-2022/

Sitemap: https://www.rtl.fr/sitemap-news.xml
Sitemap: https://www.rtl.fr/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 103 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
rtl.fr — via GANDI, 29 years, 5 months old
PASS
rtl.fr — via GANDI, 29 years, 5 months old
Info::
Domain registered until Nov 27, 2026 (7 months remaining)
Info::
Registrar: GANDI
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.
Domain expiry

165 days

November 27, 2026

SSL certificate

50 days

Issued by Let's Encrypt

Domain age

29 years, 5 months

Registered April 9, 1997

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a0a:1580:2000:4f00::14

Registrar

GANDI

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GANDI
Created April 9, 1997 (29 years, 5 months ago)
Expires November 27, 2026 (7 months)
Last Updated November 1, 2025
Name Servers ns.rtl.fr, ns.rtlnet.fr
Registrant METROPOLE TELEVISION
Hosting
IP Address 2a0a:1580:2000:4f00::14
Data source: rdap (0.9s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback