Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 251 ms totalREVIEW
https://insee.fr
83 ms · HTTP/1.0
https://www.insee.fr/
129 ms · HTTP/1.1
https://www.insee.fr/fr/accueil
40 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://insee.fr | 302 | 83 ms | HTTP/1.0 | BigIP |
| 2 | https://www.insee.fr/ | 301 | 129 ms | HTTP/1.1 | unknown |
| 3 | https://www.insee.fr/fr/accueil | 200 | 40 ms | HTTP/1.1 | unknown |
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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations316 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records1 A records, 45 ms lookupPASS
| A | 194.254.37.163 |
| AAAA | — |
| CNAME | — |
| NS | ns1.insee.fr, nsc.perf1.com, nsb.perf1.com, ns2.insee.fr, nsa.perf1.fr |
| MX | 10 heimdall.insee.fr 20 freyja.insee.fr 30 heimdall2.insee.fr 40 freyja2.insee.fr |
| TXT | google-site-verification=53P2IH4qpas0FyydHON7c4SPIw3tfivf_gQfxIFZWdM SPF v=spf1 ip4:194.254.37.152 ip4:143.196.255.150 ip4:194.254.37.232 ip4:143.196.255... _github-challenge-inseefr ZOOM_verify_1-v6iuNwQ4Od26zPcC_5rA intranet |
| 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 0 URLsPASS
User-agent: *
Disallow: *.xls
Disallow: *.csv
Disallow: *.zip
Disallow: *.xlsx
Disallow: /*/bdm2/
Disallow: /*/ddl/
Sitemap: https://www.insee.fr/sitemap-index.xml
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceinsee.fr — via CSC CORPORATE DOMAINS INC., 30 years, 4 months old, hosted on FR-RENATER Reseau National de telecommunications pour la Technologie, FRPASS
135 days
October 28, 2026
316 days
Issued by Sectigo Limited
30 years, 4 months
Registered May 6, 1996
Enabled
Protects against DNS spoofing
FR-RENATER Reseau National de telecommunications pour la Technologie, FR
ASN AS2200
194.254.37.163
CSC CORPORATE DOMAINS INC.
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