Skip to Content
Platform.Ontology

ETag and HTTP cache supercookie

A tracker stores an ID in the cache validators of a file, which come back on every request.

Used to track youNetwork and connectionSupercookiesWeb browsersWhen the page loads

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

BrowserStatusFirst versionReleasedNote
ChromeRemoved862020-10-20HTTP cache partitioned
EdgeRemoved862020-10-09HTTP cache partitioned
FirefoxRemoved852021-01-26Network state partitioning
SafariRemoved12003-06-23Cache partitioned by first party (2013)
Safari on iPhoneRemoved12007-06-29Cache partitioned by first party (2013)
Chrome on AndroidRemoved862020-10-20HTTP cache partitioned
Samsung InternetRemoved14.02021-04-17HTTP cache partitioned

How a site asks for it

APIETag, If-None-Match, Last-Modified, Cache-Control
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Server issues unique ETag
  2. Browser caches the resource
  3. Later request sends If-None-Match with the ID

Data you get

What comes back: Opaque ID
Shape: string

FieldTypeUnitRangePrecision
etagstringNonerandom tokenexact

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

TypeExampleApps
adsAn ad network labels a tiny image with a unique tag and reads it back to recognize you on the next visit.None named
analyticsAn analytics script rebuilds a lost ID from the cache label after cookies are cleared.None named
securityA fraud company uses it to link a returning bot or a banned account.None named
shoppingA retargeting service recognizes a shopper who deleted cookies and shows the same product ads.None named
gamesA game portal links a banned player's new browser session to the old one.None named
mediaA 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

Good uses and abuse

Legitimate uses

  • Cache revalidation

Known abuse

  • Cookie free first party tracking

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility1 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits4Rough 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

Sources

How well checked: Based on official documentation.

On this page