Skip to content
https://louvre.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
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
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2001:a88:8:10::90, 2001:a88:8:10::80
Info::
IPv6 connection error
Got: dial tcp6 [2001:a88:8:10::90]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2001:a88:8:10::90, 2001:a88:8:10::80 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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), 1004 ms total
REVIEW
1 redirect(s), 1004 ms total
Info::
Single redirect
Got: https://louvre.fr → https://www.louvre.fr/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1004 ms total
Got: 1004 ms

https://louvre.fr

529 ms · HTTP/1.1

301

https://www.louvre.fr/

475 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://louvre.fr301529 msHTTP/1.1wadp2
2https://www.louvre.fr/200475 msHTTP/1.1wadp2

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

280
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
2 A records, 145 ms lookup
PASS
2 A records, 145 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 195.157.4.140, 195.157.4.130
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2001:a88:8:10::90, 2001:a88:8:10::80
Info::
3 nameserver(s) configured
Got: ns2.fr.claradns.net, ns0.fr.claradns.net, ns1.fr.claradns.net
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: 145 ms
Got: 145 ms
A195.157.4.140, 195.157.4.130
AAAA2001:a88:8:10::90, 2001:a88:8:10::80
CNAME—
NSns2.fr.claradns.net, ns0.fr.claradns.net, ns1.fr.claradns.net
MX
1 d349869a.ess.barracudanetworks.com
1 d349869b.ess.barracudanetworks.com
TXT
SPF v=spf1 a ip4:89.185.38.128/28 ip4:89.185.38.135/32 ip4:89.185.38.200/29 ip4:78.1...
MS=ms46938011
google-site-verification=2Y5RJkNMxo9M98WG1Nc1GdaI6Pt13aUTYizD9NI5q_s
teamviewer-sso-verification=2b4692338519425695cef641d1bce041
CAALookup not available with standard resolver
Resolved in 145 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 2852 URLs
PASS
robots.txt present, sitemap with 2852 URLs
Info::
robots.txt is present
Got: 1067 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2852 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 1067 B Sitemaps referenced 0 User-agents Bytespider, Applebot, *, anthropic-ai, ClaudeBot, Sogou web spider, Google-Extended, GPTBot, ChatGPT-User, CCBot, Amazonbot Blocking No — crawling allowed
User-agent: *
Disallow: /*?uuid=*&preview=*
Disallow: /*?*preview=*


# Bloque les IA

User-agent: GPTBot
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: ChatGPT-User
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: anthropic-ai
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: ClaudeBot
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: CCBot
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: Amazonbot
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: Bytespider
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: Applebot
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: Sogou web spider
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$

User-agent: Google-Extended
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.png$
Disallow: /*.webp$
sitemap.xml 200 OK
Type URL Set URLs 2852 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
louvre.fr — via GANDI, 31 years, 2 months old, hosted on CLARANET-AS ClaraNET LTD, GB
PASS
louvre.fr — via GANDI, 31 years, 2 months old, hosted on CLARANET-AS ClaraNET LTD, GB
Info::
Domain registered until Dec 30, 2026 (8 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.
Info::
Hosting: CLARANET-AS ClaraNET LTD, GB
Got: AS8426
Domain expiry

166 days

December 30, 2026

SSL certificate

280 days

Issued by Gandi

Domain age

31 years, 2 months

Registered July 16, 1995

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CLARANET-AS ClaraNET LTD, GB

ASN AS8426

195.157.4.130

Registrar

GANDI

Unlocked 3 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 July 16, 1995 (31 years, 2 months ago)
Expires December 30, 2026 (8 months)
Last Updated December 7, 2025
Name Servers ns0.fr.claradns.net, ns1.fr.claradns.net, ns2.fr.claradns.net
Registrant ETABLISSEMENT PUBLIC DU MUSEE DU LOUVRE
Hosting
IP Address 195.157.4.130
ASN AS8426 (CLARANET-AS ClaraNET LTD, GB)
Provider CLARANET-AS ClaraNET LTD, GB
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

A
HTTP Probe Timing
Total 532 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
139 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
129 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
134 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
533 ms
Total Time Total request time from DNS lookup through full response.
533 ms

Connection waterfall

DNS Lookup 139 ms TCP Connect 129 ms TLS Handshake 134 ms Server Processing 131 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