What a WebRTC leak is
WebRTC is the technology behind calls and video chats inside the browser. To connect two peers directly, the browser asks a STUN server for its external address and lists its local interfaces. Those requests bypass a regular HTTP proxy: the website gets your real IP even when the page itself was loaded through a proxy or VPN. That is how “different” accounts living behind the same home router get linked together.
How to read the result
Ok — WebRTC is blocked or reports the same public address as the server: no leak. Notice — the public address matches, but the browser reveals real local IPs (192.168.x.x, 10.x.x.x), which are used to link profiles on the same network. Modern Chrome and Firefox hide them behind mDNS names like xxxx.local — such entries are marked “hidden”. Exposed — WebRTC shows a different public IP than the server: anti-fraud sees both the proxy and the address behind it.
How to close the leak
The quick way is to disable WebRTC with an extension or a flag, but the block itself is visible too: a normal user has WebRTC working. The better way is to make WebRTC report the proxy address instead of nothing — that is what antidetect browsers do by routing ICE through the profile’s proxy. Compare products in the rating and read setup guides in the blog. For the full picture, run the fingerprint check.