How to fix: CSP report-to Group Has No Reporting-Endpoints Definition
The CSP references a 'report-to' group name, but the response does not define that group via a Reporting-Endpoints header.
Why it matters
CSP violation reports are silently dropped instead of being delivered, so real policy violations (including active XSS attempts) go unnoticed.
The modern Reporting API requires a separate Reporting-Endpoints header (or the legacy Report-To header) to map a group name used in 'report-to' to an actual URL. Without it, browsers have nowhere to send the reports.
How to fix it
- 1Add a Reporting-Endpoints header defining the same group name referenced by CSP's report-to directive.
- 2Verify the endpoint URL accepts POST requests with the application/reports+json content type.
Code examples
Next.js
const nextConfig = {
async headers() {
return [{
source: '/(.*)',
headers: [
{ key: 'Reporting-Endpoints', value: 'csp-endpoint="https://example.com/csp-reports"' },
{ key: 'Content-Security-Policy', value: "default-src 'self'; report-to csp-endpoint" },
],
}];
},
};
export default nextConfig;References
Detected automatically by VulnRadar. The check id is reporting-api-endpoints-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP report-to Group Has No Reporting-Endpoints Definition?
- VulnRadar rates this low severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id reporting-api-endpoints-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.