Live demo · real production endpoint

This is your device.

No login. No cookie. We're reading this device's own characteristics and matching them at the global edge — right now.

collect.darkid.io / v0 / collectreading
visitorId · this browser · stable across reload & incognito
reading device_
Continuous authentication · behavioural biometrics

Move your mouse around and type a sentence below — darkid learns the rhythm of how you drive the session, then flags if someone else takes over.

Now prove it. Reload this page — the visitorId (this browser) holds. Open this URL in an incognito / private window — still the same. Incognito wipes cookies and storage, so a stored ID couldn't survive. darkid's does, because it's matched from the device itself.

The darkid user above is the person behind the device — a stable, speculated id built with no login, no sign-up. basis: account means a hashed account hint deterministically linked your devices; device means one recognised device; network means repeated shared-network co-occurrence. Confidence reflects certainty without a deterministic anchor.

Want to see the verdict flip? Open this page with a headless browser — Playwright, Puppeteer, or any automation tool — and watch the kind switch to Agent and the automation score climb.

Even when a browser updates — new version, new canvas — darkid still recognizes the device from its stable hardware, GPU and network core.

On Chrome for Windows, darkid also silently issues a device-bound key — a credential minted in the machine's secure hardware (TPM) that the browser re-signs in the background, with no prompt and nothing for you to do. When you see the ⛨ device-bound key chip, this session is cryptographically pinned to this physical device, so a stolen cookie alone can't impersonate it. Other browsers simply skip it — the passive recognition above still works everywhere.
darkid.io · see in the dark · home · console
signals are hashed for this demo only · IPs are never stored raw