WebRTC Leak Test — Check Your Browser's IP Exposure
Compare the public IPs found through WebRTC with your current connection
Last updated: October 18, 2026
Not measured
What is a WebRTC leak?
WebRTC supports browser calls and direct data connections. To find a usable route, a browser gathers connection candidates that can contain IP addresses. A WebRTC IP leak can occur when that process reveals an address you intended to hide behind a VPN or proxy. WebRTC traffic follows network routing; it does not inherently operate outside every VPN tunnel.
This test creates a data channel and gathers candidates using Google and Cloudflare STUN services, which necessarily see the address contacting them. It does not request your camera or microphone or establish a call with another visitor. It compares discovered public addresses with the current IP lookup, while listing private addresses separately. A mismatch is a reason to investigate, not proof that a particular person or location has been identified.
How to prevent WebRTC leaks
Firefox
Set media.peerconnection.enabled to false in about:config
Chrome / Edge
Check a maintained extension's documented WebRTC IP-handling controls
VPN Extension
Verify which traffic and WebRTC settings your specific extension covers
How to Read Your WebRTC Results
A public address can identify an internet-facing connection. A private address such as 192.168.1.10 belongs to a local network and is reused in many homes; it does not identify a household by itself. Browsers may substitute an mDNS hostname for a local address. This test recognizes those names and does not report them as exposed IP addresses. Relay candidates identify a relay server and are not counted as your public IP.
The comparison needs compatible addresses. An IPv4 baseline cannot verify an IPv6 candidate, or the other way around. Such candidates remain inconclusive even when another address matches. IPv6 addresses in the same /64 prefix are treated as consistent because temporary addresses can rotate within that prefix. That is an address-comparison rule, not independent evidence that the VPN encrypted a packet.
An unexpected address may indicate a different route, a proxy that covers web requests but not other traffic, a split-tunnel exception or a changing connection. Note the address and compare it with your VPN provider's documented exit. Do not assume a city label is exact or that every difference means a tunnel failure. If the address belongs to your direct connection, check VPN routing and IPv6 handling.
No mismatch found means this run found no disagreement in the addresses it could compare. It does not certify every application, future call or reconnect. An inconclusive run supplies insufficient evidence and is not counted as a matching observation in the combined privacy test. Repeat after a VPN server change, network switch or browser update; keep the connection stable while the test runs so the baseline and candidates describe the same session.
Check Other Browser and Network Signals
Each tool answers a different question. Use the result details and stated limits to decide what to check next; the suite cannot reveal everything another website knows about you.
IP Lookup — Check both IPv4 and IPv6 addresses, then select one to inspect its network and approximate location.
IP Consistency Check — Run the extended IP-consistency check with per-endpoint detail and the method's limits explained.
Browser Fingerprint — Inspect browser attributes and an illustrative score; it does not measure your uniqueness among all users.
Speed Test — Measure transfer speed and latency on the current test route.
Browser Settings and Their Tradeoffs
Controls differ by browser, platform and managed-device policy. Use current vendor instructions and review an extension's publisher, permissions and update history before installing it. An extension can change routing policy where the browser allows it; it cannot promise every call will keep working or repair every VPN configuration. Test both privacy behavior and the communication services you need.
Chrome and Edge extensions can expose WebRTC IP-handling controls. Check the specific extension's current documentation rather than assuming every VPN or ad blocker includes them. uBlock Origin removed its old local-IP option from desktop browsers in version 1.38; it was not a general guarantee against public-IP exposure. Managed browsers may apply policies you cannot change. Restrictive policies can prevent some calls from connecting.
On desktop Firefox, open about:config, find media.peerconnection.enabled and set it to false to disable peer connections. Set it back to true to restore them. This can break browser calls and other WebRTC features. Availability differs on mobile versions. If you need those features, keep them enabled and check the VPN route or a documented IP-handling control instead.
Brave provides a WebRTC IP Handling Policy setting. Its Disable Non-Proxied UDP option restricts UDP paths unless the proxy supports them; it is a routing policy, not a universal anonymity switch. It may affect connectivity or call quality. Note the previous value, change the policy, and test a call as well as the addresses shown here.
Keep Safari's normal privacy restrictions enabled and review camera and microphone permissions for each site. A developer option named Disable ICE Candidate Restrictions relaxes restrictions; it is not a way to disable WebRTC. Camera permission and address discovery are different controls. Safari behavior depends on version and permissions, so check the actual result with your VPN instead of assuming its defaults hide every public address.
Choose a Fix That Fits Your Calls
Start with your VPN's routing and IPv6 settings. A system VPN can carry WebRTC traffic without disabling the browser feature, while a browser proxy may have narrower coverage. If you do not use WebRTC, disabling it is another option. Record the setting you change, rerun the test and check a non-sensitive call. Restore the setting if needed and fix the route instead; a broken test or broken call is not proof of complete privacy.
Frequently Asked Questions
What is a WebRTC leak?
Can every website check for WebRTC leaks?
How do I disable WebRTC in my browser?
Will disabling WebRTC break anything?
Does my VPN protect against WebRTC leaks?
Full results are displayed in your browser. If you allow optional analytics before starting a run, we may record a coarse outcome and pseudonymous request metadata while your permission remains active. Operational request and error logs apply independently. The privacy policy explains retention, external services and your choices.
Privacy Policy