Donate
Donate

WebRTC Leak Test

Check whether browser WebRTC behavior can expose your real IP while using a VPN

WebRTC leak test for Chrome, Firefox, Edge, and Brave

WebRTC may expose local or network IP information through requests, depending on browser behavior and VPN setup. This can happen even when your main public IP appears changed.

Lily's browser seal

Close the gap WebRTC opens in your browser

WebRTC can hand out your real address from inside the browser even while a VPN is connected. Apply the per-browser fix below, then re-run the test and confirm the leak is gone.

Test for DNS leaksVPNs that block it
Lily sealing a leak in a browser window
Live browser check

Run the WebRTC leak test

This test asks your browser to gather WebRTC network candidates and compares public candidates with the IP address this site normally sees.

Ready to test

Start the browser test to compare WebRTC candidates with your normal visible IP.

Visible IPNot checked yet

Loaded from the normal IP checker during the test.

Public WebRTC IPs0

No public WebRTC IP captured yet.

Local or hidden candidates0

Includes private LAN addresses and mDNS-masked browser candidates.

CandidateTypeProtocolExposure
Run the test to see WebRTC candidates here.

Best use: run once without a VPN, connect the VPN, then run again. If a public WebRTC candidate still shows your normal ISP IP while the visible IP shows the VPN, your browser is leaking through WebRTC.

WebRTC still exposing your real IP?

Browser flags stop the leak in one browser, on one device. A VPN that blocks WebRTC at the application level covers every browser and profile on the machine instead.

Compare VPN WebRTC handlingCompare VPNs

Affiliate link. IP Trackers may earn a commission if you buy through it, at no extra cost to you. It does not change what we recommend - see our editorial policy.

Fast answer: how to fix a WebRTC leak in Chrome

Chrome does not include a normal settings toggle that fully disables WebRTC. The practical fixes are to use your VPN's browser leak protection, install a trusted WebRTC control extension, or use a browser that lets you restrict WebRTC IP handling more directly.

After changing Chrome, retest with the VPN connected. A fixed setup should not reveal your original ISP address through browser-originated WebRTC/STUN behavior.

Check the other VPN leak paths

How to run a WebRTC leak test

  1. Capture baseline IP/ISP details on the homepage checker.
  2. Connect your VPN, then repeat the same checks.
  3. Compare browser-level behavior with Proxy Check and DNS Leak Test.
  4. If browser-originated IP signals still differ, apply WebRTC fixes below and retest.

Related tests

How to disable WebRTC in every major browser

Each browser handles WebRTC differently. Here is how to limit or disable it in the most common browsers. After making changes, always retest to confirm the fix worked.

  • Firefox: Open about:config in the address bar, search for media.peerconnection.enabled, and set it to false. This fully disables WebRTC. Note: video calls and screen sharing in the browser will stop working.
  • Chrome / Edge / Brave:Chrome does not allow fully disabling WebRTC from settings. Install a trusted extension like “WebRTC Network Limiter” or use your VPN’s built-in WebRTC leak protection. Brave has a built-in toggle under Settings > Privacy > WebRTC IP Handling Policy.
  • Safari:Go to Preferences > Advanced > enable “Show Develop menu”, then Develop > Experimental Features > uncheck WebRTC mDNS ICE candidates. Safari is less prone to WebRTC leaks by default.
  • Opera:Similar to Chrome. Use the “WebRTC Leak Prevent” extension and set it to “Disable non-proxied UDP”.
  • VPN apps: Most quality VPNs (NordVPN, ExpressVPN, Mullvad, Surfshark) include built-in WebRTC leak protection. Enable it in your VPN app settings before relying on browser-level fixes alone.

Compare VPNs with WebRTC protection

What WebRTC actually exposes and why it matters

WebRTC uses STUN servers to discover your network-facing IP address for peer-to-peer communication. This process can reveal three types of information:

  • Your public IP address even when connected to a VPN, because the browser may send STUN requests outside the tunnel.
  • Your local/private IP address (like 192.168.x.x or 10.x.x.x), which reveals your network structure.
  • Your ISP identity through the public IP, which can be mapped to an ASN and provider name via ASN lookup.

