Test your website’s HTTP security headers: Content-Security-Policy, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and cookie flags. Free with fixes.
Security headers are one-line settings on your web server that tell browsers how to protect your visitors — against injected scripts, clickjacking and data leaks. They are cheap to add and auditors look for them. Enter your site to see which are missing and how to add each one.
The main browser defence against cross-site scripting (XSS).
Forces HTTPS and stops SSL-stripping attacks.
Stops other sites from loading yours in a hidden frame (clickjacking).
Stops browsers guessing file types.
Limit what leaks to other sites and which browser features pages may use.
Session cookies marked Secure and HttpOnly; software versions not advertised.
HTTPS with HSTS first, then Content-Security-Policy. CSP takes the most work: start with Content-Security-Policy-Report-Only, collect reports, then enforce.
Yes — use Rules → Transform Rules → Modify Response Header, or a Cloudflare Worker. HSTS has its own switch under SSL/TLS → Edge Certificates.
Not directly, but HTTPS is a ranking signal and browsers flag insecure pages. Headers like CSP mainly protect your visitors and your reputation.
Free plan for one domain. No credit card needed.