Skip to Content
Platform.Ontology

Timestamp seed (tsSeed)

Records the browser's clock value when collection starts.

Gets silentlySpeed and timingTimeWeb browsersWhen the page loadsWhile you use it

In one line

Can note your browser's clock when it starts collecting data

Records the browser's clock value when collection starts.

Time value used to order events and to check clock drift against the server.

What it can and can't do

What the user does: Nothing. It happens when collection starts on the page

It can

  • Save the current clock value
  • Put events in order
  • Check for clock drift against the server

It cannot

  • Know your exact location
  • Ask permission first
  • See your files
  • Know who you are by itself

Browser support

BrowserStatusFirst versionNote
ChromeSupportedNot availableNone
EdgeSupportedNot availableNone
FirefoxSupportedNot availableNone
SafariSupportedNot availableNone
Safari on iPhoneSupportedNot availableNone
Chrome on AndroidSupportedNot availableNone
Samsung InternetSupportedNot availableNone

How a site asks for it

APIDate.now() or performance.now()
How access is grantednone
What the user seesNone (no browser prompt)
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. Script reads the value
  2. Value joins the fingerprint payload

Data you get

What comes back: Timestamp seed (tsSeed)
Shape: integer
How often: read on demand

FieldTypeUnitRangePrecision
tsSeedintegermsNot listed1 ms

Technical limits

  • Rounded in some browsers

The story

What it is

A bot defense script records the browser's clock value when its data collection starts.

For you

You never see it. A security script stamps the time it started collecting traits. That helps the site check that the data it receives is fresh and was not copied from another visit.

For makers

Bot defense vendors use a time seed to stop replay, where an attacker reuses a valid data bundle from a real browser. It also helps measure how long each part of collection took, which separates humans from scripts.

Where you see it

TypeExampleApps
securityA bot defense system rejects a data bundle with an old timestamp, since an attacker reused it.Akamai Bot Manager, DataDome
shoppingA sneaker or ticket site blocks bots that replay a captured valid session.Ticketmaster
bankingA bank checks that device checks were produced on this visit, not copied.None named
gamesA browser game with prizes blocks replayed session data sent by cheats.None named
socialA social site blocks fake sign up scripts that reuse a valid captured bundle.None named
adsAn ad network rejects click reports with stale or repeated time seeds.None named
analyticsA fraud analytics tool measures time between steps to see if it matches a person.None named

Risks

  • Part of silent checks
  • Hard for honest users to see

Good uses and abuse

Legitimate uses

  • Order events

Known abuse

  • Clock skew checks

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1Rough identifying entropy, when known

A real example: LinkedIn

Collector key(s): tsSeed. Exact use of tsSeed is not documented publicly.

Sources

How well checked: Inferred from related behavior.

On this page