A VPN can look connected in the app but still leak your real IP through DNS requests, WebRTC, or a briefly dropped connection. These four checks confirm your VPN is doing its job.
Test 1: IP address leak
Open ipleak.net or ipchicken.com without the VPN and note your real IP and location. Connect the VPN, refresh the page. The IP and country should now match your VPN server, not your real ISP.
Test 2: DNS leak
DNS leaks reveal what sites you visit even if your IP is hidden. Use dnsleaktest.com and run the 'Extended test'. Every DNS server that appears should belong to your VPN provider — not your ISP.
Test 3: WebRTC leak
Browsers can leak your real IP through WebRTC. Test at browserleaks.com/webrtc while connected. If you see your real public IP, disable WebRTC in the browser or use a VPN with built-in WebRTC blocking.
Test 4: Kill-switch drop test
Start a download or ping test. Disable your Wi-Fi for a few seconds and re-enable it. A working kill switch should block all traffic until the VPN reconnects — the download should pause, not fail with a burst of unprotected packets.
If something leaks
Switch protocols (try WireGuard), enable the kill switch, and turn on your VPN's DNS leak protection. If leaks persist, change provider — it's a serious quality problem.
Frequently asked questions
QHow often should I test my VPN?
Once after installation, and again after any major app or OS update.
QDo I need any special software?
No. A browser is enough for all four tests.
QWhat's a WebRTC leak?
A browser feature (used for video calls) that can broadcast your real IP even through a VPN.
Related guides
Keep going down the rabbit hole 🐇
Ready to pick a VPN?
Compare the providers we have tested against every criterion in this guide.
See top VPNs