VPN & Proxy Leak Test
Find out if your VPN or proxy is leaking your real IP address through WebRTC.
Press the button. We detect your public IP and ask your browser what network addresses it can see through WebRTC. If anything other than your VPN or proxy IP shows up, you have a leak.
What is an IP leak?
A VPN or proxy is supposed to hide your real IP address. A leak is any way your real address slips out anyway. The most common one is WebRTC, a browser feature for voice and video calls that can reveal your real local and public IPs even while the VPN is connected. DNS leaks are the other classic: your DNS requests (which site am I visiting) go to your provider instead of through the VPN tunnel.
What this test checks
This page runs two checks. First it finds your public IP as the internet sees it right now. Then it asks your browser, through WebRTC, which network addresses it can discover on its own. If WebRTC exposes addresses your VPN should be hiding, the test flags it. For DNS, no web page can directly see your DNS servers, so the honest check is this: if your public IP here matches your VPN server location, your DNS is almost certainly going through the tunnel too.
How to fix a WebRTC leak
- In Chrome or Edge, install a WebRTC leak prevention extension and set it to block non-proxied traffic.
- In Firefox, open about:config and set media.peerconnection.enabled to false if you do not need browser calls.
- Use a VPN client with a kill switch and built-in leak protection, and re-run this test after every change.
Frequently asked questions
Is the leak test free?
Yes, free with no signup. Everything runs in your browser.
I see a 192.168.x.x address. Is that a leak?
Those are local network addresses from your router. They do not identify you on the internet, but privacy-focused users still prefer to hide them.
My public IP matches my VPN. Am I safe?
Mostly. It means your traffic is going through the VPN. Re-test after reconnecting, because leaks often appear only in specific moments.
Can a proxy leak too?
Yes. Browser-based proxies do not cover WebRTC or DNS by default, which is exactly why this test exists. Check with What Is My IP too.