Why This Test Is Different From a DNS Leak Test
If you've already run a DNS leak test and passed, that's good — but it doesn't mean you're in the clear. WebRTC leaks are a separate issue entirely. A DNS leak exposes your browsing history to your ISP. A WebRTC leak exposes your real IP address directly to websites — and it bypasses your VPN at the browser level, not the network level.
You can have a perfectly clean DNS leak test and still have a WebRTC leak. Running both tests is the only way to know where you actually stand.
Check for WebRTC leaks right now — takes 10 seconds, no account needed.
Run the WebRTC Leak Test →How to Run the Test — Step by Step
Before connecting your VPN, run the test once to see your real public IP. Write it down. This gives you a clear comparison point for the next step.
Open your VPN app and connect fully. Make sure the status shows connected — not just connecting.
Visit the test tool. It sends WebRTC requests from your browser and records every IP address that responds. The whole process takes about 10 seconds.
If the real IP you noted in step 1 appears in the results — you have a leak. If only your VPN's IP appears — you're protected.
Reading Your Results
WebRTC tests typically show three types of IP addresses. Here's what each one means:
Your real IP is hidden. WebRTC is routing through your VPN. No leak detected.
This is your internal network address — shared by millions of people. Lower risk, but confirms WebRTC is active. Worth fixing to be thorough.
Your actual IP address is visible despite the VPN. Any website can see your real location. This is a confirmed WebRTC leak — fix it before continuing.
💡 IPv6 leaks are easy to miss. If the test shows an IPv6 address that matches your real connection, that's also a leak — even if your IPv4 address looks clean.
What to Do If You Have a Leak
The fix depends on your browser. Start here:
Firefox — the cleanest fix
- Type about:config in the address bar
- Search for media.peerconnection.enabled
- Set it to false
This fully disables WebRTC. Browser-based video calls won't work, but your IP is completely protected.
Chrome and Edge — use an extension
Chrome doesn't allow disabling WebRTC natively. Install a WebRTC control extension — WebRTC Leak Prevent or uBlock Origin with WebRTC protection enabled. Both are free and available in the Chrome Web Store.
Check your VPN settings
Some VPNs include a WebRTC leak protection toggle in their advanced settings. If yours does, enable it — this is the lowest-friction fix and doesn't affect normal browser use.
After any fix, run the test again. Assume nothing until you've verified the result changed.
Run Both Tests for Complete Coverage
WebRTC and DNS are two separate leak channels. Fixing one doesn't fix the other. If you care about privacy, run both:
- WebRTC leak test — checks if websites can see your real IP
- DNS leak test — checks if your ISP can see your browsing history
Passing both with your VPN active means your privacy setup is actually doing what it's supposed to.
Run the WebRTC test now — then check the DNS test below to cover both leak types.
Test for WebRTC Leaks →Frequently Asked Questions
How do I run a WebRTC leak test?
Connect your VPN, then visit a WebRTC leak test tool. If only your VPN's IP appears in the results, you're protected. If your real IP shows up, you have a leak.
What does a WebRTC leak test show?
It shows every IP address your browser is exposing through WebRTC — including your public IP, local network IP, and IPv6 addresses. Any of these can identify your real location.
Should I run the test with my VPN on or off?
Run it with your VPN on — that's when a leak matters. You can also run it without the VPN first to record your real IP as a comparison point.
What is a local IP address in the results?
A local IP like 192.168.x.x is your device's address on your home network. It's lower risk than a public IP leak, but confirms WebRTC is active and potentially exposing information.
Does passing this test mean I'm fully private?
No — this test only covers WebRTC leaks. Run a DNS leak test too. Both tests together give a complete picture of your VPN's actual protection.