WebRTC Leak Test (Compare HTTP Proxy IP vs. UDP STUN Candidates)

Updated: 2026-11-05

WebRTC (Web Real-Time Communication) is built into Chrome, Edge, Firefox, Brave, and mobile browsers for voice and video calls. Because WebRTC uses UDP STUN servers (stun.l.google.com, stun.cloudflare.com) to discover network paths, it frequently bypasses standard HTTP(S) proxy configurations and reveals your true home ISP IP or local LAN address to websites. This page automatically tests your browser on load.

Pair Leak-Free Browser Profiles with Clean Static IPs

Buy Anti-Detect Proxies Free Proxy Checker

HTTP(S) Proxy / Server-Seen IP

216.73.216.252

Seen by websites via TCP / HTTP headers

WebRTC STUN Public IP(s)

No Public WebRTC IP Exposed

Discovered via browser UDP STUN servers

✅ No WebRTC Public IP Mismatch Detected

Your browser either blocks UDP STUN completely or masks WebRTC candidates.

How to Interpret Your WebRTC Leak Test Results

Anti-fraud scripts on TikTok Shop, Facebook Business Manager, Shopee, Amazon, and Etsy run a silent RTCPeerConnection probe on login. Compare the three possible candidate states below:

Candidate Type	What Website Scripts See	Risk Level	Recommended Action
Public STUN IP ≠ HTTP IP	Both your Proxy IP and your Real Home IP	CRITICAL (100% Account Link)	Enable WebRTC Spoofing/Replace in Anti-Detect Browser or disable WebRTC
Public STUN IP = HTTP IP	Only your Proxy IP (`srflx` matches HTTP)	SAFE (Natural Browser Profile)	Ideal state produced by Genlogin, GoLogin, AdsPower, and Multilogin
mDNS `.local` / Disabled	Obfuscated UUID `.local` or no candidate	SAFE (Protected)	Good for standard Chrome/Firefox browsing with extensions

How to Fix WebRTC Leaks Across Browsers

Anti-Detect Browsers (Genlogin, GoLogin, AdsPower, Dolphin{anty}): Set WebRTC mode to 'Alter / Replace' so RTCPeerConnection returns your VinaProxy proxy IP as the public STUN candidate.
Mozilla Firefox: Open about:config, search for media.peerconnection.enabled, and toggle it to false.
Google Chrome & Microsoft Edge: Install the official WebRTC Network Limiter extension and enable Anonymize local IPs exposed by WebRTC in chrome://flags / edge://flags.

Step by step

1
Connect through your proxy or anti-detect profile
Open this page inside the exact browser profile you use for managing accounts.
2
Compare the HTTP IP card and WebRTC STUN card
Verify that the right card either shows 'No Public WebRTC IP Exposed' or matches your HTTP Proxy IP on the left.
3
Check the ICE Candidate table for LAN leaks
Ensure local 192.168.x.x or 10.x.x.x addresses are masked by .local mDNS hostnames.
4
Click 'Re-Test WebRTC' after adjusting settings
Confirm the green 'No WebRTC Public IP Mismatch Detected' banner appears before logging into your target platform.

Frequently asked questions

Why does WebRTC leak my real IP when I use a Chrome proxy extension like SwitchyOmega or FoxyProxy?

HTTP(S) proxy extensions only route TCP HTTP/HTTPS traffic. By default, Chrome sends WebRTC STUN binding requests over raw UDP outside the proxy tunnel unless WebRTC UDP routing is restricted by an extension or anti-detect browser.

Is it better to completely disable WebRTC or set it to 'Replace / Alter' in anti-detect browsers?

For high-trust platforms like Facebook Ads, TikTok Shop, and Amazon, setting WebRTC to 'Replace / Alter' (where STUN returns your proxy IP) looks more natural than completely disabling the RTCPeerConnection API.

What is a `.local` mDNS candidate in the table?

Modern browsers replace private LAN IPs (like 192.168.1.5) with an ephemeral UUID ending in .local so websites cannot fingerprint your local router subnet.