Privacy tools that let you verify your own privacy protection rather than take a vendor's word for it. The IP leak test checks what address the outside world sees when you load a page, and whether WebRTC, DNS, or a partially-routed VPN can expose your real one. The privacy leak test scans for the quieter leaks — fingerprinting surfaces, tracking headers, and the identifiers a site can assemble without ever storing a cookie. 1 of the 2 tools in this category run entirely in your browser and your input never leaves your device. The other 1 (IP Leak Test) run on our server, so what you type is sent to us for processing. Each tool page states which it is. Use them before and after enabling a VPN to confirm your protection is working. How to use: open the tool, allow any permissions it asks for (browser mic, camera and location are never requested), and read the report rather than just the verdict. LaiUse never logs your results and never sees your real IP — all checks happen client-side. The IP leak test answers one question: what address does the outside world see when you load this page? It compares the address your browser reports through WebRTC, through DNS resolution, and through the HTTP request itself, then tells you when they disagree. That disagreement is the finding worth acting on, because it is the signature of a VPN that is only partly routing your traffic, or of a browser whose WebRTC setting bypasses the tunnel entirely. A VPN client that routes HTTP traffic but leaves UDP alone — which is the default for many of them — will show your real address through WebRTC while every website you visit sees the VPN address. From the outside, those two facts together identify you far more precisely than either alone, and the whole point of a VPN is that the two match. The mechanism behind WebRTC is worth understanding, because it is the reason this class of leak keeps resurfacing. WebRTC is the browser API that supports video calls and peer-to-peer connections. To establish a direct connection between two browsers, it needs to know your local network address, and modern browsers will reveal a local or public address to a web page that asks for it — a capability that was built for legitimate use and that a good number of sites have abused. Disabling WebRTC outright breaks video calling, so the practical advice is usually to keep it on and route it through the tunnel, and to check that it is in fact being routed. That is exactly what the comparison above tells you: if the WebRTC address and the HTTP address differ, the tunnel is not carrying WebRTC, and whatever else your VPN is doing, this particular leak is open. The privacy leak test covers the quieter surfaces. It looks at which tracking headers your browser sends, whether your canvas, fonts, timezone and screen dimensions combine into a stable identifier, and how much a site can tell about you without ever storing a cookie. Fingerprinting works differently from tracking: a cookie is a file the site gives you and asks you to bring back, and clearing it resets the relationship. A fingerprint is computed from properties of your browser and machine that you never agreed to share, it is stable across sessions and across sites, and clearing your cookies does nothing to it. The practical consequence is that "clear your cookies" is not a privacy reset, and a site that fingerprints you can still recognise you on your next visit — or recognise that you are the same person who visited a different site an hour ago. Reading the results is a skill of its own, and the tool is deliberately explicit about what each check can and cannot establish. A header check shows what this browser sent to this particular page; it does not tell you what a tracker with an embedded script would have learned, because that behaviour is chosen by the script and not by the browser. A canvas or font check shows whether your environment is distinctive enough to identify; it does not tell you whether any site is actually fingerprinting you, which requires seeing the scripts that run. And a check that passes is evidence about the vector it covers, not a general certificate of privacy. Read it before you enable a VPN rather than after — a leak that you only find once your traffic is already on the wrong exit node is a leak you have to react to rather than one you can prevent. Neither tool asks for the microphone, the camera or the location, and neither writes your address to a server or a log. That matters more than it sounds: the first thing many leak-test sites do with a fresh visitor is send the address they just learned to a third party, which converts the diagnostic into the leak. Running these checks in your own browser, with the results computed on the page and never transmitted, keeps the diagnostic from becoming the thing it is diagnosing. Use them before you switch a VPN on and again afterwards, and compare the two reports rather than looking at a single verdict — a check that passes in one run and fails in the other is telling you something that a green tick on its own would hide. Two things worth adding to that picture, because they change what a result means. First, a leak test is a snapshot, not a verdict. It tells you what was true at the moment the page loaded, from the network path your browser happened to take, and some of what it measures changes between a home connection and a corporate one — a proxy that terminates TLS will look like a different address to the outside world, and a captive portal will look like a leak. Read the individual results rather than the headline, and re-run from a network you actually use if the answer matters. Second, there is a limit to what any of this can tell you. A fingerprint is a combination of browser and machine characteristics, and a check that reports "your fingerprint is distinct" is telling you that a site could single you out — not that one is doing it. Establishing that requires observing what a specific site does, which is outside what a local check can reach. What a local check can do is give you a baseline and a direction: if a particular vector comes back as distinctive, then reducing it is worthwhile, and the usual remedies are unglamorous and effective — a standard browser profile rather than a heavily modified one, common font settings, a consistent window size, and blocking third-party scripts and trackers rather than relying on the fingerprint being too weak to be useful. Privacy here is less about hiding in a crowd than about not handing over a stable identifier, and the tools on this page tell you which of your identifiers are the stable ones.
Check if your real IP address is exposed. Detect WebRTC, DNS, and VPN leaks to protect your privacy online.
Test your browser for privacy leaks. Check fingerprinting, tracking scripts, and data exposure across multiple vectors.