Check whether WebRTC exposes the IP your proxy should hide
Updated:
A WebRTC leak test checks whether your browser reveals your real IP through WebRTC even while your web traffic goes through a proxy. WebRTC powers voice and video calls in Chrome, Edge, Firefox, Brave and mobile browsers, and it discovers network routes by contacting UDP STUN servers such as stun.l.google.com and stun.cloudflare.com. Those requests can bypass an HTTP(S) proxy entirely. The test runs automatically when this page loads.
Your browser either blocks UDP STUN completely or masks WebRTC candidates.
Why this matters for account work
Anti-fraud scripts on platforms such as TikTok Shop, Facebook Business Manager, Shopee, Amazon and Etsy can quietly create an RTCPeerConnection during login and collect whatever addresses it returns. If one of them is your home IP while the HTTP request came from a proxy, the platform sees both, and the proxy has not separated your accounts at all.
The page shows two cards: on the left, the IP websites see through TCP and HTTP headers; on the right, the public address discovered through UDP STUN. Below them, a table lists every ICE candidate with its scope (local LAN host, public srflx or mDNS .local) and transport.
Three outcomes and what to do
| What you see | What sites learn | Verdict | Action |
|---|---|---|---|
| Public STUN IP differs from HTTP IP | Your proxy IP and your real home IP | Leak: accounts can be linked | Set WebRTC to replace or alter in your antidetect browser, or disable WebRTC |
| Public STUN IP equals HTTP IP | Only the proxy IP (the srflx candidate matches) | Safe, and looks like a normal browser | None; this is what GenLogin, GoLogin, AdsPower and Multilogin aim for |
Only mDNS .local names, or WebRTC disabled | A random .local name or nothing | Safe | Fine for everyday Chrome or Firefox browsing |
Closing the leak, browser by browser
- Antidetect browsers (GenLogin, GoLogin, AdsPower, Dolphin{anty}): choose the WebRTC Alter or Replace mode so
RTCPeerConnectionreports your ProxyV4 proxy IP as the public candidate. Setup details: GenLogin, GoLogin. - Firefox: open
about:config, findmedia.peerconnection.enabledand set it tofalse. More in Firefox proxy setup. - Chrome and Edge: install the official WebRTC Network Limiter extension and turn on
Anonymize local IPs exposed by WebRTCinchrome://flagsoredge://flags. - Afterwards: confirm the main IP with my IP, then come back here and press Re-Test WebRTC.
Step by step
- 1
Open the page in the right profile
Load it inside the same browser profile, with the same proxy, that you use for your accounts.
- 2
Compare the two cards
The WebRTC card should show No Public WebRTC IP Exposed, or the same IP as the HTTP card.
- 3
Scan the ICE candidate table
Local addresses like
192.168.x.xor10.x.x.xshould be hidden behind.localmDNS names. - 4
Re-test after changes
Press Re-Test WebRTC and wait for No WebRTC Public IP Mismatch Detected before you sign in anywhere.
Frequently asked questions
I use SwitchyOmega or FoxyProxy. Why does WebRTC still show my real IP?
Those extensions route HTTP and HTTPS traffic over TCP. Chrome sends WebRTC STUN requests over UDP outside that route unless an extension or antidetect browser restricts WebRTC.
Should I disable WebRTC or use Replace mode?
For platforms that score trust, such as Facebook Ads, TikTok Shop and Amazon, Replace or Alter mode, where STUN returns the proxy IP, looks more natural than removing RTCPeerConnection entirely.
What is a `.local` candidate?
Modern browsers hide private LAN addresses such as 192.168.1.5 behind a temporary random name ending in .local, so sites cannot read your local network layout.
Does a clean result mean my profile is undetectable?
No. It only rules out a WebRTC IP leak. Fingerprint, cookies and timezone still matter; the IP lookup tool helps you match timezone and country to the proxy.
A clean IP for a clean profile
ProxyV4 private IPv4 and static residential ISP proxies, one customer per IP, ready for GenLogin, GoLogin and AdsPower.
See static ISP prices