WebRTC Leak Test

The test shows which addresses your browser reports through WebRTC, and compares the public one with the address that websites see. If they do not match, your real IP leaks past the proxy or tunnel. The browser learns your public address from our STUN server; no third-party service receives it.

What your result means

A leak means a public address different from the one websites see. An address like 192.168.1.5 comes from your home network and does not reveal your real IP. Names ending in «local» are the browser's protection: this is how it hides the local address.

Our site works over IPv4, so if your browser reports an IPv6 address, it is shown separately. There is nothing to compare it against, so check it yourself: if it belongs to your ISP, sites with IPv6 support will see it.

How to close the leak

In Firefox, open about:config and set media.peerconnection.enabled to false. WebRTC turns off completely, and browser calls stop working.

Chrome, Edge, and Yandex Browser have no such switch. The WebRTC Network Limiter extension by Google from the Chrome Web Store works in all three browsers. Many proxy and VPN programs have their own WebRTC leak protection — check that it is enabled, and press «Check again».