Mini App

Visitor tagging, browser hints, and passkey labels in one demo.

This page creates an anonymous visitor record with a cookie-backed token, shows the coarse browser and OS hints your frontend can infer, and lets you register a sample user with an optional WebAuthn passkey.

Server View

Anonymous visitor record

The server stores a hashed visitor token plus IP and user-agent fingerprints as supporting metadata.

Loading visitor state...

Client View

Detected browser hints

Detecting browser and OS...

Passkey Preview

Derived device label

Passkey on this device

Create a passkey in the form below to inspect the stored metadata.

Example Flow

Create a demo account

Passwords are hashed server-side. Passkeys are optional unless you enable the staff-style toggle.

Demo scope: the backend verifies the WebAuthn challenge and origin, then stores the returned credential fields. Full production attestation and assertion verification should use a dedicated WebAuthn server library.

Result

Registration response

No registration submitted yet.

Local Store

Persisted demo records

The JSON store will appear here after the first API call.

What To Look For

Signals this app demonstrates

  • Anonymous visitors are tagged by a random cookie token, not by IP alone.
  • IP and user-agent hashes are useful side-channel signals, not identity anchors.
  • OS and browser labels come from client hints and the user agent string.
  • Passkey labels are derived from device hints and transports, not stored as a separate field.