top
logo
custom iconResourcesHOT
custom iconFeature overview
language-switch
loadingloading...
loadingloading...
The WebRTC Leak Test is an essential privacy tool for VPN users. WebRTC technology communicates with STUN servers. This can potentially expose your actual local or public IP address, even when using a VPN or proxy.Use this tool to easily check whether your IP may be exposed, so you can see if your online anonymity is at risk.Granting media device permissions allows WebRTC to expose your private IP address.
mediaMedia Devices API
successAvailable
microphoneMicrophone Permission
1Permission: Not granted
Allow Access
CameraCamera Permission
1Permission: Not granted
Allow Access
STUN (stun.miwifi.com)
Private IP-
Public IP:Not detected
STUN (stun.qq.com)
Private IP-
Public IP:Not detected
STUN (hw-v2-web-player-tracker.biliapi.net)
Private IP-
Public IP:Not detected
STUN (stun.smartgslb.com:19302)
Private IP-
Public IP:Not detected
STUN (stun.l.google.com:19302)
Private IP-
Public IP:Not detected
STUN (stun2.l.google.com:19302)
Private IP-
Public IP:Not detected
STUN (stun3.l.google.com:19302)
Private IP-
Public IP:Not detected
STUN (stun4.l.google.com:19302)
Private IP-
Public IP:Not detected
STUN (stun.nextcloud.com:443)
Private IP-
Public IP:Not detected
STUN (stun.cloudflare.com)
Private IP-
Public IP:Not detected
STUN (stunserver.stunprotocol.org:3478)
Private IP-
Public IP:Not detected
STUN (freestun.net:5350)
Private IP-
Public IP:Not detected
STUN (global.stun.twilio.com)
Private IP-
Public IP:Not detected
STUN (jp1.stun.twilio.com)
Private IP-
Public IP:Not detected
STUN (sg1.stun.twilio.com)
Private IP-
Public IP:Not detected
STUN (us1.stun.twilio.com)
Private IP-
Public IP:Not detected
STUN (stun.syncthing.net)
Private IP-
Public IP:Not detected
How to disable WebRTC
Chrome / Edge
Chrome does not provide a native option to completely disable WebRTC, but IP exposure can be mitigated using browser policies or extensions.Install extensions like:WebRTC ControluBlock Origin (manual setup required)After installation, enable the 'Disable WebRTC' optionConfirm 'Blocked' status in the plugin icon
Note: Browser extensions offer only partial control over WebRTC and are not completely reliable. It's recommended to use them in conjunction with a VPN and DNS leak tests.
Firefox
Firefox allows disabling WebRTC media and peer connection features, which significantly reduces IP exposure risks.Steps to Disable (Firefox):Enter about:config in the address bar.Search for: media.peerconnection.enabledSet the value from true to false.After this, WebRTC functionality will be completely disabled.
Safari(macOS / iOS)
Safari limits WebRTC configuration options. IP exposure is primarily controlled by system-level privacy settings and network policies.Control over WebRTC on iOS is limited. It is strongly advised to use a VPN and test for leaks.
desc16
You can test using this website:https://www.*******.com/zh/WebRTCIf the page does NOT display your actual local IP (e.g., your private IP address or ISP-assigned IP), it indicates that WebRTC has been effectively blocked.
What exactly is a WebRTC leak, and what does it expose?
To make peer-to-peer audio and video work, WebRTC collects network candidate addresses through STUN servers — and that process can slip past your current network path and hand your real public IP, or your local network IP, to the web page. What's exposed is the IP itself and an approximate location. Your passwords and browsing history aren't leaked this way, but your anonymity is gone.
My results show a 192.168.x.x or 10.x.x.x address — does that count as a leak?
Generally, no. Those are private LAN addresses that can't be reached from the public internet, so they tell an observer very little. The thing to watch for is a public IP that isn't your current exit — that's a real leak. Also, Chrome has masked local IPs with mDNS by default since version 75, so seeing a hostname ending in .local is normal too.
How do I stop WebRTC leaks? Is it the same in every browser?
It varies. In Firefox, set media.peerconnection.enabled to false in about:config and it's off outright. Chrome and Edge have no built-in toggle — you'll need an extension that works through webRTCIPHandlingPolicy to restrict it. Safari's implementation is relatively restrained. Bear in mind that disabling it completely breaks web-based meetings and voice calls, so decide based on what you actually need.