Question 1

What exactly is a WebRTC leak?

Accepted Answer

WebRTC uses ICE candidate gathering to find the best network path, which can list your real public and local addresses. Any page with JavaScript can trigger this, no permission prompt required.

Question 2

How does this test work?

Accepted Answer

We open a loopback RTCPeerConnection and collect its ICE candidates, the exact same signal a real page reads. Everything runs in your browser; no data leaves your machine.

Question 3

What does an mDNS (.local) address mean?

Accepted Answer

Modern browsers hide local IPs behind randomized mDNS hostnames (e.g. abc123.local). That's the privacy-preserving behavior you want to see.

Question 4

My public IP is shown, is that a leak?

Accepted Answer

Only if it's your *real* address while you expect to be proxied. If you're browsing directly, showing your public IP is expected. Compare it against your proxy's exit IP.

Question 5

How do I stop a WebRTC leak?

Accepted Answer

In anti-detect browsers, enable WebRTC protection. In regular browsers, use a WebRTC-controlling extension or browser flag so candidates are proxied or suppressed.

Question 6

Does the test work on mobile?

Accepted Answer

Yes, on browsers that expose WebRTC (all modern ones). Some mobile networks strip candidates; the test reports that too.

WebRTC Leak Test: catch the leak before the block

Three steps, ten seconds

Run the test

Inspect the findings

Fix what leaks

Keep testing your setup

Questions, answered

Start working with cleaner IPs