Skip to Content
Platform.Ontology

Cache timing history sniffing

Times how fast a resource loads to guess whether the person already visited a site.

Used to track youSpeed and timingSide channelsWeb browsersWhile you use it

In one line

Can time how fast something loads to guess if you visited a site before

Times how fast a resource loads to guess whether the person already visited a site.

A cached image or script loads in milliseconds, an uncached one in tens. Probing resources from other sites, or the status of a login, reveals browsing history. Cache partitioning mostly ended the cross-site variant.

What it can and can't do

What the user does: Nothing. It happens when the page loads

It can

  • Time how fast an image or script loads
  • Guess it was cached if it loads in a few milliseconds
  • Learn if you have visited some sites or are logged in

It cannot

  • See your full browsing history
  • Work as well now that browsers keep separate caches per site
  • Ask permission first
  • See what you did on the other site

How it differs between platforms: Chrome, Edge, Firefox and Safari now partition the cache per site, which breaks most of this.

Browser support

BrowserStatusFirst versionNote
ChromeNot supportedNot available:Mitigated by cache partitioning since 86
EdgeNot supportedNot available:Mitigated by cache partitioning since 86
FirefoxNot supportedNot available:Mitigated since 85
SafariNot supportedNot available:Mitigated since 2013 (ITP and partitioned cache)
Safari on iPhoneNot supportedNot available:Mitigated since 2013 (ITP and partitioned cache)
Chrome on AndroidNot supportedNot available:Mitigated by cache partitioning since 86
Samsung InternetNot supportedNot available:Mitigated by cache partitioning since 86

How a site asks for it

APIfetch/Image + performance.now(); PerformanceResourceTiming transferSize
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. Choose a resource unique to a target site
  2. Request it and measure timing
  3. Infer cached or not

Data you get

What comes back: Timing distribution threshold
Shape: boolean

FieldTypeUnitRangePrecision
load timefloatms1 to 300limited by timer

Technical limits

  • Same-site cache probing still works
  • Partitioned caches make cross-site probing fail in all three major browsers

The story

What it is

A site times how fast something loads to guess if you have already visited another site.

For you

You never see it. A page asks for a picture from another site and watches how quickly it appears. A fast load suggests you have been there before. Newer browsers have mostly blocked this.

For makers

It once let a site learn your browsing history without asking. Browsers now keep a separate cache for each site. Researchers and security teams still test it, and old browsers can still be fooled.

Where you see it

TypeExampleApps
securityA researcher shows that a news page can tell if you visited a bank by timing a logo load.None named
adsAn ad network guesses that you are in market for a car by checking which dealers' images are in cache.None named
socialA social site checks whether you have seen a rival site recently to tune what it shows.None named
shoppingA shop checks if you saw a competitor's product images to adjust a promo.None named
developerA web performance team uses cache timing in tests to see how much a page benefits from caching.None named
newsA paywall tests whether you came from a certain site by checking for its assets.None named
analyticsA security team reviews logs for pages that probe other sites' files.None named

Risks

  • Mostly fixed in modern browsers
  • Old browsers still exposed

What the platform says

Good uses and abuse

Legitimate uses

  • None legit

Known abuse

  • Browsing history leak, login state detection

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 partitions HTTP cache by first party
  • 2020-10, Chrome 86: HTTP cache partitioned by top-level site and frame site
  • 2021-01, Firefox 85: Network partitioning including HTTP cache

Sources

How well checked: Based on official documentation.

On this page