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 rollout planning: enable strict HTTPS without locking in a mistake

Published August 2026 · 2 min read · Updated 2026-09-05

HSTS tells browsers to use HTTPS for a hostname for a period of time. That persistence is why rollout should happen after HTTPS is stable on every covered name. An HSTS error cannot be bypassed by simply asking users to click through a certificate warning.

Stabilize HTTPS and redirects first

Verify valid certificates, complete chains, canonical HTTPS redirects, and renewal automation on the exact host that will send HSTS. Fix mixed HTTP dependencies that users still need.

Do not add HSTS to compensate for an HTTPS setup that is not reliable.

Start with a short max-age

A small max-age limits the blast radius while you confirm real browsers and operational renewal. Increase gradually once you are confident the host will remain HTTPS-only.

Remember browsers that already received the header retain it until their stored max-age expires.

Treat includeSubDomains as a separate commitment

With includeSubDomains, every covered subdomain must support valid HTTPS, including forgotten internal/public services and delegated customer/application names under that hierarchy.

Inventory DNS and certificate ownership before enabling it.

Consider preload only after long-term readiness

Browser preload has stricter requirements and removal can take time. Review the current preload program requirements before publishing preload headers. Document who owns certificate renewal for every included hostname before making that commitment.

  • Make HTTPS reliable first.
  • Increase max-age gradually.
  • Audit every subdomain before includeSubDomains.
  • Treat preload as a separate commitment.

Next step

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

See the DotMoose security approach

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

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

Security header rollout: add browser protections without breaking the site

Inventory current behaviour, deploy security headers one at a time, use report-only modes where available and verify login, checkout and embedded content.

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