Before calling a site production-ready, validate HTTP security headers: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options and Referrer-Policy. Run this checklist after DNS and SSL — missing headers do not break the site but increase risk.
This guide complements the DNS and SSL checklist. Use the Security Headers Validator to audit any URL.
| Header | Present (good) | Missing (risk) |
|---|---|---|
Strict-Transport-Security | Forces HTTPS on future visits | Possible downgrade on first connection |
Content-Security-Policy | Limits script/style sources | Larger XSS surface |
X-Frame-Options | Reduces clickjacking | Page may load in malicious iframe |
X-Content-Type-Options: nosniff | Blocks MIME sniffing | Browser may misinterpret type |
Referrer-Policy | Controls URL leakage | Full referrers may expose paths |
Permissions-Policy | Restricts browser APIs | Sensitive features unrestricted |
max-age when testing.HTTP instructions that harden how the browser handles your app.
HSTS + X-Content-Type-Options + anti-framing (X-Frame-Options or CSP frame-ancestors).
Yes, with weaker security posture.
After DNS and SSL in production, before announcing go-live.
Forces HTTPS; requires a valid certificate first.
Security Headers Validator on XploreNetHub.