sante.fr

Readiness by lane

Green: sante.fr. Thin bar: Government Services peer median.

Priority fixes for sante.fr

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   51% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 0 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   68% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 64 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Nuxt: Nuxt Image can output WebP and AVIF.

   15% of Government Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What sante.fr already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, letsencrypt.org.17% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers

What we saw

Homepage checked

https://www.sante.fr/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-28

CDN or edge

Imperva

Platform or framework

Drupal, Nuxt

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

228 KB, gzip

Images on homepage

64 (png 40, jpg 22, svg 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Government Services sites

• csc.gov.ph64
• prix-carburants.gouv.fr65
• programasparaelbienestar.gob.mx65
• sam.gov65
• tn.gov65

Government Services readiness benchmark