Sign up
Create a project, get a unique report URL. That's your setup.
Start with a 7-day trial — one project, no credit card, one AI-generated policy included. Five minutes from now your CSP could be doing its actual job.
Create a project, get a unique report URL. That's your setup.
Both report-uri and report-to are included for full browser coverage. Report-Only means nothing breaks — you're just listening.
Violations stream in automatically. We strip out browser extension garbage, bots, and AV false positives. When you're ready, one click generates a production-ready CSP with a plain-English explanation per directive.
Add a URL to your CSP header. Violations arrive automatically from every browser, every visitor. No SDK, no script tag, no code changes. Works with any stack — if you can set an HTTP header, you're done.
Browser extensions, antivirus injections, bots — stripped out at the pipeline by default. Add your own patterns when something slips through. The ones that hit across multiple projects get promoted to the shared list everyone sees. Moderated, not automatic — but the input is yours.
Click "Generate policy." Our LLM analyzes your violations, fetches your current header, and produces a new one. Not just rules — a plain-English explanation per directive, warnings about risky additions, and a list of origins it intentionally ignored (and why).
A Content Security Policy tells browsers which external resources your site is allowed to load. Sounds simple — until you realize you load fonts from Google, scripts from three CDNs, analytics from two providers, a payment iframe from Stripe, and a chat widget you forgot about. Miss one and your site breaks. Add too many and your policy is useless.
You set up reporting and immediately your inbox fills with garbage. Browser extensions injecting scripts. Antivirus rewriting pages. Crawlers and bots triggering false positives. Without serious filtering, CSP violation data is unusable.
Most developers know they need a CSP. But the reporting step — actually collecting and analyzing violations — gets skipped because the tooling is too complex, too expensive, or self-hosted. Only 13% of sites with a CSP have reporting enabled.
PCI-DSS 4.0 (enforced since March 2025) requires merchants to monitor scripts on payment pages. CSP reporting is the recommended approach. The deadline has passed — many companies are still scrambling.
Click once. Get a copy-paste-ready CSP, with a plain-English explanation per directive.
Below the €10 no-brainer line. Same features as Trial — just unlocked indefinitely.
Extensions, antivirus, bots — gone before they hit your dashboard. Add your own filters when something slips through.
One per registrable domain. One free LLM generation. Decide after you've seen it work.
All prices exclude VAT — Paddle adds VAT / sales tax at checkout based on your country. Upgrades are immediate and prorated; downgrades apply at the end of your billing period. Cancel anytime.