See what your Content Security Policy blocks, before your users do
A Content Security Policy tells the browser which scripts, styles and images a page may load. When the browser blocks something, it can send a report. Point those reports at Buggregator, and you see what your policy blocks while you write it.

One report: the rule, what was blocked and where, with the full policy below.
What was blocked, by which rule, where
Every report the browser sends, readable, next to your other events.
One line per blocked thing
The feed card shows the page, then one line per report, for example «script-src-elem blocked https://cdn.example.com/x.js». Report-only violations get a badge.
Where it happened
The event page shows the directive, the blocked resource, the file with line and column, the code sample and the message.
The full policy and raw report
Below each report: the policy the browser applied and the report exactly as it came.
report-uri and report-to
Both formats: the classic application/csp-report and the Reporting API list. A Reporting API request with several reports becomes one event.
Deprecation warnings too
The Reporting API also tells you when your page uses a deprecated feature. Name the endpoint default to get those reports.
A project per app
Put the project in the path, /csp/shop: browsers send no headers of your own. A new name creates the project with its first report.
Tighten your policy without breaking checkout
Add the policy as Content-Security-Policy-Report-Only and click through your app. Nothing is blocked yet, but what the policy would block shows up in Buggregator, with the rule and the page. Allow what you need, and switch to the enforcing header once the reports stop.
Setup in 60 seconds
No registration. No account. Start it and point your app at it.
Start Buggregator
Requires Buggregator v2.13.0 or later. Reports arrive on port 8000, the same port as the UI. Nothing to turn on. One file, about 40 MB, installed with one command. Prefer containers? Use the Docker tab.
$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh $ HTTP_ADDR=127.0.0.1:8000 \ SMTP_ADDR=127.0.0.1:1025 \ VAR_DUMPER_ADDR=127.0.0.1:9912 \ MONOLOG_ADDR=127.0.0.1:9913 \ PROXY_ADDR=127.0.0.1:8080 \ ~/.local/bin/buggregator
The script picks the file for your CPU: Intel/AMD or ARM.
One file for Linux, macOS and Windows, about 40 MB. Nothing else to install.
Runs on Windows, macOS and Linux, on Intel/AMD and ARM.
Prefer not to do it yourself? Your AI agent can set Buggregator up for you →
Point the browser’s reports at Buggregator
The address is http://localhost:8000/csp/<project>; leave out /<project> for the default project. Start with Report-Only: the browser reports but blocks nothing.
Content-Security-Policy-Report-Only: default-src 'self'; report-uri http://localhost:8000/csp/shop
Works everywhere, also over plain http.
Open your page — see what the policy blocks
Each report request becomes one card in the feed. CSP reports in the menu lists only these events.
Works with browser reports
One or two headers in your app. Buggregator takes both report formats browsers send.
Good to know
- report-to needs https or localhost on both sides. Over plain http, use report-uri.
- A report body may be at most 1 MB. An empty list or JSON that is not a report gets 400.
- Browsers may first send a CORS check (OPTIONS); Buggregator answers it.
Ready to try it?
One command to start. No account needed.
Also built into Buggregator