max-age
The number of seconds a browser remembers the HTTPS-only policy. A one-year value is 31536000 seconds.
Test the Strict-Transport-Security header on any public website. Inspect max-age, includeSubDomains and preload directives, then get a practical configuration review.
HSTS tells a browser to use HTTPS for future requests to a host. The header's directives control how long that rule lasts, whether it extends to subdomains, and whether the site signals an intent to join browser preload lists.
The number of seconds a browser remembers the HTTPS-only policy. A one-year value is 31536000 seconds.
Extends the policy to subdomains. Enable it only when all intended subdomains are ready for HTTPS.
Signals intent to participate in browser preload programs. The directive alone does not mean the domain is actually preloaded.
A commonly used preload-ready form combines a long max-age with both directives.
HSTS can make HTTP-only subdomains unreachable. Before using includeSubDomains or pursuing preload, confirm that the root domain and every affected subdomain can remain on HTTPS. DeployPass checks the observed header; it does not claim that a domain is present in a browser preload list.
HTTP Strict Transport Security is a browser policy delivered through the Strict-Transport-Security response header. It tells supporting browsers to use HTTPS for future requests to the host.
The right rollout depends on your environment. For preload eligibility, a max-age of at least 31536000 seconds is required. Teams often begin more cautiously before committing to a long-lived policy.
No. The directive signals intent. Actual preload-list inclusion has additional requirements and a separate submission process.
It applies the HTTPS-only policy to subdomains too. A legacy or internal subdomain that cannot serve HTTPS can become inaccessible to browsers enforcing the policy.
Yes. Use DeployPass Security Headers Checker for CSP, HSTS, MIME sniffing, framing, Referrer-Policy, CORS and observable cookie signals.