Privacy

How to Test Your VPN for IP, DNS, and WebRTC Leaks

A VPN that 'connects' isn't the same as a VPN that protects. Use the IP checker below before and after connecting — then work through DNS and WebRTC.

Looking up IP details…

Test 1: IP leak

Disconnect your VPN. Note your IP, ISP, and country above.
Connect to a VPN server in a different country.
Reload this page. The IP, ASN, and geolocation should now match the VPN provider — not your ISP.

Test 2: DNS leak

Even with a working tunnel, your computer may still ask your ISP's DNS server to resolve domains — defeating the privacy goal. Run a DNS lookup with the VPN connected. The resolver returning the answer should belong to your VPN provider (or a neutral one like Cloudflare), not your ISP. If you see your ISP's name, enable “Force DNS over VPN” in your client settings.

Test 3: WebRTC leak

WebRTC is a browser feature for peer-to-peer connections that can reveal your real IP even through a VPN. Open about:webrtc in Firefox or any WebRTC test page. If you see your real public IP or local network IP, install an extension to disable WebRTC or use a browser like Brave that blocks it by default.

When everything passes

Don't assume it stays that way. VPN servers fail open, clients update, and OS changes can reintroduce leaks. Pro users can schedule a recurring IP & DNS check so any future leak is caught the day it appears, not months later.

Recommended next steps

Diagnostic workflow

1
Check your public IP
Confirm the tunnel is changing what the internet sees.
IP checker
2
Test DNS resolver
Verify lookups are going through the VPN, not your ISP.
DNS lookup
3
Check resolver speed
VPN DNS that's slow makes everything feel broken.
DNS speed test
4
Schedule recurring checks
Catch leaks the day a client update introduces them.
Open dashboard

Frequently asked questions

What's a VPN 'leak'?

When some of your traffic bypasses the VPN tunnel and reveals your real identity. The three common types are IP leaks (your true IP is exposed), DNS leaks (lookups go to your ISP's resolver), and WebRTC leaks (browsers expose your local IP via JavaScript).

How do I know my VPN is actually working?

Check your public IP before and after connecting. If the IP, ASN, and geolocation change to the VPN provider's network, the basic tunnel is up.

Why do DNS leaks happen on a working VPN?

Many operating systems send DNS queries outside the tunnel for speed. Quality VPN clients force DNS through their tunnel; cheaper ones often don't.

Is a WebRTC leak dangerous?

It exposes your local network IP and sometimes the real public one, even while the VPN is connected. It's a real privacy issue for anyone using a VPN for anonymity.

What if I find a leak?

Switch to a VPN protocol like WireGuard or OpenVPN with leak protection enabled, disable WebRTC in your browser (or use an extension), and force DNS through the tunnel in your VPN client settings.