WebRTC Leak Test
What a WebRTC leak is, why it silently defeats a proxy in the browser, how to read the result, and how to fix the cause.
Last updated
The WebRTC Leak Test is at /tools/webrtc-leak-test. It checks whether your browser is exposing your real address to the pages you visit, regardless of any proxy in use.
What a leak is
WebRTC is the browser feature behind video calls and peer-to-peer connections. To find a route to the other party, it enumerates your network interfaces and candidates for reaching the internet.
That enumeration can include your real local address and, in some configurations, your real public address. When it does, a site can learn where you actually are even though your HTTP requests went through a proxy. The proxy is working; the browser is telling the truth in a second channel.
Why it matters
A leak makes several kinds of work pointless.
| Task | What the leak breaks |
|---|---|
| Geo-targeted checks | Results reflect your real location, not the target market |
| Account separation | Profiles that should be isolated share one real address |
| Location-sensitive prices | You see your own market's prices |
The failure is silent. Nothing errors; the result is simply wrong.
Running the test
- Open
/tools/webrtc-leak-test. - Let the page enumerate ICE candidates.
- Read the result.
The test runs entirely in your browser. It enumerates candidates locally and classifies them; nothing is sent to a server.
Reading the result
| Result | Meaning |
|---|---|
| No public address exposed | Candidates are limited to local or private addresses; no leak |
| Public address exposed | Your real public address is visible; there is a leak |
The local and private addresses (the 192.168.x.x and 10.x.x.x style entries) are expected and are not the problem. What matters is whether a public address that belongs to you, rather than to your proxy, appears.
Fixing a leak
The setting lives in the browser, not in the proxy.
- Disable WebRTC in the browser or profile where it is not needed. Antidetect browsers and profile managers generally expose this as a per-profile setting.
- Use a browser profile built for it. A profile manager that controls WebRTC behaviour per profile is the reliable route when you run many identities.
- Check after every configuration change. A browser update or a new extension can reintroduce a leak.
Where it fits in your checks
Three checks cover the common browser problems, and they answer different questions:
- The Proxy Checker confirms the endpoint works and reports its exit address.
- The IP Lookup confirms where that address sits.
- This test confirms the browser is not disclosing your real address alongside it.
Run all three after setting up a new profile. The third is the one most often skipped and the one that silently invalidates the other two.