ETag and HTTP cache supercookie
A tracker stores an ID in the cache validators of a file, which come back on every request.
In one line
Can try to tag your browser with a hidden cached ID, though browsers now limit it
A tracker stores an ID in the cache validators of a file, which come back on every request.
A server sets a unique ETag or Last-Modified on a resource; the browser sends If-None-Match back, identifying the visitor. Since cache partitioning (Chrome 86, Firefox 85, Safari earlier) the ID is only valid per top-level site.
What it can and can't do
What the user does: Nothing. It happens when you visit a site that tries it
It can
- Store an ID in the cache details of a file
- Recognise a returning visitor on the same site
- Keep the ID after you clear cookies in older browsers
It cannot
- Follow you across different sites; modern browsers separate the cache by site
- Survive clearing your cache or browsing data
- Work the same in every browser
How it differs between platforms: Chrome, Firefox and Safari all split the cache by site now, so the ID only works inside one site.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Removed | 86 | 2020-10-20 | HTTP cache partitioned |
| Edge | Removed | 86 | 2020-10-09 | HTTP cache partitioned |
| Firefox | Removed | 85 | 2021-01-26 | Network state partitioning |
| Safari | Removed | 1 | 2003-06-23 | Cache partitioned by first party (2013) |
| Safari on iPhone | Removed | 1 | 2007-06-29 | Cache partitioned by first party (2013) |
| Chrome on Android | Removed | 86 | 2020-10-20 | HTTP cache partitioned |
| Samsung Internet | Removed | 14.0 | 2021-04-17 | HTTP cache partitioned |
How a site asks for it
| API | ETag, If-None-Match, Last-Modified, Cache-Control |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Server issues unique ETag
- Browser caches the resource
- Later request sends If-None-Match with the ID
Data you get
What comes back: Opaque ID
Shape: string
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
etag | string | None | random token | exact |
Technical limits
- Cross-site ID no longer works; same-site ID still works
- Cleared with Clear browsing data
The story
What it is
A tracker hides a personal ID in a saved file's label, so it survives clearing cookies.
For you
You never see it. You clear your cookies and still get recognized, because the ID rides on a cached file. Modern browsers now keep separate caches per site, which weakens this trick.
For makers
Trackers and ad firms used it as a backup when cookies were blocked or deleted. It is mostly unfriendly to privacy, and browsers have been closing it with split caches.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | An ad network labels a tiny image with a unique tag and reads it back to recognize you on the next visit. | None named |
| analytics | An analytics script rebuilds a lost ID from the cache label after cookies are cleared. | None named |
| security | A fraud company uses it to link a returning bot or a banned account. | None named |
| shopping | A retargeting service recognizes a shopper who deleted cookies and shows the same product ads. | None named |
| games | A game portal links a banned player's new browser session to the old one. | None named |
| media | A video site recognizes a viewer who tried to dodge a free article limit. | None named |
Risks
- Survives clearing cookies
- Used for hidden tracking
What the platform says
- Google Chrome: HTTP cache partitioning. Chrome describes splitting the cache by site so one site cannot learn about your visits to another through shared cached files.
Good uses and abuse
Legitimate uses
- Cache revalidation
Known abuse
- Cookie free first party tracking
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 1 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 4 | Rough identifying entropy, when known |
History
- 2013-01, Safari: Safari double keys HTTP cache
- 2020-10, Chrome 86: HTTP cache partitioning
- 2021-02, Firefox 85: Network partitioning including cache
Related capabilities
Related
- Favicon cache supercookie (F-CACHE). Can try to tag your browser with a hidden icon cache ID, though fixes limit it
- Cache timing history sniffing. Can time how fast something loads to guess if you visited a site before
Sources
How well checked: Based on official documentation.