WebRTC Leak Test
Check whether your browser's WebRTC stack reveals a public IP address that differs from the one your traffic uses, which would defeat a VPN or proxy. The test runs automatically when the page loads.
- Runs in your browser
- Free to use
About this tool
Even with a VPN connected, a browser can give away your real address: WebRTC asks a STUN server "what is my public IP" to set up peer-to-peer connections, and that answer may come from your real interface rather than the tunnel. The WebRTC Leak Test reproduces that request, lists every public address exposed through ICE candidates, compares it with the address our server sees and gives a plain yes/no leak verdict, plus whether RTCPeerConnection and RTCDataChannel exist at all.
Thinking of disabling WebRTC? Keep in mind that meeting applications such as Google Meet rely on it: disabling WebRTC or changing its settings in the browser can cause connectivity or functionality issues during calls.
Check the exposed IPs with the IP Blacklist Check.
How to use it — quick steps
- 01
Let the test run
It starts when the page loads: the browser gathers ICE candidates while we read your remote IP.
- 02
Compare the addresses
The table lists the public IPs WebRTC exposed, the address your traffic uses and whether they match.
- 03
Read the verdict
A leak means WebRTC shows an address your VPN or proxy should hide; the note explains what to do about it.
Key features of this tool
Real leak check
Compares the public addresses gathered through STUN with the address your HTTP traffic arrives from, exactly how leak sites work.
Capability report
Shows whether RTCPeerConnection and RTCDataChannel are available, so you can confirm that a WebRTC-blocking extension is effective.
Instant and repeatable
Runs on page load and can be repeated after changing VPN servers or browser settings by clicking the "Run the test again".
Frequently asked questions
What is a WebRTC leak?
WebRTC lets browsers talk peer to peer and, to do so, discovers your public IP through STUN. That request can bypass a VPN or proxy, so a website can learn your real address even though your web traffic is hidden.
How do I stop it?
Use a VPN client that blocks WebRTC, install a WebRTC-blocking extension, or disable it in the browser (for example media.peerconnection.enabled in Firefox). Then run this test again: it should report no WebRTC or no leak.
Why do I see no public IP at all?
The browser blocked the STUN request, WebRTC is disabled, or your network filters UDP. In all those cases nothing leaks.
Is anything of mine sent to IPVoid?
Only the request that reads your remote IP, the same information every website receives. STUN candidates are processed in your browser.