Timestamp seed (tsSeed)
Records the browser's clock value when collection starts.
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
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | Date.now() or performance.now() |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Script reads the value
- Value joins the fingerprint payload
Data you get
What comes back: Timestamp seed (tsSeed)
Shape: integer
How often: read on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
tsSeed | integer | ms | Not listed | 1 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
| Type | Example | Apps |
|---|---|---|
| security | A bot defense system rejects a data bundle with an old timestamp, since an attacker reused it. | Akamai Bot Manager, DataDome |
| shopping | A sneaker or ticket site blocks bots that replay a captured valid session. | Ticketmaster |
| banking | A bank checks that device checks were produced on this visit, not copied. | None named |
| games | A browser game with prizes blocks replayed session data sent by cheats. | None named |
| social | A social site blocks fake sign up scripts that reuse a valid captured bundle. | None named |
| ads | An ad network rejects click reports with stale or repeated time seeds. | None named |
| analytics | A 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
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): tsSeed. Exact use of tsSeed is not documented publicly.
Related capabilities
Related
- APFC / DNA device fingerprint (abuse prevention features). Can collect about 48 device traits and send them in secret with later requests
Sources
How well checked: Inferred from related behavior.