WebRTC Leak Test
Test if WebRTC exposes your real public or local IP address even when you use a VPN or proxy. Free, runs in your browser.
Free online tool · Guide updated
| IP found via WebRTC | Type |
|---|---|
| Gathering candidates… | |
IP seen by this website: 216.73.216.69
How to read the results
- Public IP equal to the site IP: normal; websites already see this address.
- A different public IP while on VPN: this is a leak, and your real ISP address is exposed.
- .local addresses: your browser hides your local IP with mDNS (good).
How to stop WebRTC leaks
- Use a VPN app with built-in WebRTC and DNS leak protection, or run the VPN on your router.
- Firefox: open
about:configand setmedia.peerconnection.enabledto false. - Chrome/Edge: use uBlock Origin → Settings → "Prevent WebRTC from leaking local IP addresses".
Next, check your connection with the VPN, Proxy & Tor Checker.
WebRTC Leak Test: complete guide
What a WebRTC leak test checks
A WebRTC leak test checks whether your browser exposes your real public IP address or local IP address through WebRTC, even when you're connected to a VPN or proxy. On this page, the tool runs in your browser, so it can spot network details that web pages and scripts may be able to read while you browse.
WebRTC, which stands for Web Real-Time Communication, is built into modern browsers for audio, video, and peer-to-peer data connections. Those same browser features can reveal network information through ICE candidates, which is why a VPN alone does not always stop IP leaks.
Public IP versus local IP
Your public IP address is the address your internet service provider, or ISP, presents to the outside world. Your local IP address is the private address your router gives your device on the home network, such as 192.168.1.23 or 10.0.0.45.
A leak test can show both. That matters because a VPN should normally hide your public IP, while your browser should not expose your private LAN address unless something on your system or browser allows it.
Why WebRTC can reveal addresses
WebRTC uses STUN servers, ICE, and network path discovery to set up real-time connections. During that process, your browser may collect candidate addresses from your network interfaces, including addresses from Ethernet, Wi-Fi, and sometimes your VPN adapter.
If the browser sends those candidates to a page's JavaScript, the page can read them. That is why privacy-focused users test WebRTC while connected to a VPN, Tor, or a proxy.
Why you should run a WebRTC leak test with a VPN or proxy
You should run a WebRTC leak test when you want to confirm that your VPN or proxy is hiding the IP address you expect it to hide. It is a quick way to spot a browser-level privacy gap before you rely on that connection for work, streaming, or sensitive browsing.
A VPN changes your visible public IP, but it does not automatically change browser behavior. If WebRTC is enabled and your browser or extension allows it, sites may still see your real network information.
Common situations where leaks matter
A WebRTC leak matters most when you use:
- A commercial VPN for privacy or location masking
- A proxy for region-specific access or account testing
- Tor Browser alternatives where you want stronger browser privacy
- A work laptop that connects to both a home network and a corporate VPN
If you want broader network privacy checks, the VPN, Proxy & Tor Checker can help you compare what different systems expose.
What a leak does and does not mean
A leak does not always mean someone can track your exact street address. It does mean your browser may be exposing information that weakens anonymity, especially the public IP tied to your ISP or the local IP tied to your home network.
That can be enough for location profiling, account linking, or network fingerprinting. It is a small detail with a big privacy impact.
How the WebRTC leak test works in your browser
This test runs in your browser and reads the network details that WebRTC makes available to a page. It does not need you to install software, and it does not need router access or admin rights.
The tool checks whether the browser reports addresses that should stay hidden when you use a VPN, proxy, or privacy-hardened setup. Because the test runs client-side, it can reflect what your browser is actually exposing at that moment.
What the tool may detect
The test may reveal:
- Your real public IP address from your ISP
- Your VPN exit IP address
- Local private IP addresses on your home network
- Interface details from Wi-Fi, Ethernet, or virtual adapters
- IPv6 addresses if your browser and network support them
If you want to compare IPv6 behavior separately, use the IPv6 Test. IPv6 leaks are common on networks where the VPN tunnel covers IPv4 but not IPv6.
Why browser-based testing is useful
A browser-based test shows the same path a website sees. That is useful because many WebRTC leaks are caused by browser settings, extensions, or OS-level networking behavior rather than the VPN app alone.
If the test shows the same IP you expected to hide, you may need to change browser privacy settings, disable WebRTC in the browser, or adjust the VPN's leak protection.
How to read the results of a WebRTC leak test
You should compare the result to the IP address you expect to see while the VPN or proxy is active. If the tool shows your ISP address, your local IP, or both, your browser is exposing more than you want.
The key thing to look for is whether the visible address matches the VPN exit node or your normal home connection. If the result includes private addresses, that can be normal on some systems, but it still matters for privacy-focused browsing.
Common result patterns
| Result pattern | What it usually means | Privacy impact |
|---|---|---|
| Only VPN public IP appears | The VPN is masking your ISP address | Good |
| VPN IP and local private IP appear | The browser can still see local network details | Moderate |
| Real ISP public IP appears | Your VPN or browser is leaking your real IP | High |
| IPv6 address appears outside the VPN tunnel | IPv6 is not fully covered | High |
| No address appears | The browser may block WebRTC candidate exposure | Usually good |
Public IP and private IP are not the same
A public IP address is routable on the internet. A private IP address is not, and it comes from ranges defined for home and office networks, such as 192.168.0.0/16, 10.0.0.0/8, and 172.16.0.0/12.
If you want a deeper explanation of those ranges, see Private IP address ranges explained. For a quick lookup of common router addresses, the default router IP address list is useful.
How to reduce WebRTC leaks on your device and browser
You reduce WebRTC leaks by making sure your browser, VPN, and operating system all agree on which network path to use. That usually means checking browser settings, enabling VPN leak protection, and confirming that IPv6 is handled correctly.
No single fix works on every browser. Chrome, Firefox, Edge, Safari, and mobile browsers all handle WebRTC a little differently.
Browser settings to check
In Firefox, WebRTC controls are often easier to change than in Chromium-based browsers. In Chromium browsers such as Google Chrome, Microsoft Edge, and Brave, you may need a privacy extension or VPN feature because there is no simple built-in switch for every WebRTC leak case.
Check for settings related to local IP exposure, proxy bypassing, or WebRTC blocking. The exact wording varies by browser version.
VPN and router settings to check
Some VPN apps include options like DNS leak protection, IPv6 blocking, or WebRTC protection. Those settings matter because DNS, NAT, and routing behavior can reveal network details even when the tunnel is active.
Your router can also affect the test result if it is using dual-stack IPv4 and IPv6, or if it hands out local addresses through DHCP, the service that assigns IP addresses on your network. If you need to log in to adjust router options, the router login guides by brand and the 192.168.1.1 login page can help, depending on the model.
When changing router settings matters
Router settings matter most when your VPN app protects only the device but not every interface. A router that hands out local IP addresses through DHCP can still leave the browser aware of your LAN address, and a dual-band router may expose separate interfaces for Wi-Fi and Ethernet.
If you do not know your gateway address, start with how to find your router IP address on any device. You can also use the internal IP address index to identify common gateway addresses.
What WebRTC leak testing can tell you about your network setup
A WebRTC leak test can tell you whether your browser sees the network the way you think it does. It can also reveal whether your VPN, proxy, browser, and operating system are working together or fighting each other.
That makes it useful for comparing different privacy setups before you trust them.
Comparing VPNs, proxies, and Tor
A VPN reroutes your traffic through a remote server and usually changes your public IP address. A proxy often changes only app or browser traffic and may not protect everything on the device. Tor routes traffic through multiple relays and is designed for stronger anonymity, but it can break some real-time browser features.
A WebRTC test helps you see where those differences show up in practice. If the browser still exposes your home IP while you use a proxy, the proxy is not covering the full browser path.
Comparing browsers
Some browsers expose fewer network details than others. Privacy-focused browsers often restrict WebRTC candidate exposure more aggressively, while general-purpose browsers may allow more of it by default for compatibility.
If you want to compare browser behavior on the same machine, run this test in Chrome, Firefox, Edge, Brave, and Safari, one at a time. Keep the VPN state unchanged while you compare so the results are easier to interpret.
When you should retest after changing settings
You should retest after any change that might affect networking, privacy, or browser permissions. That includes switching VPN servers, changing browser privacy settings, installing a new extension, or moving from Wi-Fi to Ethernet.
A fresh test is also worth running after router changes, especially if you changed DHCP scope, DNS settings, or IPv6 support.
Good times to run the test again
Run the test again after:
- Turning your VPN on or off
- Switching to a different VPN server region
- Changing browsers or browser profiles
- Enabling or disabling a privacy extension
- Rebooting your router or modem
- Connecting to public Wi-Fi, hotel Wi-Fi, or a work network
If you want to check whether your wider connection changed at the same time, the Router Speed Test and Ping Test can help confirm that your path to the internet is behaving normally.
Troubleshooting when the test still shows your real IP
If the test still shows your real IP, the problem is usually one of three things: the VPN is not fully connected, the browser is exposing WebRTC data, or IPv6 is bypassing the tunnel. The fix depends on which address the test reveals.
Start with the simplest checks first. Make sure the VPN connection is active, then refresh the page, then try a different browser profile or a different browser.
Useful checks in order
- Disconnect and reconnect the VPN.
- Switch to a different VPN server.
- Clear browser cache and reload the page.
- Disable extensions that affect privacy, proxying, or network traffic.
- Check whether IPv6 is enabled and leaking outside the tunnel.
- Test again in another browser.
If the issue looks like a router login or local network problem, your gateway may be one of the common addresses in the default router passwords list or the default password database.
When the result shows a local IP only
If you only see a local private IP, such as 192.168.1.x or 10.0.0.x, your browser may be exposing LAN details but not your public ISP address. That is still worth fixing for privacy, but it is less serious than a full public IP leak.
If you want to identify the range used by your network, the private IP address ranges explained guide can help you map the result correctly.
How this tool fits into a wider privacy check
This tool is one part of a broader privacy check, not the only test you should run. A clean WebRTC result does not guarantee that your DNS, IPv6, or browser fingerprint is hidden, and a bad result does not always mean your entire setup is broken.
For a more complete check, use it alongside other network tools and compare the results. That gives you a better picture of what your browser exposes and what your VPN actually covers.
Useful companion tools
You can pair this test with these pages on the site:
- VPN, Proxy & Tor Checker to see what network path your browser appears to use
- IPv6 Test to spot IPv6 exposure
- MAC Address Lookup if you need to understand device-level identification on your network
- Free network tools to browse related diagnostics in one place
If you need to work on router access or local network settings after a leak test, the 192.168.0.1 login page, 10.0.0.1 login page, and 192.168.1.254 login page cover common gateway addresses used by many routers and ISP-provided devices.
Frequently asked questions
What is a WebRTC leak?
WebRTC (used for browser video calls) can discover your IP addresses through STUN servers, bypassing a proxy and sometimes a VPN, revealing your real IP to websites.
How do I fix a WebRTC leak?
Use a VPN with WebRTC leak protection, disable WebRTC in Firefox (media.peerconnection.enabled = false), or use an extension such as uBlock Origin's "Prevent WebRTC from leaking local IP addresses".
Does a WebRTC leak test use my camera or microphone?
No. A WebRTC leak test checks browser network information, not media hardware. It does not need access to your camera or microphone, and it should not prompt for those permissions.
Why does the test show a local IP address even when my VPN is on?
That can happen because WebRTC can read private network interfaces on your device. A local IP address like 192.168.x.x or 10.x.x.x is part of your home network, not your public internet address, but it can still reveal information you may want to hide.
Can my router cause a WebRTC leak?
The router does not create the leak by itself, but it can affect the addresses your device uses and whether IPv6 is available. If your router, modem, or ISP connection is handling IPv6 differently from IPv4, the browser may expose more information than you expect.
Will a proxy block WebRTC leaks the same way a VPN does?
Not usually. A proxy may change browser traffic, but it often does not protect all network paths on the device, and WebRTC can still expose real addresses if the browser is not configured well. A VPN usually offers stronger system-wide coverage, but it still needs leak protection settings to work properly.
Should I disable WebRTC completely?
Not always. Disabling WebRTC can improve privacy, but it can also break video calls, voice chat, and some browser apps that depend on it. Many people prefer to limit WebRTC exposure instead of turning it off entirely, then retest to make sure the setting works.