Security
HSTS: the header that makes browsers insist on HTTPS
HSTS is a one-line instruction your website sends to every visitor's browser: only ever talk to this site over HTTPS, the encrypted connection, never over plain HTTP. Once a browser has seen that instruction, it refuses to load the unencrypted version of your site at all, even if someone types the address without the https part or clicks an old unencrypted link.
Why that one line matters
The risky moment is the first hop. When a visitor arrives through an unencrypted link, a normal site answers by redirecting them to the secure version. That redirect itself travels unencrypted, and someone sitting between the visitor and your site, on public Wi-Fi for example, can intercept it and send the visitor somewhere else instead. HSTS closes that gap: after the first secure visit, the browser skips the unencrypted step entirely and goes straight to HTTPS, every time, for as long as the instruction lasts.
What the header actually says
The header looks like this: Strict-Transport-Security: max-age=31536000; includeSubDomains. In plain words, the two settings are:
max-age=31536000 means remember this rule for 31,536,000 seconds, which is one year. Browsers refresh the timer on every visit, so regular visitors stay covered continuously.
includeSubDomains means the rule covers subdomains too, addresses like shop.yoursite.ca, not just the main address. That stops the same first-hop trick from being played on a subdomain.
It is on by default here
Every Shared and Managed WordPress site hosted on DotMoose sends this header with exactly those settings, one year and subdomains included. There is nothing to turn on and nothing to pay extra for. It is part of how the shared servers answer HTTPS requests, the same for the smallest Starter site as for any other plan.
How to check your own site
Run your address through our free HSTS checker. It follows your site's responses and reports whether the final secure answer carries the header. If your current host does not send it, the usual fix is one line of server or panel configuration, and it is reasonable to ask them why it is not already on.
What HSTS does not do
HSTS is not a certificate and it does not encrypt anything by itself. Your site still needs a working HTTPS certificate first, and HSTS only starts protecting a visitor after their first secure visit, because the browser has to receive the instruction over a connection it already trusts. It is one small, strict rule layered on top of HTTPS, and it removes a whole category of first-click interception for free.
The next step
If your site is moving to DotMoose, HSTS is already waiting on the other side: Shared hosting starts at C$5.99 a month and Managed WordPress at C$7.99 a month, flat at renewal, and migration is free. 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.