Privacy & security
How to test your VPN
Check that your VPN hides your IP and isn’t leaking DNS or WebRTC.
Updated · First published · 9 sources
The short answer
Note your real IP address with the VPN off, then connect and check that sites now see only the VPN’s address. Then run DNS, WebRTC and IPv6 leak tests with free tools such as ipleak.net, dnsleaktest.com and BrowserLeaks, and check that the kill switch blocks traffic when the connection drops.
What should a VPN test check?
A VPN can look connected and still expose you. A full test checks five things:
- IP address: sites see the VPN server’s address, not yours.
- DNS: your lookups go to the VPN’s DNS servers, not your internet provider’s.
- WebRTC: your browser doesn’t reveal your real public address to web pages.
- IPv6: IPv6 traffic doesn’t bypass the tunnel.
- Kill switch: nothing goes out over your normal connection when the VPN drops.
Test on every device and browser you use, and again after updating the VPN app or your operating system.
How do you check that your IP address has changed?
- Turn the VPN off and open an IP checker such as YourPublicIP, ipleak.net, BrowserLeaks or dnsleaktest.com. Write down the IPv4 address, any IPv6 address, and the location shown.
- Connect to a VPN server, ideally in another country so the change is obvious.
- Reload the checker. Every address should now be different, and the internet provider shown should be the VPN’s hosting company, not yours.
- Check that the location roughly matches the server you picked. IP location databases are approximate, so a nearby city is fine.
If your real IPv6 address still appears while the IPv4 address has changed, you have an IPv6 leak. See below.
All of these checkers are free and need no account. YourPublicIP is run by the owner of PickMyVPN; using a second, independent checker confirms the result.
How do you test for DNS leaks?
With the VPN connected, run the extended test on dnsleaktest.com, which sends 36 lookups. Every DNS server listed should belong to your VPN provider or its hosting company. A server from your internet provider means your lookups are leaking.
If you see a server from Cloudflare, Google or another public DNS company, your browser is probably using DNS over HTTPS. Firefox turns DoH off on its default setting when a VPN is active; Mozilla lists no VPN exception for its Increased and Max settings. Our guide to DNS leaks explains each result and how to fix it.
How do you test for WebRTC leaks?
WebRTC lets browsers make voice and video calls directly between devices. To set up a call, the browser contacts a STUN server, which Mozilla’s documentation describes as “a protocol to discover your public address”. Web pages can read the addresses this finds.
With a VPN that carries all your traffic, the address found should be the VPN’s. The IETF’s guidance on WebRTC address handling explains the exception: with a split-tunnel VPN, WebRTC can discover the internet provider’s address that the VPN runs over.
- Connect to the VPN and open BrowserLeaks WebRTC, or the WebRTC section of ipleak.net.
- Look at the public IP addresses the test finds.
- If your real public IP appears, you have a WebRTC leak. Turn off split tunneling for your browser, or check the VPN app’s leak protection settings.
A private address, such as one starting 192.168 or 10., identifies your device on your home network, not you on the internet. It isn’t the leak you’re looking for.
How do you test for IPv6 leaks?
Many networks give devices both an IPv4 and an IPv6 address. An IETF report on VPN leakage explains that a VPN which only handles IPv4 can let IPv6 traffic bypass the tunnel, and that devices often prefer IPv6 when a site supports it.
- Connect to the VPN and open test-ipv6.com, or check the IPv6 line on BrowserLeaks or ipleak.net.
- If it shows no IPv6 address, either your network has no IPv6 or the VPN blocks it; both are fine.
- If it shows an IPv6 address from the VPN, the VPN supports IPv6. That’s also fine.
- If it shows the IPv6 address you noted with the VPN off, or names your internet provider, IPv6 is leaking. Turn on the app’s IPv6 leak protection.
How do you test the kill switch?
Turn on the kill switch, connect, and start a long video. Then turn Wi-Fi off and on again, and reload an IP checker straight away. You should see either no connection or the VPN’s address, never your real one. Disconnecting in the app isn’t a fair test, because some apps lift the block when you disconnect on purpose. Our kill switch guide covers the settings on each platform.
What should you do if a test fails?
- Check that the app shows you as connected, then reconnect or try another server.
- Turn on DNS leak protection, IPv6 leak protection and the kill switch in the app.
- Leave the app to set DNS rather than entering DNS servers by hand.
- Check your browser’s DNS over HTTPS setting, and turn off split tunneling for your browser.
- Update the VPN app and restart the device, then test again.
- If it still leaks, contact the provider’s support. If it can’t fix it, choose another service from our [rankings](/).
Common questions
How do I know if my VPN is working?
Check your IP address with the VPN off and on. If sites see a different address and location, and DNS and WebRTC tests show no trace of your real IP or internet provider, it’s working.
What is a WebRTC leak?
It’s when a browser feature for voice and video calls reveals your real public IP address to a web page, even with a VPN on. It mostly happens when the browser’s traffic isn’t fully routed through the VPN, for example with split tunneling.
Why does my VPN show the wrong location?
IP location databases are estimates, so a checker may place a VPN server in a nearby city or a different region. What matters is that the address isn’t yours.
How often should I test my VPN?
When you first set it up, after app or operating system updates, and on any new device or browser.
Sources
We checked this guide against these pages on October 22, 2026.
- Introduction to WebRTC protocols · MDN Web Docs (Mozilla), Sep 17, 2026
- RFC 8828: WebRTC IP Address Handling Requirements · IETF
- RFC 7359: Layer 3 Virtual Private Network (VPN) Tunnel Traffic Leakages in Dual-Stack Hosts/Networks · IETF
- Configure DNS over HTTPS protection levels in Firefox · Mozilla Support
- Standard vs extended test: what’s the difference? · DNS leak test
- IPleak.net · IPleak.net
- Your public IP · YourPublicIP (run by PickMyVPN’s owner)
- WebRTC leak test · BrowserLeaks
- Test your IPv6 connectivity · test-ipv6.com