Browser Privacy Check
One click runs two checks in your browser: a WebRTC leak test (the classic way a real IP escapes even with a VPN on) and a fingerprint surface report showing the traits — screen, timezone, language, canvas, WebGL — that let sites recognize you without cookies. Nothing is logged; the only network call is the IP comparison you already get on this site.
WebRTC leak test
—
- Apparent IP (what sites see)
- —
- IPs exposed by WebRTC
- —
Fingerprint surface — what makes this browser recognizable
| Trait | Your value | Note |
|---|
No single row identifies you — the combination often does. Common values help you blend in; unusual ones stand out. A VPN changes none of these — see the VPN guide.
Reading your results
- WebRTC: if a public IP appears here that differs from your apparent IP, your real address is leaking around the VPN — fix it in the VPN app (WebRTC protection) or browser settings. Local addresses like
192.168.x.xor obfuscated.localnames are normal and low-risk. - Fingerprint surface: no single trait identifies you; the combination often does. The report marks which of your traits are common (crowd-blending) vs unusual (identifying). This is exactly the tracking a VPN cannot stop — the full picture is in our VPN guide.
Frequently asked questions
Is a WebRTC leak dangerous?
If you use a VPN for location privacy — yes, it can expose your real public IP to sites that ask for it. Without a VPN it reveals nothing your normal traffic doesn't already. Most VPN apps and extensions can block it.
Can I stop browser fingerprinting?
You can reduce it: mainstream browser + default window size + fewer extensions makes you blend in; Tor Browser goes furthest by making everyone look identical. Ironically, exotic anti-fingerprint tweaks can make you MORE unique.
Do you store any of these results?
No. The checks run and render locally; the page makes no logging calls. It's a mirror, not a scanner.