Browser Privacy Check
See exactly what your browser leaks about you.
Runs entirely in your browser — nothing you enter is uploaded, logged, or tracked.
Every website you open can silently read dozens of signals from your browser — and combine them into a “fingerprint” that tracks you even without cookies. This tool shows you the same signals a tracker sees: your fingerprint, whether WebRTC leaks your real IP (even behind a VPN), your GPU, screen, fonts, timezone and more. It all runs locally — nothing is uploaded — so you can see your exposure and decide what to harden.
computing… A tracker can recognize this combination of signals — no cookie needed. WebRTC IP leak
Device & browser
Rendering fingerprint
Detected fonts
Nothing on this page is uploaded — these are the exact signals any website can read about you, computed locally so you can see (and reduce) your exposure.
Frequently asked questions
Is any of this sent to a server?
No. Every signal is read and hashed entirely in your browser; nothing is transmitted, logged, or stored. It’s a mirror, not a tracker.
What is the WebRTC leak?
WebRTC can expose your local (and sometimes public) IP address to a site even when you’re on a VPN — a classic deanonymization leak. This tool gathers your browser’s own ICE candidates locally (no STUN server) and shows what they reveal. Modern browsers mask host IPs behind an mDNS “.local” name; if you see a real IP, that’s a leak worth fixing.
What is a browser fingerprint?
A combination of signals — canvas/WebGL rendering, fonts, screen, timezone, hardware — that is often unique enough to identify you across sites without any cookie. The fewer unique signals you expose, the harder you are to track.
How do I reduce my fingerprint?
Use a hardened browser (e.g. Tor Browser or Brave), disable WebRTC or use a VPN/extension that blocks the leak, keep extensions minimal, and avoid letting sites read your GPU/fonts. This page helps you see what changes actually move the needle.