Skip to content
Kordu Tools
Network & IP Runs in browser Updated 30 Mar 2026

WebRTC Leak Checker

Test whether WebRTC exposes your real IP address behind a VPN — detects local and public IP leaks.

Ready to check

WebRTC leak check will begin automatically.

STUN Serverstun:stun.l.google.com:19302
ICE Candidates
Gather Time

Public IPs (0)

Local IPs (0)

Loading rating…

How to use WebRTC Leak Checker

  1. Open the tool

    The WebRTC leak check runs automatically when the page loads. No configuration or button press is needed.

  2. Review discovered IPs

    Examine the local and public IP addresses that WebRTC exposed through ICE candidate gathering.

  3. Check for leaks

    If you are using a VPN, compare the displayed public IP to your VPN's expected server IP. A different IP means WebRTC is leaking your real address.

  4. Re-check after changes

    Click Re-check to run the test again after adjusting VPN settings, switching servers, or installing a WebRTC blocking extension.

WebRTC Leak Checker FAQ

What is a WebRTC leak?

WebRTC uses STUN servers to discover your IP addresses for peer-to-peer connections like video calls. These requests can bypass VPN tunnels, revealing your real public IP to websites even when the VPN is active.

Does this tool send my IP anywhere?

The only external request is a standard STUN binding request to a public STUN server for IP discovery. No personal data is stored or transmitted. All IP parsing and display logic runs locally in your browser.

How do I fix a WebRTC leak?

In Firefox: set media.peerconnection.enabled to false in about:config. In Chrome: install a WebRTC Control or WebRTC Leak Prevent extension. Some VPN apps include native WebRTC leak protection — check your VPN settings.

Why do I see a local/private IP address?

Local IPs like 192.168.x.x or 10.x.x.x are your device's addresses on the local network. Exposing these is a minor privacy concern. The more serious issue is public IP exposure.

My VPN is connected but I see my real IP. What should I do?

This confirms a WebRTC leak. Disable WebRTC in your browser or use an extension to block it. Switch to a VPN with native WebRTC protection enabled, or use Firefox with WebRTC disabled.

Does every VPN protect against WebRTC leaks?

No. Many VPNs do not block WebRTC by default. VPNs like Mullvad and ProtonVPN include WebRTC leak protection. Others require manual browser configuration.

What is an ICE candidate?

ICE (Interactive Connectivity Establishment) candidates are IP address and port combinations gathered by WebRTC for establishing peer-to-peer connections. They may include local, VPN, and public IPs.

Does this work if I have no VPN?

Yes. Without a VPN, it shows your real public IP — confirming what your browser leaks to any site using WebRTC. This is normal and expected without a VPN.

Background

Check whether WebRTC is leaking your real IP address behind a VPN. WebRTC uses STUN requests to discover local and public IPs for peer-to-peer connections — and these requests can bypass VPN tunnels, exposing your real location to websites even when your VPN is active.

This tool creates an RTCPeerConnection in your browser, gathers ICE candidates, and reports every IP address discovered. If you see an IP that does not match your VPN's expected address, you have a leak. Results appear automatically — no button press required. Hit Re-check after changing VPN settings.

Who is this for: VPN users verifying their privacy, privacy researchers auditing browser behaviour, security testers checking client configurations, and anyone who wants to confirm their VPN is actually hiding their real IP.

Learn more