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.
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 & Recommendations183 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, 38 ms lookupPASS
| A | 217.70.184.55 |
| AAAA | — |
| CNAME | — |
| NS | ns-7-b.gandi.net, ns-122-c.gandi.net, ns-176-a.gandi.net |
| MX | 10 mx03.cloud.vadesecure.com 10 mx04.cloud.vadesecure.com 10 mx02.cloud.vadesecure.com 10 mx01.cloud.vadesecure.com |
| TXT | SPF v=spf1 a mx ptr ip4:160.92.27.25 ip4:160.92.25.65 ip4:160.92.25.201 ip4:160.92.3... globalsign-domain-verification=111678c40af589342c6f1fdc61665c18 |
| 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.
ARedirect Chain1 redirect(s), 214 ms totalPASS
https://gouvernement.fr
52 ms · HTTP/1.1
https://www.info.gouv.fr/
163 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://gouvernement.fr | 301 | 52 ms | HTTP/1.1 | |
| 2 | https://www.info.gouv.fr/ | 403 | 163 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 17 URLsPASS
User-agent: *
# Pages techniques
Disallow: /demo/
Disallow: /api/
Disallow: /*_Incapsula*
Disallow: /*recherche?
# Paramètres
Disallow: /*?fbclid=*
Disallow: /*?geolevel=*
Disallow: /*&thematic=*
Disallow: /*&c=*
#Disallow: /*?mission=*
Disallow: /*?parent=*
Disallow: /*&ref=*
Disallow: /*?utm_*
Disallow: /*?date_filter*
Disallow: /*?egn-publisher=*
Disallow: /*?at_creation=*
Disallow: /*?55pushSuggestion=*
Disallow: /*?xtor=*
Disallow: /*?wpmobileexternal=*
Disallow: /*?category=*
Disallow: /*?_hsenc=*
Disallow: /*?url=*
Disallow: /*?sort=*
Disallow: /*?text_size=*
Disallow: /*?filter=*
Disallow: /*?politique_publique=*
Disallow: /*?limit=*
Disallow: /*?end_date=*
Disallow: /*?ead-publisher=*
Disallow: /*?gclid=*
Disallow: /*?tid_1=*
Disallow: /*?subid=*
# Sitemaps
Sitemap: https://www.info.gouv.fr/sitemap.xml
Sitemap: https://www.info.gouv.fr/articles-sitemap.xml
Sitemap: https://www.info.gouv.fr/reports-sitemap.xml
Sitemap: https://www.info.gouv.fr/speechs-sitemap.xml
Sitemap: https://www.info.gouv.fr/ministers_councils-sitemap.xml
Sitemap: https://www.info.gouv.fr/press_packs-sitemap.xml
Sitemap: https://www.info.gouv.fr/projects-sitemap.xml
Sitemap: https://www.info.gouv.fr/pages-sitemap.xml
Sitemap: https://www.info.gouv.fr/ministries-sitemap.xml
Sitemap: https://www.info.gouv.fr/personalities-sitemap.xml
Sitemap: https://www.info.gouv.fr/crises-sitemap.xml
Sitemap: https://www.info.gouv.fr/static_pages-sitemap.xml
Sitemap: https://www.info.gouv.fr/results-sitemap.xml
Sitemap: https://www.info.gouv.fr/engagements-sitemap.xml
Sitemap: https://www.info.gouv.fr/launch_stories-sitemap.xml
Sitemap: https://www.info.gouv.fr/organisations-sitemap.xml
Sitemap: https://www.info.gouv.fr/local_priority_policies-sitemap.xml
Sitemap: https://www.info.gouv.fr/custom-list-pages-sitemap.xml
- https://www.info.gouv.fr/articles-sitema...
- https://www.info.gouv.fr/reports-sitemap...
- https://www.info.gouv.fr/speechs-sitemap...
- https://www.info.gouv.fr/ministers_counc...
- https://www.info.gouv.fr/press_packs-sit...
- https://www.info.gouv.fr/projects-sitema...
- https://www.info.gouv.fr/pages-sitemap.x...
- https://www.info.gouv.fr/ministries-site...
- https://www.info.gouv.fr/personalities-s...
- https://www.info.gouv.fr/crises-sitemap....
- https://www.info.gouv.fr/static_pages-si...
- https://www.info.gouv.fr/results-sitemap...
- https://www.info.gouv.fr/engagements-sit...
- https://www.info.gouv.fr/launch_stories-...
- https://www.info.gouv.fr/organisations-s...
- https://www.info.gouv.fr/local_priority_...
- https://www.info.gouv.fr/custom-list-pag...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
ADomain Intelligencegouvernement.fr — via GANDI, 22 years, 10 months old, hosted on GANDI-AS Domain name registrar - www.gandi.net, FRPASS
EXPIRED
June 21, 2026
183 days
Issued by Gandi SAS
22 years, 10 months
Registered September 28, 2003
Status unknown
Protects against DNS spoofing
GANDI-AS Domain name registrar - www.gandi.net, FR
ASN AS29169
217.70.184.55
GANDI
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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