WebRTC leak test:
is your real IP showing?
WebRTC can hand out your real IP address even when a proxy or VPN is on. This test asks your browser exactly what it exposes and compares it with the IP websites see.
- Websites see you as (IPv4)
- -
- Websites see you as (IPv6)
- -
- Public IPs exposed by WebRTC
- -
- Local IPs exposed by WebRTC
- -
- WebRTC status
- -
- UDP and STUN
- -
All ICE candidates the browser produced
How this works: your browser asks Google's public STUN servers (stun.l.google.com) for the addresses it can be reached on, which is exactly what a website's WebRTC script does. Google sees your IP like any server you connect to. To compare, our server and api.ipify.org / Cloudflare tell us which address websites see over normal web requests.
What is a WebRTC leak?
WebRTC is the browser feature behind video calls and peer-to-peer apps. To connect two devices it finds every address the browser can be reached on and shares them with the page. A normal web proxy only carries web requests (TCP), but WebRTC talks over UDP and can go straight out of your network, so a script can read your real address even though every page you open shows the proxy's IP.
Why it matters for you
If you run several accounts or scrape behind a proxy, a site that sees the proxy IP in the request and your home IP in WebRTC knows the proxy is a cover. That mismatch is one of the first things anti-fraud checks compare.
What is mDNS (.local)?
To stop leaking your LAN address (like 192.168.1.20), Chrome, Edge, Safari and Firefox swap it for a random name ending in .local. Seeing a .local name here is good: the local IP is hidden. Public addresses are not hidden this way.
How to fix a leak
In AdsPower, GoLogin, Multilogin or Dolphin{anty} set the profile's WebRTC mode to replace the address with the proxy IP (or disable it). In plain Chrome use a WebRTC-blocking extension; in Firefox set media.peerconnection.enabled to false in about:config. Then run this test again.
Questions
Does a proxy or VPN stop WebRTC leaks?
Not by itself. An HTTP or SOCKS5 proxy set in the browser carries web traffic but usually not the UDP packets WebRTC sends. A full-tunnel VPN covers more, yet browsers can still expose the real local or IPv6 address. The only way to know is to test with your proxy on.
Is a visible local IP like 192.168.x.x a problem?
It cannot be used to reach you from the internet, so it is a small risk. It does add detail to your device fingerprint, and it is another sign that WebRTC is not masked. Current browsers hide it behind a .local name unless you have allowed camera or microphone access.
Should I just disable WebRTC?
Disabling it stops the leak but breaks video calls, and a browser with no WebRTC at all can look unusual to anti-fraud systems. For multi-account work it is usually better to keep WebRTC on and have it report the proxy IP.
Route WebRTC through a real mobile IP
XProxy mobile proxies run on real 4G/5G carrier connections and support SOCKS5 UDP, so WebRTC traffic can go through the proxy and report the same IP as the rest of your browser.
