WebRTC leak test
See which IP addresses your browser reveals through WebRTC and compare them with the address websites see.
Your public IP
216.73.216.174
Checking WebRTC addresses
Your result and detected addresses will appear here after the check.
Check details
This checks the current browser and connection without requesting media permissions. Results may differ on another network or on a site with camera or microphone access.
Use a different public IP with Kryon VPN
Connect through a VPN server, then run the test again to check the addresses your browser exposes.
What is a WebRTC leak?
WebRTC powers browser calls, video meetings and peer-to-peer data transfer. A leak occurs when it reveals a public IP you expected your VPN or proxy to hide.
To find a connection path, ICE gathers addresses from network interfaces and STUN servers. A website can read those addresses without starting a call or requesting camera access. TURN can relay calls when a direct path is unavailable.
Two paths worth comparing
Website request → public IP
WebRTC → ICE and STUN addresses
How to test for a WebRTC leak with a VPN
Connect your VPN and open this page. The test starts automatically.
Connect your VPN
Wait for the VPN to connect. Make sure this browser is included in the tunnel. In the Kryon extension, leave WebRTC Protection enabled.
Read the result
Compare the public IP used to reach this site with the WebRTC addresses. A different public IP may indicate a VPN or proxy bypass.
Retest after changes
Repeat the test after changing a VPN server, browser permissions or network. A successful check covers the observed configuration; it does not measure DNS leaks or all traffic from other apps.
What the detected addresses mean
Public IPs, private addresses and mDNS names have different privacy implications.
Public IPv4 or IPv6
A public address can identify a network exit and its approximate location. A VPN exit appearing here is normal. A second address can come from another route; comparing before and after VPN gives stronger evidence.
Local network addresses
Addresses such as 192.168.1.10 and IPv6 link-local or unique-local addresses are not public internet exits. They may reveal details of your local network, but do not by themselves expose your original public IP.
Names ending in .local
Browsers may replace local addresses with random mDNS names. These names hide the raw local IP from page scripts. This masking does not guarantee that STUN cannot return a public address.
Check your browser with Kryon VPN connected
Route your connection through a VPN server. In the Kryon browser extension, keep WebRTC Protection enabled and verify the result here.
How to prevent WebRTC IP leaks
Check VPN routing and browser settings first. Disabling WebRTC entirely can break browser calls, screen sharing and other real-time features.
Check the VPN route
Include the browser in the VPN tunnel and check split-tunneling exclusions. Both UDP and IPv6 need to go through the VPN or be blocked when they cannot be tunneled.
Chrome and Edge extensions
An ordinary HTTP proxy does not cover every WebRTC connection. A browser extension can restrict non-proxied UDP. Keep WebRTC Protection enabled in the Kryon extension and rerun this test.
Firefox and Safari
Keep the browser updated and verify the VPN route. Firefox offers advanced WebRTC controls, but changing them can break calls. Safari behavior depends on settings and site permissions; there is no universal result for every site.
Retest after changes
Repeat the test after changing a VPN server, browser permissions or network. A successful check covers the observed configuration; it does not measure DNS leaks or all traffic from other apps.
Check the public IP of your connection
See the address, network and approximate location that websites observe.
WebRTC leak test FAQ
Understand your results and the limits of a browser-based check.
No. The test works with other VPNs, proxies or a direct connection. It compares the public IP seen by this site with WebRTC candidates. It does not automatically determine whether you are connected to Kryon.