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

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

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

A Content Security Policy rollout reduces where the browser may load or execute content, but a strong policy must still permit every legitimate application path. The safest sequence is inventory, Report-Only observation, nonce/hash design, browser interaction coverage, enforcement, and continued regression monitoring.

Inventory resource and action origins

List scripts, styles, fonts, images, connect/fetch endpoints, frames, workers, media, forms, and base/object behavior across representative routes. Include consent-dependent analytics and rare application flows, not only the homepage.

Remove unused third-party dependencies before adding them to a permanent allowlist.

Prefer nonces/hashes over broad unsafe-inline

For server-rendered dynamic scripts, per-response nonces can authorize intended code while blocking injected inline script. Hashes work for stable inline blocks. Keep script-src-attr restricted so event-handler attributes do not bypass the design.

Understand strict-dynamic browser behavior before relying on it.

Use Report-Only to discover breakage

Collect violation reports or browser-console evidence while exercising forms, checkout, menus, tools, downloads, authenticated flows, and analytics with consent denied/granted. Separate browser extensions/noise from genuine site resources.

Do not leave Report-Only forever after compatibility is proven.

Enforce and continuously test

Move the same tested policy to enforcing mode, verify critical flows again, and assert the header in production edge tests. Review new violations when dependencies change and add only the minimum policy change required.

  • Inventory all directive categories.
  • Use nonce/hash-based script policy.
  • Exercise real flows in Report-Only.
  • Enforce with ongoing browser regression.

Next step

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

See the DotMoose security approach

Keep reading

Related guides.

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

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