Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1881 ms totalFIX
https://free.fr
584 ms · HTTP/1.1
https://www.free.fr/
582 ms · HTTP/1.1
https://www.free.fr/freebox
715 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://free.fr | 301 | 584 ms | HTTP/1.1 | nginx |
| 2 | https://www.free.fr/ | 302 | 582 ms | HTTP/1.1 | nginx |
| 3 | https://www.free.fr/freebox | 200 | 715 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
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)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BTLS Certificate Expiry & Recommendations90 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records1 A records, 164 ms lookupPASS
| A | 212.27.48.10 |
| AAAA | 2a01:e0c:1::1 |
| CNAME | — |
| NS | freens3-scw.free.fr, freens1-g20.free.fr, freens2-g20.free.fr |
| MX | 10 mx1.free.fr 20 mx2.free.fr |
| TXT | google-site-verification=t11beEEtTGbjTRaHIR3ZAde9bcpIueH4i3Qn0orBExQ SPF v=spf1 include:_spf.free.fr ~all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 354 URLsPASS
User-Agent: Googlebot
User-Agent: Googlebot-Image
User-Agent: Mediapartners-Google
User-Agent: Googlebot-News
User-Agent: Googlebot-Video
User-Agent: AdsBot-Google
User-Agent: AdsBot-Google-Mobile
User-Agent: AdsBot-Google-Mobile-Apps
User-Agent: Storebot-Google
User-Agent: Bingbot
User-Agent: AdIdxBot
User-Agent: DuckDuckBot
User-Agent: Slurp
User-Agent: Qwantify
User-Agent: Pinterest
Allow: /
User-Agent: *
Disallow: /freebox/informations/avis-freebox/?page=
Allow: /freebox/informations/avis-freebox/?page=1
Disallow: /apps/
Disallow: /*contentOnly*
User-Agent: buenibot
Disallow: /
User-Agent: EtaoSpider
Disallow: /
User-Agent: Yandex
Disallow: /
User-Agent: Baiduspider
Disallow: /
User-Agent: Baiduspider-image
Disallow: /
User-Agent: 360Spider
Disallow: /
User-Agent: MJ12bot
Disallow: /
User-Agent: CazoodleBot
Disallow: /
User-Agent: HaosouSpider
Disallow: /
User-Agent: ia_archiver
Disallow: /
User-Agent: Wget
Disallow: /
User-Agent: TurnitinBot
Disallow: /
User-Agent: HTTrack
Disallow: /
Sitemap: https://www.free.fr/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefree.fr — via SCALEWAY, 27 years, 5 months old, hosted on PROXAD, FRPASS
558 days
December 23, 2027
90 days
Issued by DigiCert Inc
27 years, 5 months
Registered March 15, 1999
Status unknown
Protects against DNS spoofing
PROXAD, FR
ASN AS12322
212.27.48.10
SCALEWAY
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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