This is why a WebRTC leak check is a separate step from a DNS or IP check. Your VPN can change your visible IP and DNS resolver while WebRTC still reveals the real address through a different channel.

Validate other leak paths

Protect your IP

What to do next after a WebRTC leak test

Use DNS, proxy, and IP checks to confirm your VPN setup is consistent across leak vectors.

1Next step
Resolver path

Run a DNS leak test

WebRTC and DNS leaks are separate problems. Validate resolver traffic before trusting your VPN setup.

Check DNS leaks
2Next step
IPv6 path

Run an IPv6 leak test

Some VPNs route IPv4 correctly but still expose your normal IPv6 path. Validate that separately.

Check IPv6 leaks
3Next step
Guided flow

Use the VPN verification wizard

Record pass/warn/fail results in one guided workflow and keep the checklist for future retesting.

Open wizard
4Next step
Context

Compare proxy/VPN signals

Proxy checks help interpret whether your IP context looks like a shared gateway, VPN, or hosting network.

Run proxy check
5Next step
Troubleshooting

Fix VPN connected but IP not changing

If your browser still shows the wrong IP, review common causes like split tunneling or app routing issues.

Read fixes

Related Articles

How to Protect Your IP Address from Tracking12 min read • April 26, 2026VPN vs Proxy: Privacy, Speed, and Which to Use14 min read • August 1, 2026VPN Connected but IP Not Changing? How to Fix It8 min read • February 9, 2026What Is a VPN? How It Works and What It Actually Hides20 min read • August 1, 2026

Frequently asked questions

Does this page run a real WebRTC leak test?
Yes. The live test uses your browser WebRTC peer connection API to collect ICE candidates through STUN and compares public candidates with the IP address this site normally sees.
How do I fix a WebRTC leak in Chrome?
Install a WebRTC leak prevention extension such as WebRTC Network Limiter or uBlock Origin, restrict non-proxied UDP, and re-run the test. If the test still shows your real IP, switch the VPN to TCP mode or a different provider with built-in WebRTC protection.
How do I disable WebRTC in Chrome with a VPN?
Chrome does not expose a global toggle to disable WebRTC. Use an extension like WebRTC Control or WebRTC Network Limiter to block STUN candidate gathering, then verify with this leak test. Brave and Firefox have native settings for the same goal.
What is a WebRTC leak?
A WebRTC leak is when browser WebRTC/STUN behavior exposes IP-related information outside your expected VPN route.
Can WebRTC leak even if my VPN is connected?
Yes. Browser-level behavior can still expose network details if WebRTC settings are not constrained.
How do I prevent WebRTC leaks in Chrome?
Use trusted privacy controls/extensions and limit non-proxied WebRTC UDP behavior where supported, then retest.
How do I prevent WebRTC leaks in Firefox?
Review and harden WebRTC configuration in about:config, then validate with repeated checks.
Should I run DNS and WebRTC leak tests together?
Yes. DNS and WebRTC are different leak vectors, so both should be tested for reliable VPN verification.
What is the difference between a WebRTC leak, DNS leak, and IP leak?
An IP leak means the visible HTTP IP is your real IP (the VPN tunnel is broken). A DNS leak means the visible IP is the VPN exit, but DNS queries still hit the ISP resolver. A WebRTC leak means both the IP and DNS go through the VPN, but the browser still reveals your real IP via the WebRTC API. A VPN session can pass two of these tests and fail the third, so run all three independently.
How can a website use a leaked WebRTC IP against me?
A leaked WebRTC IP gives a website three things a VPN would otherwise hide: (1) accurate geolocation pointing to your real city, (2) ISP attribution useful for cross-session fingerprinting even with rotating VPN exits, and (3) local LAN structure (192.168.x.x vs 10.0.x.x) for stable device identification. Anti-fraud, ad-targeting, and content-licensing systems all use this data.