CSP Violation-Report Analyzer

Analyze supplied CSP reports by directive and distinguish enforced from report-only records.

On-device No sign-up Free to use

Analyze CSP reports controls

?

Up to 1 MiB and 1,000 events. Paste the Reporting API array or a legacy {"csp-report": ...} object. Reports remain in your browser.

Processed in your browser. Your inputs stay on this device.

Showing an example. Change the fields, then use analyze csp reports to update it.

Result

Showing an example.

Group one enforcing img-src report and one report-only script-src report.

1 event on img-src, enforcing. 2 reports across 2 directives: 1 enforcing, 1 report-only.

Loading the tool. Your result will appear here.

https://usefreetools.net/csp-violation-report-analyzer · 20 November 2026

Was this helpful?

How to use CSP Violation-Report Analyzer

  1. Paste a Reporting API array of csp-violation events or a supported legacy csp-report object. Keep the collection within 1 MiB and 1,000 events.
  2. Run Analyze CSP reports. Read which entries were accepted or skipped and compare directive counts with their stated enforcing or report-only disposition.
  3. Inspect document/referrer origins and blocked-source summaries. Unknown directives and dispositions remain unknown rather than being inferred.
  4. Download the normalized event CSV if needed. Paths, queries, fragments, credentials, script samples and the original policy are omitted; origins can still identify a site.

Example: CSP Violation-Report Analyzer

Group one enforcing img-src report and one report-only script-src report.

You add
Violation reports as JSON: [ { "type": "csp-violation", "body": { "documentURL": "https://shop.example.com/orders/checkout?cart=42&token=abc", "referrer": "https://search.example.org/results?q=secret", "blockedURL": "https://cdn.tracker.example/pixel.gif?id=9911", "effectiveDirective": "img-src", "disposition": "enforce", "lineNumber": 12, "columnNumber": 4, "statusCode": 200 } }, { "type": "csp-violation", "body": { "documentURL": "https://shop.example.com/orders/checkout?cart=42&token=abc", "blockedURL": "inline", "effectiveDirective": "script-src", "disposition": "report", "lineNumber": 40, "columnNumber": 1 } } ]
You get
1 event on img-src, enforcing. 2 reports across 2 directives: 1 enforcing, 1 report-only.

Options

Violation reports as JSON
Up to 1 MiB and 1,000 events. Paste the Reporting API array or a legacy {"csp-report": ...} object. Reports remain in your browser.

Supported inputs and limits

  • Up to 1 MiB and 1,000 supplied events in the supported Reporting API or legacy format.
  • Unsupported entries are skipped and reported.
  • Directives are matched against a fixed list; unrecognized names or dispositions remain unknown.
  • URL details, samples, original policies and unsupported extensions are omitted from normalized output.
  • No URL is fetched, report authenticated or current policy discovered.
More details

Even an event marked enforce is a supplied claim, not proof that a real browser blocked an operation.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Reports are observations supplied by someone else

An enforcing event and a report-only event have different meanings, so keep their groups separate. Reports can be incomplete or forged and do not establish a site’s current policy. URL values are reduced to the supported scheme/origin representation; samples and arbitrary extensions are omitted rather than copied into exports.

Questions about CSP Violation-Report Analyzer

Are URL tokens exported?

Detailed path, query, fragment and credential values are omitted by the supported sanitization.

Does a report prove a current policy?

No. Supplied reports can be stale, partial or forged.

Are script samples included?

No. Samples and unsupported extensions are omitted from the report.

Page updated · Project managed by Tony Hines · Report a problem with CSP Violation-Report Analyzer