Wouldn't it be great if every visitor to your site would take the time to notify you when they are experiencing connectivity issues? Wouldn't it be even better if they would also tell you exactly what caused the issue? Things like DNS lookup failures, connection timeouts, reset connections or dead links that result in 404 errors?

As most of these issues are not detectable server-side, since by definition the client might not have been able to successfully establish a connection with the server, getting client-side feedback would be extremely valuable!

Well..., stop fantasizing because this is now possible by adding just two response headers to your website. By adding the 'Report-To'- and 'NEL'-header you are instructing supporting user agents (browsers) to send you reports about connectivity issues. Aside from logging errors,  NEL can also be used to log successful requests allowing you to determine rates of errors across different client populations.

Report-To Response headers

The 'Report-To' header instructs the user agent where to sent the reports. It's value is a JSON-formatted array of objects. After adding this header you'll receive deprecation, intervention and crash reports. I will not dive into these right now, but more information about these reports can be found here. Example:

Report-To: {"group":"endpoint-1","max_age":10886400,"endpoints":[{"url":""}],"include_subdomains":true}

More information about this header's elements can be found here.

NEL Response headers

The 'NEL' header is also a JSON-formatted array of objects and refers to a report endpoint defined in the previously mentioned 'Report-To' header. This header is an extension to the 'Report-To' header that instructs the user agent to also send network error reports. It is not possible to configure a 'NEL' header without a 'Report-To' header. Example:

NEL: {"report_to":"endpoint-1","max_age":2592000,"include_subdomains":true,"failure_fraction":0.5}

More information about this header's elements can be found here.

Sampling report volume

There are two optional fraction values (success_fraction and failure_fraction) that allow you to define a sampling rate between 0 and 1, inclusive. If you have a high traffic website, it would be a good idea to set a value lower than 1 to decrease the number of reports being sent. For instance, a value of 0.25 will instruct browsers to send only 1 out of 4 reports (25%). The default value for 'success_fraction' is 0, so you will not receive any success reports by default. Be sure to start small when enabling this feature, as this will surely result in a lot of reports. So start at 0.001 and work your way up if you need more.

Example report

Below is an example report from the W3C Editor's Draft. The report is delivered using a POST to the endpoint that was specified in the 'Report-To' response header.

  "age": 0,
  "type": "network-error",
  "url": "",
  "body": {
    "sampling_fraction": 1.0,
    "referrer": "",
    "server_ip": "",
    "protocol": "",
    "method": "GET",
    "request_headers": {},
    "response_headers": {},
    "status_code": 0,
    "elapsed_time": 143,
    "phase": "dns",
    "type": "dns.name_not_resolved"

The example report above indicates that the user agent attempted to fetch from However, the user agent was unable to resolve the DNS name ( and the request was aborted by the user agent after 143 milliseconds. Because a previous request to delivered a valid NEL policy, the user agent generates a network error report for this request. The report was uploaded immediately after the network error was encountered – i.e. the report age is 0.

Network error types

Below is a list of predefined error codes and their description. As you can see there is a lot of detailed information to gain from adding a NEL header to your website.

    DNS server is unreachable
    DNS server responded but is unable to resolve the address
    Request to the DNS server failed due to reasons not covered by previous
    Indicates that the resolved IP address for a request's origin has
    changed since the corresponding NEL policy was received 

    TCP connection to the server timed out
    The TCP connection was closed by the server
    The TCP connection was reset
    The TCP connection was refused by the server
    The TCP connection was aborted
    The IP address is invalid
    The IP address is unreachable
    The TCP connection failed due to reasons not covered by previous errors

    The TLS connection was aborted due to version or cipher mismatch
    The TLS connection was aborted due to invalid client certificate
    The TLS connection was aborted due to invalid name
    The TLS connection was aborted due to invalid certificate date
    The TLS connection was aborted due to invalid issuing authority
    The TLS connection was aborted due to invalid certificate
    The TLS connection was aborted due to revoked server certificate
    The TLS connection was aborted due to a key pinning error
    The TLS connection was aborted due to a TLS protocol error
    The TLS connection failed due to reasons not covered by previous errors

    The user agent successfully received a response, but it had a 4xx or
    5xx status code 
    The connection was aborted due to an HTTP protocol error
    Response is empty, has a content-length mismatch, has improper encoding,
    and/or other conditions that prevent user agent from processing the
    The request was aborted due to a detected redirect loop
    The connection failed due to errors in HTTP protocol not covered by
    previous errors

    User aborted the resource fetch before it is complete
    error type is unknown


Collecting and analyzing these reports can reveal valuable data that allows you to improve your website. At URIports we automatically detect issues and send notifications when we detect something is wrong. You will receive an email or push notification when multiple sources (different IP / browser combinations) experience the same issues, like '404 not-found' errors, expired or wrongly configured certificates or connectivity or DNS issues. This will keep you up-to-date and will allow you to quickly resolve the issues without the site visitor taking the time to alert you personally.


Based on the (January 2020) data from Scott Helme's Crawler.Ninja, only 1.2% of the websites in the Alexa top 1 million use Network Error Logging. In my opinion, that would make NEL the most undervalued monitoring technique available today.


Setting up 'Network Error Logging' is really easy and best of all, it is free and already supported by most browsers like Chrome (Mobile), Opera, Yandex, Electron, Vivaldi, Edge, etc. By combining it with URIports you make it even more valuable, allowing you to easily navigate and analyze the data and adding notifications as a bonus.

Getting Started with URIports

We have a 'Getting Started'-page to help you set up everything by adding just a few response headers and DNS records. You will have your free 30-day URIports trial account set up and working in less than 30 minutes. No commitment or credit card details required and no strings attached. An additional advantage to using URIports is that the reports are collected outside the network of the website so that these reports can be delivered, even when the entire network of the website is down.

As always, if you have any questions, please find me on Twitter @freddieleeman