Device and network recognition¶
At each handshake the API compares the fingerprint with the devices already seen for the same user_id under your
key, and the IP with the IPs of the user's earlier sessions. Both verdicts are in every risk object, next to the
behavioural risk_level, which they do not change.
Device¶
device.status |
Meaning |
|---|---|
first_device |
The user has no earlier device to compare with. |
known |
Same device as an earlier session. |
known_changed |
One of the user's devices with a few components changed (changed): browser update, other monitor, OS update. match_score at least 0.85. |
new |
No earlier device of this user matches. closest_device_id and changed show the nearest one. |
no_fingerprint |
SDK before 2.2.0, fingerprinting off, or it timed out. |
device_id is stable across browser updates and window sizes and is salted per customer: the same browser has
different ids under different keys. flags may contain automation (webdriver or a headless browser),
canvas_randomized (canvas is then ignored) and few_components (most signals blocked, so matches are weaker).
Network¶
network field |
Meaning |
|---|---|
ip |
Client IP of the handshake. |
known_ip |
The user had an earlier session from this IP. |
known_subnet |
...or from the same /24 (IPv4) or /48 (IPv6) network. |
previous_ip user_ips |
IP of the user's previous session; distinct IPs seen for the user. |
asn as_org as_country |
Network operator announcing the IP (autonomous system), and its registration country (not the user's location). |
known_asn user_asns |
The user had an earlier session through the same operator; distinct operators seen. Home connections often change IP within one operator. |
hosting |
The operator is a cloud or hosting provider: usually a VPN, proxy, remote desktop or automation rather than a home or office. |
A new device is not a takeover by itself
New devices and networks are common for genuine users (new laptop, travel, mobile data). They are strongest
combined with the behavioural score: a new device whose typing also diverges from the user's history.
List a user's devices¶
/v1/collect/users/{user_id}/devicessecret keyThe devices the user has been recognised on, most recent first.