WebRTC Leak Test
Checks whether WebRTC shows sites a different IP than your proxy or VPN, and whether your browser time zone matches your IP location.
Loading tool…
How it works
Open the page
The test runs on its own: your browser asks a STUN server for its address, and this site returns the IP it sees.
Read each row
Each row shows a verdict, the raw value and why. Using a proxy or VPN? Tick the box so a different IP counts as a leak.
Fix and run again
Apply a fix below, restart the browser and press Run again. Copy JSON gives agents and CI the same result.
How do I stop WebRTC leaks in Chrome?
Set the WebRtcIPHandling policy, or the profile preference webrtc.ip_handling_policy, to disable_non_proxied_udp. WebRTC then uses TCP, and UDP only through a proxy that supports it. The --force-webrtc-ip-handling-policy flag only works in chrome-headless-shell; Chrome ignores it.
How do I stop WebRTC leaks in Firefox?
In about:config, set media.peerconnection.ice.proxy_only_if_behind_proxy to true to keep WebRTC on your proxy, or media.peerconnection.enabled to false to turn WebRTC off.
Is a .local address a leak?
No. Browsers can hide local IPs behind random names ending in .local (mDNS). A raw address such as 192.168.1.20 means that protection is off and any page can read it. It is not your public IP.
Automating behind a proxy?
Browser Use cloud browsers are Chromium with residential proxies and CAPTCHA solving, built for AI agents and scrapers.