Server request
Values observed at the Cloudflare edge when this page calls the telemetry endpoint /api/whoami.
Browser runtime
Local JavaScript-readable browser, locale, and runtime identity fields.
Hardware & display hints
Approximate device capabilities exposed by browser APIs and media queries.
Proxy, TLS & privacy headers
Cloudflare edge, TLS and network context, privacy preferences, and cookie presence.
Client Hints headers
Optional browser-supplied hardware/software hints requested by the origin.
Accept-CH, and many browsers intentionally omit them.Graphics, audio & fonts
Rendering surfaces often used in fingerprinting tests.
Privacy & storage state
Browser preferences, permissions states, and local storage availability.
Capability surface
Modern APIs that reveal what the browser and device can do.
Local fingerprint demo
A digest of selected local attributes. The digest inputs are shown below and are not posted back.
Collecting local inputs...
What this demonstrates
The surprise is usually not one field. It is the combination.
User-Agent, Accept-Language, Client Hints, Fetch Metadata, referrer, and proxy headers can describe your browser, language, navigation path, and network route.
Screen geometry, timezone, hardware hints, storage estimates, connection type, permissions states, and rendering quirks can be read without a login.
Modern browsers may freeze, round, omit, or randomize values. That helps, but correlated low-entropy signals can still be useful to trackers.