Strict-Transport-Security max-age is set below 1 year, reducing HTTPS security and HSTS preload eligibility.
By Seoxpert Editorial · Published
A short HSTS max-age weakens HTTPS protection, making users vulnerable to downgrade attacks. Google requires a 1-year minimum for HSTS Preload List inclusion, which can affect site trust and SEO.
Sites remain susceptible to man-in-the-middle attacks and cannot be added to the HSTS Preload List.
The crawler inspects HTTP response headers for Strict-Transport-Security and flags any max-age value below 31536000 seconds.
Incorrect (Too Short)
add_header Strict-Transport-Security "max-age=86400; includeSubDomains; preload" always;Correct (1 Year)
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;Incorrect (Too Short)
Header always set Strict-Transport-Security "max-age=2592000; includeSubDomains; preload"Correct (1 Year)
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"A 1-year max-age ensures persistent protection against downgrade attacks and meets browser preload requirements.
It only extends the period browsers enforce HTTPS; it does not negatively impact users.
Yes, if all subdomains support HTTPS. Otherwise, configure subdomains first before enabling these directives.
Yes, but remember to update to 1 year before submitting for preload or deploying to production.
Run a scan to see if HSTS max-age Too Short affects your pages.
Scan my website →