fcpeuro.com

Readiness by lane

Green: fcpeuro.com. Thin bar: Cars & Automotive peer median.

Priority fixes for fcpeuro.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 1 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 Cars & Automotive 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 3 days, 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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   55% of Cars & Automotive peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Cloudflare: Add the header with a response header transform rule.

   52% of Cars & Automotive peers do this.

   Guide: A Practical Website Health Check for 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.

   8.9% of Cars & Automotive peers do this.

   Guide: A Practical Website Health Check for Owners

What fcpeuro.com already does well

Practices fewer than half of Cars & Automotive peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.7.8% of peers
• HTTP/3 advertisedHTTP/3 advertised.30% of peers
• Content Security Policy presentContent-Security-Policy present.31% of peers

What we saw

Homepage checked

https://www.fcpeuro.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-17

CDN or edge

Akamai

DNS operators

Cloudflare

HSTS

max-age 1 days

DMARC policy

p=quarantine

Homepage HTML

80 KB, gzip

Images on homepage

18 (png 8, jpg 7, gif 1)

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 Cars & Automotive sites

• autoreview.nl82
• dacia.fr82
• kolesa.kz82
• nettimoto.com83
• renault.fr82

Cars & Automotive readiness benchmark