Browser fingerprint check

This page scans your browser as soon as it loads. See the ID a website can compute from it and the signals behind that ID.

The scan runs in this tab and its results stay here. Its WebRTC check contacts Google STUN servers, which can see your IP address. Data handling

Your fingerprint ID

The ID appears when the scan finishes.

Derived from this browser's setup, without cookies. It is not a uniqueness score.

Scanning this browser…

User agent
Waiting for the scan
Graphics
Waiting for the scan
Screen
Waiting for the scan
Reported hardware
Waiting for the scan
Time zone
Waiting for the scan
Languages
Waiting for the scan
WebRTC
Waiting for the scan
Consistency
Waiting for the scan
Inspect all collected values

The values appear here when the scan finishes.

How to read these checks

A fingerprint is a snapshot of observable browser values. The share of checks that returned a value measures how much could be collected; it does not measure identity, uniqueness, or the probability of fraud. IP location is approximate, and missing risk data stays unknown.

This page and the full checker start a scan when they load, and both include the WebRTC check that contacts Google STUN servers. This page does not save scan results; the full checker keeps sanitized history in this browser, which you can clear there. API submissions happen from the playground when you run a request. Review data handling.

CreepJS.org is this educational diagnostic and API. It is separate from Abraham Juliot’s CreepJS research project.