What makes your browser identifiable
Every value below is computed in your browser and never uploaded. Learn how fingerprinting works.
Browser fingerprint
Computed in your browser. Not sent to or stored on our server.
What your browser exposes
Checking browser signals…
- Public IPrequestExposed
Sent with every request.
- Approximate locationrequestExposed
Derived from your IP, typically city-level.
- ISP / networkrequestExposed
Derived from your IP.
- Browser & OS (headers)requestExposed
Sent in the User-Agent header.
- Preferred languagesrequestNot exposed
Sent in the Accept-Language header.
- Timezonejs
- Screenjs
- CPU threadsjs
- Device memoryjs
- GPUjs
- Canvasjs
- WebGLjs
- Audiojs
- Fontsjs
- Tampered browser APIsjs
- JS engine fingerprintjs
- Voice listjs
- SVG renderingjs
- Permission statesjs
- WebRTC public IPjs
Where this data goes
Reaches our server: your IP address and standard request headers (user agent, languages, accepted formats). Every website receives these. We use them to answer the request and do not store them.
Stays in your browser: fingerprints, canvas, WebGL, audio and font results, screen and hardware values. They are computed and displayed locally and never uploaded during a normal visit.
Stored locally: the last test summary (IP, network and fingerprint hashes) is kept in your browser’s localStorage so “Test again” can show a comparison. Clear it any time from the comparison panel.
Blocked signals show as hidden or randomized. That is your browser protecting you, and it makes your fingerprint less stable.
Device & hardware
Reported by your browser. Browsers intentionally round or cap some values (memory, CPU threads), so treat them as approximate.
Test individual fingerprint signals
Open a focused test for a clearer explanation of what each value measures, how stable it may be and where it can mislead.