Skip to Content
Platform.Ontology

TLS session resumption tracking

Reuse of a TLS session ticket can link a visitor's connections across sites that share a server.

Used to track youNetwork and connectionSupercookiesWeb browsersWhen the page loads

In one line

Can link your visits across sites on one server if your browser reuses a ticket

Reuse of a TLS session ticket can link a visitor's connections across sites that share a server.

A session ticket or PSK is a stable ID, so two domains behind one CDN or server can see the same resumption. Sy et al. (ACSAC 2018) found browsers reusing tickets across origins. Chrome partitioned TLS session caches by network isolation key.

What it can and can't do

What the user does: Nothing. It happens when you return to a site and the connection resumes

It can

  • See the same resume ticket when you visit two sites behind one server or content network
  • Use the ticket as a temporary ID to connect those visits
  • Speed up your next connection, which is the real purpose

It cannot

  • Link visits on servers that do not share infrastructure
  • Keep the link for long, since tickets expire in hours or days
  • Work against browsers that keep separate tickets per site, such as Chrome and Firefox
  • See your name or what you do on the site

How it differs between platforms: Chrome and Firefox keep tickets separate per site. Safari is partly protected. Older tests showed browsers reusing tickets across sites.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeRemoved862020-10-20Session cache partitioned by NIK
EdgeRemoved862020-10-09Session cache partitioned by NIK
FirefoxRemoved852021-01-26Network partitioning
SafariPartialNot availableNot listed:Mitigation not verified
Safari on iPhonePartialNot availableNot listed:Mitigation not verified
Chrome on AndroidRemoved862020-10-20Session cache partitioned by NIK
Samsung InternetRemoved14.02021-04-17Session cache partitioned by NIK

How a site asks for it

APITLS 1.2 session tickets, TLS 1.3 PSK; session ID
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 ticket
  2. Client resumes later
  3. Server correlates

Data you get

What comes back: Ticket or PSK identity
Shape: string

FieldTypeUnitRangePrecision
ticketstringNoneopaqueexact

Technical limits

  • Ticket lifetime limited by browser (about 24 hours to 7 days)
  • Cross-site linking blocked by partitioning

The story

What it is

Reusing a saved secure connection ticket can link your visits across sites that share a server.

For you

You never see it. To start faster, your browser reuses a ticket from an earlier secure connection. A server that sees the same ticket from two places can tell they are the same browser.

For makers

Makers who run many sites on one server or provider can link visits without cookies. It is a quiet side effect of speed tricks. Browsers cut it by limiting how long tickets live and by splitting them per site.

Where you see it

TypeExampleApps
adsA big ad and content network serving many sites sees the same ticket on each. It joins the visits into one profile even with cookies blocked.None named
analyticsA hosting provider counts a returning visitor across all customer sites using the same ticket.Cloudflare
securityA defence service ties a bot's repeated requests to one ticket and blocks it, even if the address changes.None named
mediaA video platform links a viewer across its sites and its player embeds through one reused connection.None named
gamesA game portal hosting many titles on one server links a player's visits across games without a login.None named
socialA share button provider sees the same ticket on every site that embeds its button.None named
developerA privacy researcher tests whether a browser reuses tickets across sites, to see if it leaks.None named

Risks

  • Cookie free tracking
  • Hard to spot or clear

Good uses and abuse

Legitimate uses

  • Faster handshakes

Known abuse

  • Cross-domain linkage behind shared infrastructure

Scores

ScoreValueMeaning
Sensitivity2 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 bits3Rough identifying entropy, when known

History

  • 2018-12, paper: Sy et al. Tracking Users across the Web via TLS Session Resumption (ACSAC 2018)
  • 2020-10, Chrome 86: TLS session cache partitioned with Network Isolation Key

Sources

How well checked: Based on official documentation.

On this page