Browser fingerprint

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 IPrequest
Sent with every request.
Exposed
Approximate locationrequest
Derived from your IP, typically city-level.
Exposed
ISP / networkrequest
Derived from your IP.
Exposed
Browser & OS (headers)request
Sent in the User-Agent header.
Exposed
Preferred languagesrequest
Sent in the Accept-Language header.
Not exposed
Timezonejs
Screenjs
CPU threadsjs
Device memoryjs
GPUjs
Canvasjs
WebGLjs
Audiojs
Fontsjs

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.