Skip to content
https://www.service-public.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Santa Clara, United Stated
301 Moved Permanently
Checks
9
3 PASS 5 REVIEW 1 FIX
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
DNS Records
Action
1 A records, 870 ms lookup
REVIEW
1 A records, 870 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 160.92.168.33
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: secure-www-sp-dila-prod.as8677.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (870 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 870 ms
A160.92.168.33
AAAA—
CNAMEsecure-www-sp-dila-prod.as8677.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 870 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

B
Redirect Chain
1 redirect(s), 1244 ms total
REVIEW
1 redirect(s), 1244 ms total
Info::
Single redirect
Got: https://www.service-public.fr → https://www.service-public.gouv.fr/ (301)
Warning::
Redirect overhead: 1244 ms total
Got: 1244 ms
Info::
Cross-domain redirect detected

https://www.service-public.fr

765 ms · HTTP/1.1

301

https://www.service-public.gouv.fr/

479 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.service-public.fr301765 msHTTP/1.1
2https://www.service-public.gouv.fr/200479 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.service-public.fr/
301https://service-public.fr/

Preferred variant: www

HTTP → HTTPS

http://www.service-public.fr/

HTTP version does not redirect to HTTPS

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

Certificate validity

334
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+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 360 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps
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 360 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /compte/*
Disallow: /contact/*
Disallow: /actualites/lettresp/archives/L*
Disallow: /allo-sp/*
Disallow: /accueil/
Disallow: /*?xtor=
# Disallow: */recherche*
Allow: */recherche-guidee/*.js
Allow: /demarches-silence-vaut-accord/recherche?page=
Disallow: */partager-par-courriel
Disallow: /*/personnalisation
Disallow: */telecharger-pdf
sitemap.xml 200 OK
Type Sitemap Index URLs 14 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
service-public.fr — via NAMESHIELD, 25 years, 10 months old, hosted on ING-AS, FR
PASS
service-public.fr — via NAMESHIELD, 25 years, 10 months old, hosted on ING-AS, FR
Warning::
Domain expires in 85 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 29, 2026
Info::
Registrar: NAMESHIELD
Info::
Hosting: ING-AS, FR
Got: AS47957
Domain expiry

EXPIRED

June 29, 2026

SSL certificate

334 days

Issued by Sectigo Limited

Domain age

25 years, 10 months

Registered October 5, 2000

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ING-AS, FR

ASN AS47957

160.92.168.33

Registrar

NAMESHIELD

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
Registrar NAMESHIELD
Created October 5, 2000 (25 years, 10 months ago)
Expires June 29, 2026 (2 months)
Last Updated July 2, 2025
Name Servers ns1.dila.fr, ns2.dila.fr, ns3.dila.fr, ns4.dila.fr
Registrant Etat francais represente par la Direction de l information legale et administrative DILA
Hosting
IP Address 160.92.168.33
ASN AS47957 (ING-AS, FR)
Provider ING-AS, FR
Data source: rdap (0.9s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 288 ms TCP Connect 142 ms TLS Handshake 146 ms Server Processing 169 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