WebRTC leak test: does your proxy hide your IP?
WebRTC can tell a page the address your browser appears to have, even when your web traffic goes through a proxy or VPN. Turn your proxy on, then run the test.
Runs in your browser. It asks our check server for your connection’s address and location (one request) and, to test WebRTC, Google’s public STUN server. Nothing is stored.
How the test works
Your browser opens a WebRTC connection object and asks Google’s public STUN server what address it appears to have. Any addresses it gathers are listed here, next to the address your ordinary web connection comes from. If they differ, the second one is often your real address.
How to read it
- Same address, or none gathered: nothing is leaking through WebRTC.
- A second public address: WebRTC is reaching the network outside your proxy. Set the browser’s WebRTC setting to follow the proxy, or block non-proxied UDP.
- A local address such as 192.168.x.x: modern browsers hide these behind random .local names; an exposed one means that protection is off.
Related: DNS leaks and HTTP and SOCKS5 proxies.
Why does WebRTC expose an IP address?
Does a VPN or proxy prevent it?
Is anything stored?
Run every account in its own browser.
Download free, import your profiles in minutes and pay $9 a month for 100 of them. Every plan is free for 3 days.
- 100 profiles for $9 a month
- Imports AdsPower, Multilogin, Dolphin, GoLogin, Kameleo
- Mac, Windows and Linux
Test with your proxy on, then fix what leaks.
One profile free for as long as you like. Every plan free for 3 days. Cancel any time.