statefarm.com

Readiness by lane

Green: statefarm.com. Thin bar: Insurance & Financial Planning peer median.

Priority fixes for statefarm.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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   60% of Insurance & Financial Planning 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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   43% of Insurance & Financial Planning peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   51% of Insurance & Financial Planning peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from DigiCert Inc had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   29% of Insurance & Financial Planning peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What statefarm.com already does well

Practices fewer than half of Insurance & Financial Planning peers use.

• security.txt publishedsecurity.txt with a contact found.9.9% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, digicert.com and others.15% of peers
• HTTP/3 advertisedHTTP/3 advertised.18% of peers

What we saw

Homepage checked

https://www.statefarm.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-08

Platform or framework

Next.js, Adobe Experience Manager

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 183 days

DMARC policy

p=reject

Homepage HTML

355 KB, gzip

Images on homepage

41 (webp 48, png 3)

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 Insurance & Financial Planning sites

• ameritas.com82
• aok.de82
• asurion.com82
• axa.fr81
• tsp.gov82

Insurance & Financial Planning readiness benchmark