Warning

HSTS max-age is under a year

The short version

Raise max-age to 31536000 once HTTPS works everywhere.

What it means

Your site sends HSTS, but its max-age is shorter than one year (31,536,000 seconds). The detail shows the value we saw. Browsers forget the rule after that time unless the visitor returns.

Why it matters

A short max-age is fine while testing, but in production it means occasional visitors fall back to plain HTTP for their first request after the rule expires. The HSTS preload list also requires at least a year.

How to fix it

  1. Check that every page, image and script on the site loads over HTTPS.
  2. If you add includeSubDomains, check every subdomain too.
  3. Raise the value step by step if you are cautious: a week, a month, then max-age=31536000.
  4. Keep sending the header on every HTTPS response so returning visitors refresh it.

Check it worked

Run the HTTP and security headers check again. The HSTS row should say browsers remember HTTPS for a year or more, and the finding should be gone.