Skip to Content
Platform.Ontology

Clock skew and crystal timing fingerprint

Measures tiny clock speed differences between a device's timers.

Used to track youSpeed and timingComputeWeb browsersWhile you use it

In one line

Can compare your device clocks over many seconds to tell it apart

Measures tiny clock speed differences between a device's timers.

Each device has slightly different oscillator frequencies. Comparing performance.now, Date, requestAnimationFrame and server timestamps over many seconds yields a device-specific drift signature, researched as time-based fingerprinting.

What it can and can't do

What the user does: Nothing. It happens while the page stays open for some seconds

It can

  • Compare several clocks, such as the page timer, the date and screen refresh
  • Compare them with the site's server time
  • Build a device number from tiny speed differences

It cannot

  • Work in the first moments of a visit, since it needs many seconds
  • Ask permission first
  • See your files
  • Know who you are by itself

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APIperformance.now(); Date.now(); requestAnimationFrame; WebSocket timestamps
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. Sample timers repeatedly
  2. Compute drift ratio against server clock
  3. Cluster across visits

Data you get

What comes back: Drift in parts per million
Shape: float

FieldTypeUnitRangePrecision
skewfloatppm-100 to 100needs minutes of samples

Technical limits

  • Needs seconds to minutes and low noise, less reliable on mobile
  • Timer coarsening reduces accuracy

The story

What it is

A script measures tiny speed differences between your device's clocks to make a hardware ID.

For you

You never see it. Every device has tiny flaws in its clock chips. A page can measure those flaws over a few seconds and get a number that stays about the same for your device.

For makers

It works even when software signals are hidden or randomized, since it comes from the hardware itself. Researchers have shown it can separate nearly identical phones. Browsers fight it by blurring timers.

Where you see it

TypeExampleApps
securityA research team shows that two phones of the same model can be told apart by clock skew.None named
adsAn ad tracker could use clock skew to recognize one device across apps and sites.None named
bankingA bank looks for a hardware trait to link a login to a stolen or cloned device.None named
gamesA game with strict anti cheat checks for devices reused by a banned player.None named
analyticsA cookie free counter uses clock skew to count unique devices.None named
developerA browser maker adds noise to timers so these tricks lose accuracy.Chrome, Firefox, Safari
shoppingA ticket site tries to find a scalper using one laptop with many fake browsers.None named

Risks

  • Hard to hide a hardware trait
  • Mostly research so far

Good uses and abuse

Legitimate uses

  • None

Known abuse

  • Device-bound identification not reset by clearing cookies

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 bits5Rough identifying entropy, when known

History

  • 2018-10, paper: Sanchez-Rola et al. Clock Around the Clock (CCS 2018)

Sources

How well checked: Based on official documentation.

On this page