$0.00
A

WebRTC leak test

Check whether your browser reveals your real IP through WebRTC even with a proxy or VPN turned on.

Checking WebRTC...

What a WebRTC leak is

WebRTC is a browser technology for video calls and direct data exchange between users. To set up a connection, the browser discovers its network addresses, and a site can read them.

The catch is that WebRTC sometimes bypasses the proxy set in the browser or system. A site then sees the proxy IP in normal requests but learns your real address through WebRTC. Anti-fraud systems on social and ad platforms notice the mismatch.

How to read the result

If WebRTC shows the same external IP as the page, or only local addresses (192.168..., 10...), you are fine. If there is a public IP that differs from the page address, that is a leak.

Turn the proxy on and run the test again: the page address should change to the proxy address, and your real IP should not appear through WebRTC.

How to fix a leak

1. In an antidetect browser, set WebRTC to spoof or replace it with the proxy IP: Dolphin Anty, AdsPower, Octo Browser and others support this. 2. In a regular browser, install an extension that limits WebRTC, or disable it in settings if the browser allows. 3. If the proxy runs through Proxifier or a client app, make sure all browser traffic goes through it, including UDP. 4. Run the test again after the changes.

FAQ

Yes. The check runs in your browser; we store and send nothing.

That is a local address in your home network. It does not reveal your external IP and is usually not a leak.

Not necessarily. Disabling it is visible to sites too. In an antidetect browser, a mode where WebRTC shows the proxy IP is better.

Not always. Test with the VPN on: the external IP via WebRTC should match the VPN address.

Need a proxy without surprises?

Pick residential, mobile or SOCKS5 proxies on Proxyvizr and check them with this test.