Repository navigation
FAQ
HSTS and a real Content-Security-Policy give the most protection, followed by clickjacking protection and X-Content-Type-Options: nosniff. The others are cheap hardening.
CSP frame-ancestors supersedes it in modern browsers. Either one satisfies this check; sending both is harmless.
Start with Content-Security-Policy-Report-Only and a report-to endpoint, fix what gets reported, then switch to the enforcing header. Use nonces or hashes instead of 'unsafe-inline'.
Yes, or set it to 0. The browser XSS auditor it controlled has been removed and could itself introduce vulnerabilities.
Weights and rules differ between tools. This one rewards headers that actually restrict behaviour (an enforcing CSP that limits scripts) rather than their mere presence.
Home · Getting started · FAQ · Troubleshooting · Online tool