Privacy & Security Tools

Privacy Tools — IP, DNS Leak, WebRTC Leak, and Fingerprint Checks

A VPN that's "on" isn't the same as a VPN that's actually hiding you. Your real IP can still leak through WebRTC, your DNS queries can still route through your ISP instead of your VPN's resolvers, and your browser has a fingerprint that follows you around regardless of what your IP shows. These four tabs check each of those separately: an IP checker, a DNS leak test, a WebRTC leak test, and a browser fingerprint scan.

IP Checker

Shows your current public IP address the moment the tab loads, along with whether it's IPv4 or IPv6 and other location and network details. This is the number every website you visit already sees — checking it here is mostly useful for confirming a VPN or proxy is actually applied before you do something that depends on it.

DNS Leak Test

A DNS leak means your internet provider can still see which sites you're visiting even while a VPN is active, because your DNS lookups are quietly bypassing the VPN's tunnel. This test compares what two independent geolocation services (Cloudflare and ipapi.co) report about your connection to check for inconsistency — it's a practical proxy check rather than a direct query of your DNS resolvers, but a mismatch between the two is a real signal something's off.

WebRTC Leak Test

WebRTC — the browser technology behind video calls — can expose your real IP address through a side channel even when a VPN is masking it everywhere else. This has caught out plenty of people who assumed their VPN made them fully anonymous. Run the test and it shows you exactly what IP your browser's WebRTC implementation is broadcasting; if it matches your VPN's IP, you're fine, and if it shows your actual ISP address, you have a leak to fix.

Browser Fingerprint

Even with no cookies and a masked IP, your browser's specific combination of settings — screen resolution, installed fonts, GPU renderer, and how it draws a hidden test image via the Canvas API — can be unique enough to track you across sites. This scan reveals your fingerprint components, including a live canvas render, so you can see what a tracking script would actually collect.

Fixing a leak

If the WebRTC test shows your real IP, the fix depends on your browser: in Firefox, set media.peerconnection.enabled to false in about:config; in Chrome, an extension like uBlock Origin or a dedicated WebRTC-blocking extension closes the hole; Brave blocks WebRTC leaks by default. For a DNS leak, check that your VPN app has a "DNS leak protection" setting enabled, or manually point your system DNS at your VPN provider's resolvers.

Tips

Run all four tests with your VPN both on and off once, so you have a baseline for what "leaking" actually looks like on your setup versus what's normal. Re-run them after any VPN app update — leak-protection settings occasionally reset.

Limitations

These are point-in-time checks, not continuous monitoring — a leak that shows up during a video call (which actively uses WebRTC) might not appear in this static test. And no combination of these fixes makes you fully anonymous: the sophisticated tracking used by large ad networks (cross-device matching, first-party data correlation) goes well beyond what a browser fingerprint scan can show or defend against. Tools like these help you catch obvious leaks, not guarantee anonymity.