Audit tool

Fetch real headers and inspect CSP coverage quickly.

Browsers do not expose arbitrary response headers cross-origin, so this page can fetch through a proxy or let you paste headers from DevTools or curl -I for the same analysis flow.

Choose an input source

If you omit the scheme, the tool will prepend https://.
If one proxy fails, switch providers and try again.

No check has been run yet.

Decode a CSP violation report

Paste the JSON payload that your browser sent to report-uri or report-to. The viewer accepts both the legacy application/csp-report shape and the modern application/reports+json batch.

Awaiting input.

No events decoded. Paste a JSON report above.

Why proxy fetching exists here

This page is designed for real-world troubleshooting, where you often need to inspect a live site quickly.

Browsers block direct reads

Normal frontend code cannot read arbitrary cross-origin response headers, so a proxy is needed for URL-based checks.

Same audit logic either way

Whether the headers are fetched remotely or pasted manually, the same header assessment logic is used.

Fallback stays simple

If the proxy path fails because of rate limits or WAF rules, switch to paste mode and continue the analysis.

Related reading

Diagnose what the audit finds and roll out a fix on your platform.

Next step

Use the live response to decide whether the fix belongs in the generator or in the broader header baseline.

Official references

Useful docs when a live response needs interpretation.