WebRTC leak test
Find out whether your browser gives away your real IP address through WebRTC, even when the page itself loads through a proxy or VPN. Switch your proxy on, then run the test. Free, no sign-up, nothing stored.
- Compares WebRTC with your web IP
- No sign-up
- Nothing stored
Asking your browser which addresses WebRTC would reveal.
Every address WebRTC offered
These are the ICE candidates your browser produced. Any website can ask for the same list without showing you anything.
| Type | Protocol | Address | What it is |
|---|---|---|---|
| The list appears here once the test has run. It needs JavaScript. | |||
Why WebRTC leaks, and how to stop it
WebRTC is the browser feature behind video calls. It finds the fastest route between two devices, and it does that outside your proxy.
Why it leaks
To connect two browsers directly, WebRTC asks a STUN server what your public address is. That request travels over UDP, around an HTTP proxy, so the answer is your real IP.
What counts as a leak
A public address in the list that differs from the IP websites see. Addresses ending in .local, or starting with 192.168 or 10, are local and stay inside your network.
How to stop it
In an anti-detect browser, set WebRTC to replace or disable it in the profile settings. In Firefox, set media.peerconnection.enabled to false in about:config. Chrome has no switch of its own, so use an extension that limits WebRTC.
Then check the rest: What is my IP shows the address websites see, and the browser fingerprint checker shows everything else your browser reveals.
WebRTC leak questions
What is a WebRTC leak?
WebRTC lets browsers talk to each other directly, for calls and file transfer. To do that it discovers your network addresses, and a web page can read them. If one of them is your real public IP while you browse through a proxy or VPN, that is a WebRTC leak.
Does a proxy stop WebRTC leaks?
Not by itself. An HTTP proxy only carries web requests, and WebRTC’s address discovery goes around it. You stop the leak in the browser: by disabling WebRTC, or by using a browser profile that replaces the address WebRTC reports.
I see an address ending in .local. Is that a leak?
No. Modern browsers hide your local network address behind a random .local name, so sites cannot read it. It says nothing about your public IP.
How do I fix a leak in an anti-detect browser?
Open the profile’s settings and look for the WebRTC option. Set it to the mode that replaces the WebRTC address with the proxy’s IP, or switch WebRTC off. Then run this test again with the profile’s proxy on. The setup guides cover the proxy side.
Why does the test say it could not read the IP websites see?
That address comes from a free public IP echo service. Previews, strict networks and some browser extensions block the request. The WebRTC half of the test still runs, and you can compare the address with your proxy IP by hand.
Do you store the results?
No. The test runs in your browser. It contacts a public STUN server, which is how WebRTC discovers addresses, and ipify for the IP websites see. Neither result is sent to us or saved.
Need a clean IP to go with a clean browser?
Residential IPs in 195 countries from $4.75, or a Static Residential IP from $1.49 a month. No KYC, crypto or card.