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

Website security headers: what the common headers do

Published August 2026 · 9 min read

Security headers give browsers instructions about how to handle content, transport, embedding, referrers, and selected platform features. They can reduce certain classes of risk, but a copied header bundle can also break a real application.

Content Security Policy is powerful and application-specific

CSP can limit where scripts, styles, frames, images, and connections are loaded from. Build it from the resources the application actually needs, use reporting during rollout, and avoid weakening it with broad wildcards simply to make console errors disappear.

HSTS protects the transport decision after HTTPS is stable

It tells supporting browsers to prefer HTTPS for a remembered period. Certificate renewal and subdomain planning should be mature before long max-age or includeSubDomains settings are used.

Frame, referrer, and permissions controls solve different problems

Frame restrictions can reduce unwanted embedding, Referrer-Policy controls information sent with navigation, and Permissions-Policy limits selected browser features. Choose values that match application behaviour and third-party integrations.

Headers complement application security

They do not replace patching, secure authentication, authorization, input handling, dependency management, server hardening, backups, or incident response. Treat them as one layer in a broader security baseline.

Next step

Understand HSTS, Content-Security-Policy, frame controls, Referrer-Policy, Permissions-Policy, and why security headers need application-aware testing instead of a copied scorecard.

See 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

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