How to fix: NEL header not configured
Network Error Logging is not configured via the NEL header, preventing automatic collection of network-level failures.
Why it matters
Network failures like DNS resolution errors, connection timeouts, and TLS handshake failures that affect real users remain invisible without NEL reporting.
NEL collects client-side network failure events and reports them to your specified endpoint.
How to fix it
- 1Configure a Report-To header with a Nel reporting group
- 2Add NEL header referencing that group
- 3Monitor reports for patterns indicating infrastructure issues
Code examples
NEL setup
export default {
async headers() {
return [{ source: "/(.*)", headers: [
{ key: "Report-To", value: JSON.stringify({ group: "nel", max_age: 86400, endpoints: [{ url: "/api/nel" }] }) },
{ key: "NEL", value: JSON.stringify({ report_to: "nel", max_age: 86400 }) },
]}];
},
};References
Detected automatically by VulnRadar. The check id is nel-header-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is NEL header not configured?
- VulnRadar rates this info 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 nel-header-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.