Skip to content
https://arte.tv

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1272 ms total
FIX
2 redirect(s), 1272 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
Warning::
Redirect overhead: 1272 ms total
Got: 1272 ms

https://arte.tv

468 ms · HTTP/1.1

301

https://www.arte.tv/

630 ms · HTTP/1.1

301

https://www.arte.tv/en/

173 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://arte.tv301468 msHTTP/1.1Varnish
2https://www.arte.tv/301630 msHTTP/1.1Varnish
3https://www.arte.tv/en/200173 msHTTP/1.1Varnish

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

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
Crawlability
Action
robots.txt present, sitemap with 13 URLs
REVIEW
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 103 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 103 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
# Version: .0
# Real humans, replicants and robots are not allowed to enter

User-agent: *
Disallow: /

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, 30 ms lookup
PASS
1 A records, 30 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.40.38.97
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: sec2.rcode0.net, sec1.rcode0.net, dns1.sdv.fr, dns2.sdv.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
Info::
DNS resolution time: 30 ms
Got: 30 ms
A34.40.38.97
AAAA
CNAME
NSsec2.rcode0.net, sec1.rcode0.net, dns1.sdv.fr, dns2.sdv.fr
MX
10 de-smtp-inbound-1.mimecast.com
10 de-smtp-inbound-2.mimecast.com
TXT
SPF v=spf1 include:spf.protection.outlook.com include:de._netblocks.mimecast.com -al...
openai-domain-verification=dv-6cdE0C3x9TjGKZifbLpyC2HU
google-site-verification=6yYATCeWamOTG0WYCrFNapLThWsuNNfG-Y5fORXwVxA
linkedin-site-verification=96b2ae90-7b3f-4958-955e-27828104d97b
6082fe991b8f43d52bbed196ceaf6cf5718af4b8653b7649f443a6183a249769
bw=MPFiYNQceJwwesRAOssHUbVwmBudL5nIRXtQ9EiAKUyQ
apple-domain-verification=1xbyf7jWyxBVqUYf
atlassian-domain-verification=UO9rlNNhuvvruI8N3MkSssSGzFdqNhRyH20XQktQYxxoPaS6uS...
o0zBOP6rX578IuQEtwRgqkAaeR+5X8eqkbavmnVQ/TdJDxiT0D6PuKHIebxIfdt0g4JSlQ0TQOWBWW4u...
google-site-verification=dHPuZ5Mdf69d_Evo-qtucFyN0LrezyV8-soP8ivK-tA
466A27AD35C68FC3ECD1AF429ADCB749FF8D9F09
google-gws-recovery-domain-verification=46571573
atlassian-domain-verification=wJYfJmzvKtTC2CaMd4cACh01LdbqjPasKtchBM8OSzYpH/R5Wr...
CAALookup not available with standard resolver
Resolved in 30 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+
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

301https://www.arte.tv/
200https://arte.tv/

Preferred variant: non-www

HTTP → HTTPS

301http://arte.tv/ https://www.arte.tv/

Consistent

A+
Domain Intelligence
arte.tv — via Gandi SAS, 22 years, 3 months old, hosted on Google Cloud
PASS
arte.tv — via Gandi SAS, 22 years, 3 months old, hosted on Google Cloud
Info::
Domain registered until Apr 27, 2027 (1 years remaining)
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: Gandi SAS
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

285 days

April 27, 2027

SSL certificate

66 days

Issued by Corporation Service Company

Domain age

22 years, 3 months

Registered April 27, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.40.38.97

Registrar

Gandi SAS

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry 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 Gandi SAS
Created April 27, 2004 (22 years, 3 months ago)
Expires April 27, 2027 (1 years)
Last Updated January 25, 2026
Name Servers sec2.rcode0.net, dns1.sdv.fr, dns2.sdv.fr, sec1.rcode0.net
DNSSEC Not enabled
Hosting
IP Address 34.40.38.97
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
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 774 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
304 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
156 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
159 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
774 ms
Total Time Total request time from DNS lookup through full response.
774 ms

Connection waterfall

DNS Lookup 304 ms TCP Connect 156 ms TLS Handshake 159 ms Server Processing 156 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