Browser Fingerprint Analyzer

Every browser leaks small details — your GPU model, installed fonts, screen size, audio stack behavior. Individually these are harmless. Combined, they form a fingerprint that's often unique enough to track you without cookies.

We call browser APIs the same way any tracker would, then check if the responses are internally consistent. If navigator.plugins says 0 but the user agent claims Chrome, or if Object.getOwnPropertyDescriptor shows a getter was replaced — we flag it.

WebRTC needs your real IP to set up peer-to-peer connections. It asks your OS directly, bypassing any proxy or VPN you've configured. If we see a public IP in the STUN response that doesn't match your server IP, you're leaking.

We store a one-way SHA-256 hash of your fingerprint and your IP address (as a separate correlation signal — never mixed into the hash). This powers the cross-session detection and crowd comparison. The hash can't be reversed to reconstruct your browser configuration.

Tor Browser is the gold standard — it normalizes everything. For daily use, Brave with strict fingerprint protection works well. Ironically, installing a bunch of privacy extensions often makes your fingerprint more unique, not less.

We draw specific shapes and text on a hidden canvas, then hash the pixel output. Different GPUs, drivers, and OS font renderers produce slightly different results. Same idea for WebGL — your GPU's exact parameter set (max texture size, extensions, shader precision) is surprisingly unique.

We create an OfflineAudioContext, run a triangle wave through a dynamics compressor, and hash a slice of the output buffer. The processing pipeline varies across hardware and OS audio stacks, so the output is device-specific.

After running your tests, we compare each module hash against every other visitor who's used this tool. If 500 other people share your canvas hash, that module blends well. If your combination is seen for the first time — you stand out.