Warning

The HSTS header isn't valid

The short version

Send one Strict-Transport-Security header with a numeric max-age.

What it means

Your site sends Strict-Transport-Security, but browsers can't use it as written: max-age is missing or not a number, a directive appears twice, or the header is sent more than once, in which case browsers only read the first. The detail lists the problems.

Why it matters

Browsers ignore an HSTS header they can't parse, so the protection you meant to add doesn't exist. Duplicate headers usually come from setting HSTS in two places, such as both the CDN and the web server, with different values.

How to fix it

  1. Send exactly one header in this form: Strict-Transport-Security: max-age=31536000; includeSubDomains.
  2. max-age is a plain number of seconds, without quotes, units or spaces inside.
  3. Remove the second source if both the CDN and the server add the header; keep the one you control best.
  4. Leave out preload until you meet the preload list's rules.

Check it worked

Run the HTTP and security headers check again. The HSTS row should show a single value, and the finding should be gone.