Does WebRTC reveal your office IP?
WebRTC runs the video calls and live chat in your browser, and it can pass your office or home IP to any page you open while the proxy carries everything else. This check gathers the addresses WebRTC is willing to share and sets them beside the IP that reached our server.
How WebRTC can reveal your connection
WebRTC (Web Real-Time Communication) lets browsers run calls and direct connections without plug-ins; Google Meet, Discord voice and browser file-transfer apps rely on it. For a direct connection between two callers, the browser collects the device’s network addresses, and that list can include addresses the proxy is meant to hide.
Reading that list takes a page only a short script and no permission prompt. Ad trackers, fingerprinting services and bot-management systems do exactly that, so a leak can reveal your company network to the sites your team researches, even while the rest of the visit runs through the proxy.
Fixing a leak on team machines
Settings by browser
- Firefox: enter
about:configin the address bar and changemedia.peerconnection.enabledtofalse. Browser-based video calls in that Firefox profile will stop working, so keep a separate profile for meetings. - Chrome / Edge / Brave: extensions such as “WebRTC Network Limiter” or “WebRTC Leak Prevent” restrict what WebRTC shares; on company-managed devices, IT can enforce the same through browser policy.
- Safari: leave “WebRTC mDNS ICE candidates” (Develop → Experimental Features) switched on, because it masks local network addresses. Public addresses are a separate matter, so if this test still shows one that isn’t the proxy’s, use one of the browsers above for proxy work.
Multi-profile browsers
Agencies that keep client accounts in separate profiles often use multi-profile browsers such as Kameleo, Incogniton, GoLogin, Multilogin or Dolphin Anty. They handle WebRTC per profile, so it reports the proxy’s IP rather than the office connection. Confirm it on this page for every new profile.
Automated monitoring browsers
If your team’s monitoring runs on Puppeteer, Playwright or Selenium, the developer can launch Chrome with flags that restrict the addresses WebRTC may use, then run this test inside the automated browser to confirm the result:
// Puppeteer / Playwright args: ['--disable-features=WebRtcHideLocalIpsWithMdns', '--force-webrtc-ip-handling-policy=default_public_interface_only']
What a leak costs a research team
Teams use proxies so that sites see the proxy’s address and location. A WebRTC leak puts your own address back in the picture, and the mismatch between the two (a visit from a Paris IP whose browser also reports an address in Manchester, say) is easy for a site’s fraud checks to spot. Results from that session may then differ from what a local customer would see.
Make this test part of setting up any browser used for client accounts, ad checks or market research, and repeat it after browser updates.
Does the test send anything to us?
No. Everything happens inside your browser, and WebRTC’s findings never leave it. The “Server sees” box only repeats the IP that our server already received with your page request. To learn its public address, the browser does contact a public STUN server, just as it would at the start of a video call.
