Skip to content
IPClear

WebRTC leak test

This test asks your browser for the addresses WebRTC would share during a call and compares them with the IP this site sees. A different public IP means something is bypassing your VPN or proxy.

WebRTC leak test

WebRTC lets websites ask your browser for its network addresses. With a VPN, a leak exposes your real IP.

Running test…

Your public IP address

Your IP & location

IPv4
IPv6
Country
City / Region
Time zone
ISP / organisation
ASN
Reverse DNS

Location is approximate and based on the IP address only; it can be off by many kilometres.

What is a WebRTC leak?

WebRTC is the browser technology behind video calls in Google Meet, Discord and similar apps. To connect two people directly, the browser collects its network addresses, including the public IP it learns from a STUN server, and any website can start this process without asking for permission.

If that STUN request travels outside your VPN tunnel, it reveals your real internet provider address. Good VPN apps block this, but browser-only VPN extensions and proxies often do not.

How to read the results

  • Public IPs exposed: the public addresses STUN servers saw. If they match the IP shown below, there is no leak.
  • Leaked: a public address that differs from the one websites see. With a VPN on, this is usually your real address. This includes an IPv6 address leaking past an IPv4-only VPN.
  • Local network IPs: "Hidden by your browser (mDNS)" is the safe default in current Chrome, Edge, Firefox and Safari. A shown address such as 192.168.1.20 is not your public IP, but it makes your browser easier to fingerprint.
  • "WebRTC isn't available": WebRTC is disabled in this browser, so it cannot leak.

How to fix a WebRTC leak

  1. Use your VPN's desktop or mobile app rather than only a browser extension, and turn on its leak protection and kill switch.
  2. Brave: Settings, Privacy and security, WebRTC IP handling policy, choose "Disable non-proxied UDP".
  3. Chrome and Edge: install Google's "WebRTC Network Limiter" extension, or enable "Prevent WebRTC from leaking local IP addresses" in uBlock Origin's settings.
  4. Firefox: open about:config and set media.peerconnection.enabled to false. This turns WebRTC off completely, so browser-based calls stop working.
  5. Reload this page and press "Run again" to confirm the leak is gone.

Frequently asked questions

›Does a WebRTC leak mean I've been hacked?

No. It is normal browser behaviour. It only matters if you rely on a VPN or proxy to hide your IP, because sites could still see your real address.

›Should I disable WebRTC?

Only if the test shows a leak that your VPN cannot fix. Disabling it breaks video and voice calls that run in the browser.

›The test shows my real IP but I don't use a VPN. Is that a leak?

No. Without a VPN, the address WebRTC exposes is the same one every website already sees. It is only listed as leaked when it differs from your visible IP.

›Does incognito or private mode stop WebRTC leaks?

No. Private windows don't change how WebRTC gathers addresses.

›Is a local IP leak dangerous?

The risk is low. A local address like 192.168.1.20 can't be used to reach you from the internet, but it adds to the information that can fingerprint your browser.

›Which servers does this test contact?

Your browser asks Google's and Cloudflare's public STUN servers which address they see. No audio or video is sent and no permission prompt appears.

Related tests

Run the full IP & leak test · How it works