WebRTC Leak Test
Find whether WebRTC reveals a local or public address outside the expected browser path.
Run this tool
Input or start condition: Review the collection scope and press the start control. No active collection starts before that action.
Accepted input or signal: Current browser capability, Explicit WebRTC session start.
Possible output: ICE candidates gathered after you explicitly start the test, including local, public, IPv6, and mDNS values.; Candidate types and whether any public candidate differs from the current HTTP exit IP.
Key limitation: Browser policy, extensions, or network filtering can prevent candidate gathering without indicating a leak.
What this checks
- ICE candidates gathered after you explicitly start the test, including local, public, IPv6, and mDNS values.
- Candidate types and whether any public candidate differs from the current HTTP exit IP.
How to interpret results
- No leak found means no unexpected address appeared in the candidates gathered during this run.
- A public address outside the expected HTTP path needs review; mDNS alone usually means local-address masking is working.
Common issues
- Browser policy, extensions, or network filtering can prevent candidate gathering without indicating a leak.
- A timeout or empty candidate set is not proof that WebRTC can never expose an address.
Privacy note
The active WebRTC check starts only after a click. Candidates are parsed locally, while configured STUN providers can observe the connection used to gather them.
Key Tools and References
Frequently Asked Questions
What is a WebRTC leak?
A WebRTC leak happens when your browser exposes network candidates that reveal local addresses, public addresses, or other interface details that are different from the IP a website sees over HTTP.
Does a WebRTC leak reveal my exact home address?
No. A WebRTC leak does not reveal your street address, but it can expose a private LAN address, a public IP address outside your VPN, or a separate IPv6 address that gives websites more network information than you expect.
Is an mDNS candidate a real IP leak?
Usually not. An mDNS candidate replaces a raw local IP with a temporary hostname ending in .local. That is safer than exposing the real LAN address, but it still shows that WebRTC host discovery is active.
Why can WebRTC show a different IP than the page sees over HTTP?
WebRTC gathers candidates from multiple network paths. If your browser, VPN, proxy, or IPv6 route behaves differently for peer connections than for normal web traffic, WebRTC can surface an address that does not match the HTTP exit IP.
Do I need camera or microphone permission for this test?
No. This test only creates a peer connection and gathers ICE candidates. It does not request camera or microphone access.