sncf-connect.com

Readiness by lane

Green: sncf-connect.com. Thin bar: Trains & Public Transport peer median.

Priority fixes for sncf-connect.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

   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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   41% of Trains & Public Transport 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

   Modern image formats in use

   Observed: The homepage had 33 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 Cloudflare: Cloudflare Polish can convert images to WebP.

   28% of Trains & Public Transport peers do this.

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

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   28% of Trains & Public Transport peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   9.5% of Trains & Public Transport peers do this.

   Guide: A Practical Website Health Check for Owners

What sncf-connect.com already does well

Practices fewer than half of Trains & Public Transport peers use.

• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Structured data presentJSON-LD structured data found.33% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers

What we saw

Homepage checked

https://www.sncf-connect.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-03

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Amazon Route 53, plus 3 self-run or other nameserver domains

HSTS

max-age 183 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

661 KB, br

Images on homepage

33 (png 12, jpg 11, svg 10)

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 Trains & Public Transport sites

• aguiabranca.com.br77
• confirmtkt.com77
• kogda.by78
• mta.info78
• railmitra.com78

Trains & Public Transport readiness benchmark