How to Run a VPN Leak Test for DNS, IP and WebRTC
A VPN app can show a green shield and the word "Connected" while your laptop quietly sends every website lookup to your internet provider anyway. Nothing in the app warns you.

A VPN app can show a green shield and the word "Connected" while your laptop quietly sends every website lookup to your internet provider anyway. Nothing in the app warns you. Pages load, the speed looks normal, and the only way to know is to check from the outside what the rest of the internet can see about you.
That check takes about five minutes and needs nothing you have to install. I run it on every new device, after every major operating system update, and whenever I switch VPN apps, because each of those can change how traffic gets routed. Here is the test I use, what the results mean, and what to change when something leaks.
The three things that can slip past a VPN
A leak means some piece of traffic leaves your device outside the encrypted tunnel. There are three common kinds, and each one exposes something slightly different.
IP leaks are the obvious one: a site sees your real public address instead of the VPN server's. This usually happens during reconnection, when the tunnel drops for a second and your device falls back to the normal connection, or when your network has IPv6 and the VPN only handles IPv4.
DNS leaks are more common and harder to spot. DNS is the lookup that turns a name like a news site into an address. If those lookups go to your provider's DNS servers rather than the VPN's, your provider gets a running list of every domain you visit, even though the content itself stays encrypted. Windows is particularly prone to this because of a feature that sends lookups to several network adapters at once and takes whichever answers first.
WebRTC leaks come from the browser, not the VPN. WebRTC is the technology behind video calls in a browser tab, and to set up a call it can ask your device for its local and public addresses. A site running a small script can read those addresses without you making any call at all.
How to run the test
Do this on the device you actually use, on the network you actually use. Results on home Wi-Fi can differ from results on a phone hotspot or office network.
- Disconnect the VPN and visit a leak testing site such as ipleak.net or browserleaks.com. Write down your real public IP address and the name of your provider that appears next to the DNS servers. This is your baseline, the thing you do not want to see later.
- Connect the VPN to a server in a different country, so a leak is easy to spot. Wait for the app to say it is connected, then reload the test page.
- Check the IP address shown at the top. It should match the VPN server's location and should not match your baseline. If you have IPv6 at home, check that the IPv6 line is either blank or also belongs to the VPN.
- Look at the DNS section. Run the extended test if the site offers one; on dnsleaktest.com it sends a few dozen lookups and takes about 30 seconds. Every server listed should belong to the VPN company or a provider it names. If your home internet provider appears even once, you have a DNS leak.
- Scroll to the WebRTC result. If your real public IP appears there, the browser is leaking it. A local address like 192.168.1.23 is less serious but still worth hiding.
- Finally, test a dropped connection. Toggle Wi-Fi off and on, or switch from Wi-Fi to a phone hotspot while the test page is open, and reload immediately. This is where kill switch problems show up.
Repeat the whole thing in a second browser. Chrome, Firefox, and Safari handle WebRTC and secure DNS differently, so one clean result does not cover the others.
Reading the results without panicking
Some results look alarming and are not. If the DNS servers listed belong to Cloudflare, Google, or Quad9, that may simply mean your VPN uses one of them, or that your browser has its own secure DNS setting turned on. Check the VPN company's support page; most state which resolver they use. What matters is that your home provider does not appear.
Seeing a different city than the one you chose is also normal. IP location databases are often wrong by a few hundred kilometres. Only worry if the country is wrong or the address matches your baseline.
A leak that appears only during step 6 is a timing issue, not a constant one. It means a second or two of traffic escapes during reconnection. For most people that matters little. For anyone on a network where that brief exposure carries real risk, it is the most important result on the page.
Why a "leak protection" toggle is not proof
Most VPN apps now have a setting called DNS leak protection, IPv6 protection, or something similar, and the common advice is to turn it on and forget about it. I would turn it on, but I would not trust it without testing. I have seen the toggle switched on in two well known apps while the extended DNS test still listed the home provider, because the operating system had cached a custom DNS setting on the network adapter that the app did not override.
The same goes for kill switches. Some only block traffic when the app notices the tunnel has dropped, which can take several seconds. Others, usually labelled "always on" or "block connections without VPN", stop traffic at the system level from the start. If you want to understand the difference, the explanation of how a VPN kill switch works goes through both types.
Fixes for each kind of leak
For a DNS leak, first switch on the VPN app's DNS protection setting and reconnect. If the leak survives, remove any custom DNS you set on your network adapter or router, since some apps defer to it. On Windows, the built in "Always On VPN" and "Block connections without VPN" options under Settings, Network, VPN are worth enabling for apps that use the system VPN profile. Changing the protocol can also help; WireGuard based connections tend to handle DNS more cleanly than older OpenVPN setups, and the guide to VPN protocols covers which to pick.
For an IPv6 leak, use the app's IPv6 setting if it has one. If it does not, you can disable IPv6 on the network adapter; you lose nothing for normal browsing on most home connections.
For WebRTC, Firefox lets you set media.peerconnection.enabled to false in about:config, which stops it entirely and also breaks browser based video calls. In Chrome and Edge, an extension such as WebRTC Network Limiter restricts what is shared. Safari exposes far less by default and usually passes this check without changes.
For reconnection leaks, enable the strictest kill switch mode available and test again. If it still leaks, I would treat that as a reason to switch providers rather than something to work around.
Set a reminder to rerun the test after your next system update. It takes less time than reading the patch notes, and more of the basics are collected in the VPN basics section.
FAQ
How do I know if my VPN is leaking?
Connect to the VPN, visit a leak test site, and compare the IP and DNS servers shown with your results when disconnected. Any match with your own provider is a leak.
Is a DNS leak dangerous?
It exposes which websites you visit to your internet provider, but not what you do on them. How much that matters depends on why you use a VPN.
Do mobile VPN apps leak too?
They can, especially when switching between Wi-Fi and mobile data. Android's "Always-on VPN" and "Block connections without VPN" settings close most gaps.
How often should I run a VPN leak test?
After installing a new VPN, after major system or browser updates, and whenever you change networks you rely on regularly.
More in VPN Basics
VPN Basics
VPN vs Proxy vs Tor and Which One Fits the Job
A reader wrote to me in September after cancelling his VPN subscription.
VPN Basics
How to Choose a VPN Server Location for Each Task
You open the VPN app and it offers you 94 countries, a "fastest server" button and a map with glowing dots.
VPN Basics
VPN No Logs Policy and What It Actually Promises
Nearly every VPN provider promises it keeps no logs, and the claim is printed so large on their homepages that it starts to...