WebRTC Leak Test

Check if your browser is leaking your real IP address via WebRTC,
even when using a VPN.

Checking for WebRTC leaks...

🔍

The test failed

Try running the test again.

Type	IP	Country	ISP / Org

What is a WebRTC Leak?

WebRTC (Web Real-Time Communication) is a technology that enables direct browser-to-browser communication, for video calls and P2P transfers. To function, the browser exposes your local and public IP address - regardless of whether you're using a VPN. This is known as a WebRTC leak - a form of IP leak.

How K1VPN protects you from WebRTC Leaks

K1VPN provides protection from WebRTC Leaks without requiring you to take any action in your browser or operating system. Whichever supported application you use - the VPN Client, the Open Source apps for WireGuard®, OpenVPN® and VLESS, or your operating system's native apps (usually IKEv2) - your traffic is protected.

How the protection works at the network (routing) level

When WebRTC tries to discover your IP addresses, it "asks" the operating system for every available network interface.

Without K1VPN: WebRTC sees your real public IP (assigned by your internet provider) and, possibly, your local IP (e.g. 192.168.2.100).
With K1VPN: Every supported app creates a virtual network interface. The VPN forces all of your device's traffic through its tunnel, so WebRTC will see and reveal the VPN server's IP instead of your real IP - which is exactly the intended outcome.

This applies as long as you use the default settings of the apps and their generated configuration files.

Important note

If you want to use VLESS and connect to our Stealth Servers, check whether "Enable Tun" is turned on in the v2rayN and v2rayNG app. Without it you will have a WebRTC leak, and depending on the app version it may not be enabled by default. See the detailed VLESS installation guide for details. For every other client, there's nothing you need to do.

Extra steps to eliminate any chance of a leak

Since WebRTC runs inside the browser itself, disabling it at the source is the most bulletproof method:

Brave: Go to Settings → Privacy and Security → WebRTC IP handling policy and select Disable non-proxied UDP.
Firefox: Type about:config, search for media.peerconnection.enabled and set it to false.
Chrome / Edge / Opera: These browsers have no built-in toggle for this. You'll need to install an extension such as uBlock Origin (enable "Prevent WebRTC from leaking local IP addresses" in its settings) or the dedicated "WebRTC Leak Prevent" add-on.
Safari: Go to Settings → Advanced → Developers (or enable "Show Develop menu in menu bar"). Go to WebRTC and uncheck (disable): "Enable Legacy WebRTC API", "Enable mDNS ICE candidates" (if present). Note: some versions have a "Disable ICE Candidate Restrictions" option - if you see it, enable it (it limits local IP leakage).

In any case, you can revisit this page and run a check whenever you're in doubt about your settings.

⚠️ Attention

Various sites let you run a WebRTC leak check that may show a "possible" leak even while K1VPN is set up correctly. What you should check is whether they display the exit IP of our servers, or the real IP assigned to you by your ISP. If you see the IP of one of our servers, you have no leak at all. If you see your ISP's IP while connected to K1VPN and you've followed everything above, contact customer support and we'll sort it out.

A WebRTC leak is different from a DNS leak or an IP leak. Also try our DNS Leak Test, check which IP you're showing with our IP checker, or see all of K1VPN's security features.