Header present, long max-age
The strong result. Browsers that have visited once will insist on HTTPS for the host until the instruction expires. A max-age of 31536000 means one year.
Free tool · Security
HSTS tells browsers to always open your site over HTTPS, the secure version, even if someone types the old http address. DotMoose own site sends it: dotmoose.com returns Strict-Transport-Security with max-age=31536000 and includeSubDomains. This check builds the exact test for your domain, so you can see whether yours sends it too.
Result
Links re-run the check live.
How to read the result
The strong result. Browsers that have visited once will insist on HTTPS for the host until the instruction expires. A max-age of 31536000 means one year.
HSTS is switched on but the instruction expires quickly, so the protection lapses between visits. A short value is a sensible first step while HTTPS is being proven. It is not the finished state.
The site may have perfect HTTPS and still send no instruction, so a browser can be sent to the plain HTTP version first and intercepted there. Adding the header closes that gap. A missing header says nothing about whether the site has a certificate.
includeSubDomains extends the rule to every subdomain, which is only safe once they all serve HTTPS. Preload is a separate browser list a site applies to join, so browsers enforce HTTPS from the very first visit. This check reports the header your site sends; joining the preload list is a further, deliberate step.
Common problems
The bare domain sends it and the www version does not, or the other way round. Browsers learn the rule per host, so every version of the site needs to send it.
Browsers ignore a Strict-Transport-Security header received on an unencrypted answer, for good reason: anyone could have inserted it. It only counts on the HTTPS response.
A max-age of 0 is the off switch. It tells browsers to forget the instruction, and it sometimes survives in a configuration long after the test that put it there.
includeSubDomains plus a long max-age will lock visitors out of any subdomain that cannot serve HTTPS yet. Prove every subdomain first, then include them.
The fuller explanation, including what HSTS does not protect against, is in our guide to HSTS on shared and WordPress hosting.
Questions
HSTS stands for HTTP Strict Transport Security. It is a line a website sends back with its secure pages telling browsers: only ever load this site over HTTPS. Once a browser has seen it, it refuses plain HTTP for the site until the instruction expires, which closes the gap where a first visit or a typed address can be intercepted on the unencrypted version.
No. HSTS protects the HTTPS you already have. The certificate and the encrypted connection do the work; the header is the instruction that makes browsers insist on using them.
max-age is counted in seconds, and 31536000 is one year. A long value is the goal once HTTPS works everywhere on the host. Many sites raise it in steps, because a long instruction sent while some page still needs plain HTTP will lock visitors out of that page.
Yes. Every DotMoose Shared and Managed WordPress site serves the Strict-Transport-Security header by default, with a one year max-age and includeSubDomains. Run this check on any hosted domain and you will see it in the result.
Related checks
Every DotMoose Shared and Managed WordPress site serves the Strict-Transport-Security header by default. Shared hosting starts at C$5.99 a month, flat at renewal, and free assisted migration is included with every plan: we copy your site and email, you see the copy and approve it before anything changes, and your current site stays online the whole time.
Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.