WebRTC IP leak test
Compare the HTTP address with the available WebRTC candidates, see if another public address is visible when using the current connection.
WebRTC IP leak test
FreeLoading the check...
What the test will show
Compare the HTTP address with the available WebRTC candidates, see if another public address is visible when using the current connection.
How to take the test
- Allow a single access to the specified STUN server.
- Run the check and compare the HTTP address to the list of candidates.
- Repeat in another browser with the same connection settings.
How to understand the result
A different address is a reason to study the route, not a proven leak. No candidates guarantee protection. DNS leaks and the behavior of other applications are not measured by this test.
Compare multiple runs under the same conditions. Then change one factor: connection, device, or setting. If the symptom persists, repeat the test on another device and save the conditions - this will help to more accurately describe the problem to support.
How Calcomera measurements work
Do you need a camera or a microphone?
No. You create a data channel without access to a camera or a microphone, and you use STUN to find a public address, which sees the sender's address.
Why is the list empty?
The reason may be privacy settings, unavailable STUN, network limitations, or lack of support for WebRTC. An empty list does not mean there are no leaks.
Is this a DNS leak test?
No. To monitor DNS solvers, you need a separate authoritative DNS service, and you can't really get a list of solvers from JavaScript on a normal page.