HSTS supercookie
A site stores an ID in which subdomains the browser has been told to load only over HTTPS.
In one line
Can try to tag your browser with a hidden secure site ID, though it is limited
A site stores an ID in which subdomains the browser has been told to load only over HTTPS.
Each bit is a subdomain set to HSTS or not. The tracker reads it back by probing http:// URLs and seeing which upgrade (Kamkar 2015). Safari's ITP and clearing site data restrict it; HSTS is mostly cleared with history.
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 bits by choosing which subdomains your browser forces onto https
- Check them later by trying plain http web addresses
- Recognise a returning visitor until you clear history or site data
It cannot
- Survive clearing history in most browsers
- Work well in Safari, which limits it
- Carry much data; each subdomain gives one bit
How it differs between platforms: Safari limits it. Chrome, Edge and Firefox allow it partly, but it is cleared with history.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Partial | Not available | Not listed | :Partitioning not shipped (HSTS state is cleared with history) |
| Edge | Partial | Not available | Not listed | :Partitioning not shipped (HSTS state is cleared with history) |
| Firefox | Partial | Not available | Not listed | :State survives; private mode isolated |
| Safari | Removed | 12 | 2018-09-17 | WebKit mitigation 2018 |
| Safari on iPhone | Removed | 12 | 2018-09-17 | WebKit mitigation 2018 |
| Chrome on Android | Partial | Not available | Not listed | :Partitioning not shipped (HSTS state is cleared with history) |
| Samsung Internet | Partial | Not available | Not listed | :Partitioning not shipped (HSTS state is cleared with history) |
How a site asks for it
| API | Strict-Transport-Security on N subdomains; redirect probing |
| 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
- Set HSTS on chosen subdomains to write bits
- Request http subdomains
- Check which redirect to https to read the ID
Data you get
What comes back: N bit identifier (a few dozen subdomains)
Shape: integer
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
id bits | integer | bits | up to 30 to 40 | needs many requests |
Technical limits
- Needs dozens of subdomains and many requests
- Cleared when the person clears browsing data
The story
What it is
A site stores an ID in which of its sub-sites your browser forces onto secure mode.
For you
You never see it. Your browser remembers secure site choices. A tracker can set many tiny secure flags like switches and read them back later to see your personal code. Many browsers now limit this trick.
For makers
It is an old trick to recognize people after cookie clearing, and it still shapes how browsers handle secure site lists. Trackers once used it. Privacy teams want it blocked.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A tracker sets a pattern of secure site flags on a first visit and reads it back to recognize you. | None named |
| analytics | An analytics vendor uses it as a backup ID when cookies are deleted. | None named |
| security | A researcher shows how it could re identify private browsing users. | None named |
| shopping | A store ad partner uses it to re identify a shopper who cleared cookies. | None named |
| media | A publisher could match a returning reader behind a paywall. | None named |
| games | A game site could link repeat sessions of a banned player. | None named |
Risks
- Survives clearing cookies
- Browsers now limit it
Good uses and abuse
Legitimate uses
- None
Known abuse
- Cookie-free persistent ID
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
- 2018-01, Safari: WebKit limits HSTS to prevent cross-site tracking (ITP)
Related capabilities
Related
- ETag and HTTP cache supercookie. Can try to tag your browser with a hidden cached ID, though browsers now limit it
Sources
How well checked: Based on official documentation.