Live demo
Run a real check on this visit
We ask for cookies first — then collect network, device, TLS, and behavior the same way your product would. You get a score, verdict, and reasons. Full IP, breach intel, and the abuser graph stay off.
01
Allow cookies
Needed to collect on this page
02
Move & type
Richer sessions → clearer scores
03
Run the check
Same shape as production
04
Start free
1,000 live checks / mo
Consistency
What changes when you switch?
Try it: rerun the check from an incognito window, another browser, or a phone hotspot. Each signal has a job — some should hold, some should reset. If a value changes exactly the way a card below predicts, the collection is working.
Reopen this browser
Close the tab, come back tomorrow — same profile, same IDs. Return visits match instantly.
- Bound ID
- same
- TLS (JA4)
- same
- Network
- same
- Cookies
- same
Private / incognito window
Storage and extensions vanish, but the device binding holds — and the private window itself is flagged as context.
- Bound ID
- same
- TLS (JA4)
- same
- Network
- same
- Cookies
- gone
Switch browser
A standalone browser → another engine or an embedded app shell. Each engine mints its own Bound ID on purpose — TLS and network still tie the visits together.
- Bound ID
- new
- TLS (JA4)
- new
- Network
- same
- Cookies
- gone
Switch Wi-Fi / hotspot
Device identity is independent of the connection. The IP range and ASN change; everything bound to the browser stays put.
- Bound ID
- same
- TLS (JA4)
- same
- Network
- new
- Cookies
- same
VPN / proxy on
Same browser, new exit network. The device binding holds while the datacenter or VPN ASN raises network risk.
- Bound ID
- same
- TLS (JA4)
- same
- Network
- new + flagged
- Cookies
- same
Different computer
A new machine is a new visitor — every browser signal resets. Only your account (email / user ID) links the two.
- Bound ID
- new
- TLS (JA4)
- new
- Network
- new
- Cookies
- gone
What each signal tells us
- Bound ID
- The identity of this browser profile on this device. Stable across reopens, extension changes, and private windows — never shared between browsers or machines.
- TLS (JA4)
- How the browser's network stack introduces itself. Stable per browser build, so it helps re-link visits when the Bound ID legitimately resets.
- Network
- Coarse IP range, ASN, and geo. Changes with Wi-Fi, mobile data, or a VPN — datacenter and VPN networks add risk on their own.
- Cookies
- First-party attribution on this site. Cleared by incognito and browser switches; a warm marketing trail reads differently from a cold blank profile.
- Extensions
- Risk context only — AI agents, autofillers, and anti-detect tools stand out. Installing or removing one never changes the Bound ID.
- Behavior
- Pointer, typing, and dwell aggregates from this page. Humans are messy; scripts are instant, linear, or silent.
Next
Put the same check on signup
Free forever — 1,000 live API checks / month. Unlimited sk_test_ keys never bill. No credit card.
Account → verify domain → SDK or POST /api/v1/check