Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Security

HSTS header setup: when to enable it and when to wait

Published August 2026 · 8 min read

HTTP Strict Transport Security is a browser policy that can protect users from being downgraded to HTTP after they have received the header over HTTPS. It is powerful precisely because the browser remembers it, which makes premature configuration risky.

Make HTTPS boring before adding HSTS

Every intended hostname should have valid certificates, reliable renewal, and correct HTTP-to-HTTPS redirects. Fix mixed content and redirect loops before asking browsers to refuse HTTP fallback.

Start with a cautious max-age

A shorter initial policy can reduce the blast radius while you verify production behaviour. Increase duration deliberately after the HTTPS path has proven stable.

Understand includeSubDomains before using it

That directive applies the policy to subdomains too. An old service, third-party hostname, or forgotten subdomain without working HTTPS can become inaccessible to browsers that inherit the policy.

Preload is a separate long-lived decision

Browser preload programs have additional requirements and removal is not immediate. Do not treat preload as a default checkbox; evaluate the entire domain namespace and operational maturity first.

Next step

HSTS tells browsers to use HTTPS for a host. Enable it only after HTTPS, redirects, certificates, renewal, subdomains, and rollback implications are understood.

Read HTTPS guidance

Keep reading

Related guides.

Content Security Policy rollout: build CSP from the resources a site really uses

Inventory scripts, styles, frames and connections, start with reporting, reduce unsafe allowances and enforce CSP only after normal user paths still work.

Read the guide

HSTS rollout planning: enable strict HTTPS without locking in a mistake

Stabilize HTTPS first, choose max-age carefully, cover subdomains deliberately and understand preload consequences before making HSTS hard to reverse.

Read the guide

HTTPS redirect mistakes: loops, chains and host changes that hurt a site

Find conflicting HTTP-to-HTTPS and hostname redirects across proxies, servers and applications, then reduce the path to one intentional canonical destination.

Read the guide

More security guides

We will handle the move. You check it first.

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.

Start my free moveSee plans and prices
See pricesFree move