The demo login is fixed and is not tied to a real account.
01 DEVICE BOUND SESSION CREDENTIALS
Bind your session
to this device.
Log in to see DBSC at work. Each time this session's cookie is refreshed, your browser has to prove it still holds the key it registered with the server.
02 YOUR SESSION
You are logged in.
The status below shows whether your browser has bound this session to a key on this device.
SESSION STATUS
Checking DBSC registration
Waiting for your browser to send a signed registration request.
Awaiting registration
A stolen session cookie usually works on any device. Whoever copies it can use it.
With DBSC, each session gets its own key pair. The browser keeps the private key, in hardware such as a TPM where it can, and the server keeps the public key.
The login cookie only lasts a short time. When it expires, Chrome holds the next request, signs a challenge with the private key, collects a new cookie, and then sends the request.
DBSC works alongside passwords, MFA, and WebAuthn sign-ins such as passkeys. It cannot help if malware already controls the device or the browser.
- 01
Open Chrome DevTools.
- 02
Select Application.
- 03
Expand Background services.
- 04
Select Device bound sessions.
- 05
Watch creation, challenge, refresh, and termination events.
- 06
Use Network to inspect the DBSC headers.
Events will appear after login.
Only event names and times are shown here. Proofs, cookies, challenges, and keys never reach this page.
This demo follows the W3C Editor's Draft of DBSC. It is not an RFC or a W3C Recommendation, and its details may change.