Directives that aren't there.
No script-src? No object-src? No policy at all? The most common CSP problem is absence — we flag every load-bearing directive your header should have.
Enter a URL and we'll grade its Content-Security-Policy: missing directives, unsafe-inline, over-broad sources, and whether it reports violations at all. Free, no sign-up.
No script-src? No object-src? No policy at all? The most common CSP problem is absence — we flag every load-bearing directive your header should have.
'unsafe-inline' and 'unsafe-eval' in script-src re-open the exact attack CSP exists to block. We grade them accordingly.
Wildcards, bare https:, whole CDN domains anyone can upload to — a guest list that says "everyone" isn't a guest list.
A policy without report-uri / report-to fails silently: you never learn what it blocked, or what it missed. Only 13% of sites with a CSP report violations.
A policy exists, but 'unsafe-inline' and a missing report-uri leave the door open.
A rating tells you today's header is weak; it can't tell you what a strong one looks like for your traffic. csplog collects the violation reports your visitors' browsers already send, drops extension, antivirus and bot noise before it reaches you, and assembles a policy from the origins you approve, with a plain-English explanation per directive. Then it fetches your pages to check the header really went live. From €7/month in the EU, $8/month elsewhere. 14-day trial, no credit card.
launching_soon · want to fix it yourself first? the guide covers nonces, report-only mode and rollout.