Skip to Content
Platform.Ontology

HSTS supercookie

A site stores an ID in which subdomains the browser has been told to load only over HTTPS.

Used to track youNetwork and connectionSupercookiesWeb browsersWhen the page loads

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

BrowserStatusFirst versionReleasedNote
ChromePartialNot availableNot listed:Partitioning not shipped (HSTS state is cleared with history)
EdgePartialNot availableNot listed:Partitioning not shipped (HSTS state is cleared with history)
FirefoxPartialNot availableNot listed:State survives; private mode isolated
SafariRemoved122018-09-17WebKit mitigation 2018
Safari on iPhoneRemoved122018-09-17WebKit mitigation 2018
Chrome on AndroidPartialNot availableNot listed:Partitioning not shipped (HSTS state is cleared with history)
Samsung InternetPartialNot availableNot listed:Partitioning not shipped (HSTS state is cleared with history)

How a site asks for it

APIStrict-Transport-Security on N subdomains; redirect probing
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. Set HSTS on chosen subdomains to write bits
  2. Request http subdomains
  3. Check which redirect to https to read the ID

Data you get

What comes back: N bit identifier (a few dozen subdomains)
Shape: integer

FieldTypeUnitRangePrecision
id bitsintegerbitsup to 30 to 40needs 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

TypeExampleApps
adsA tracker sets a pattern of secure site flags on a first visit and reads it back to recognize you.None named
analyticsAn analytics vendor uses it as a backup ID when cookies are deleted.None named
securityA researcher shows how it could re identify private browsing users.None named
shoppingA store ad partner uses it to re identify a shopper who cleared cookies.None named
mediaA publisher could match a returning reader behind a paywall.None named
gamesA 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

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

  • 2018-01, Safari: WebKit limits HSTS to prevent cross-site tracking (ITP)

Sources

How well checked: Based on official documentation.

On this page