Reporting API (crash, CSP and deprecation reports)
Sends the browser's own error, crash and policy violation reports to a site endpoint.
In one line
Can get the browser's crash and error reports sent to the site
Sends the browser's own error, crash and policy violation reports to a site endpoint.
A site can learn when its page crashes, runs out of memory, hits a blocked resource or uses a deprecated feature on your device, and gets those reports even after the page closed. No prompt is shown.
What it can and can't do
What the user does: Nothing. It happens if the page crashes or breaks a site rule
It can
- Receive reports on crashes, out of memory stops and blocked content
- Receive notes about old features your device used
- Get the report even after you left the page
It cannot
- See anything you typed or saved
- Ask permission first
- Know who you are by itself
- See reports from pages it does not own
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 96 | 2021-11-15 | None |
| Edge | Supported | 96 | 2021-11-19 | None |
| Firefox | Supported | 130 | 2024-09-03 | None |
| Safari | Supported | 16.4 | 2023-03-27 | None |
| Safari on iPhone | Supported | 16.4 | 2023-03-27 | All iOS browsers use WebKit |
| Chrome on Android | Supported | 96 | 2021-11-15 | None |
| Samsung Internet | Supported | 17.0 | 2022-05-04 | None |
How a site asks for it
| API | Reporting-Endpoints: default="https://example/r"; new ReportingObserver(cb, {types}) |
| Browser compat keys | http.headers.Reporting-Endpointsapi.ReportingObserverapi.ReportBody |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| Activation | none |
| How long it lasts | Reports are queued and sent in the background, even after the tab is closed |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | Per document and its Reporting-Endpoints header; cross-origin frames use their own policy |
Typical flow
- Server sends Reporting-Endpoints header
- Browser notices a violation, deprecation or crash
- Browser sends a JSON report to the endpoint, possibly later
- Page can also read some reports with ReportingObserver
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- Report types vary: csp-violation, deprecation, intervention, crash, coep, coop, permissions-policy-violation, integrity-violation
- Browsers batch reports and retry for a limited time; delivery is best effort and delayed
- Reports cannot include page content, only the violation details and URL
- Firefox supports the header from 130 and ReportingObserver from 149; Safari 16.4
- The older Report-To header is removed from the spec in favour of Reporting-Endpoints
The story
What it is
The browser sends its own crash, security policy and old feature warning reports to an address the site chooses.
For you
You never see these reports. When your browser blocks a bad script or a tab crashes, it quietly tells the site, so the team can fix the problem. Your browser may send some details with it.
For makers
Teams use it to catch crashes and blocked content from real visitors, which a test lab would miss. It also helps teams roll out stronger security rules safely, in report only mode first.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bank turns on a strict content policy in report mode and learns which scripts it would block before it enforces. | None named |
| games | A browser game studio gets crash reports from real players on rare phones. | None named |
| developer | A site learns that a feature it uses will be removed in the next browser, and plans a fix. | None named |
| shopping | A retailer sees reports that a third party script is being blocked, and finds a broken checkout step. | None named |
| analytics | A monitoring service collects reports across many sites and groups them by cause. | Sentry, Datadog |
| ads | A publisher sees that an ad was blocked for breaking a rule and removes it. | None named |
| news | A news site uses reports about intervention warnings to stop heavy ads that freeze the page. | None named |
Risks
- Reports may include page URLs
- Sent without asking
What the platform says
- Google Chrome: Reporting API. Chrome says it lets sites receive reports about crashes, policy violations and deprecated features from real users.
- MDN: Reporting API. Describes a standard way for browsers to send reports about problems to a site's chosen endpoint.
Good uses and abuse
Legitimate uses
- CSP violation monitoring
- Crash and OOM telemetry
- Deprecation warnings before breaking changes
Known abuse
- Collecting reports about the person's browser features and blocked extensions
- Exfiltrating clues about browser state
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2021-11, Chrome 96: Reporting-Endpoints header ships
- 2023-03, Safari 16.4: Reporting API ships in Safari
- 2024-09, Firefox 130: Firefox ships Reporting-Endpoints header
Related capabilities
Related
- Beacons and keepalive requests. Can send data to a server as you leave or close the page
- Long Animation Frames (LoAF). Can see slow page frames and which scripts caused them
Sources
How well checked: Based on official documentation.