Step-by-Step: Running the Test
Worth knowing: A WebRTC leak check typically completes in under 5 seconds, since it only needs to gather ICE candidates through a STUN server rather than load a full page.
- Connect to your VPN and confirm it shows as connected.
- Open the browser you actually use for daily browsing — the leak is browser-specific.
- Run a WebRTC leak test and review every IP address listed in the results.
- Compare the addresses shown against your VPN's assigned IP.
- Repeat in each browser installed on your device, since a leak fixed in one doesn't apply to another.
Run the check now — it takes under a minute and needs no installation.
Run the WebRTC Leak Test →How to Read Your Results
A clean result shows a single IP address matching your VPN server's location. A leak shows two: your VPN's IP address, and a second one that traces back to your actual internet connection and location. That second address is what a website or service could use to identify your real network, even while your VPN otherwise appears to be working normally.
Why Testing in Every Browser Matters
WebRTC leak behavior, along with any protective extensions or manual settings you've applied, is scoped to each individual browser. Fixing the leak in Chrome does nothing for Firefox or Safari installed on the same computer. If you regularly switch between browsers, each one needs its own separate check and, if needed, its own separate fix.
What to Do If a Leak Is Found
Three options close a confirmed WebRTC leak: disabling WebRTC directly in your browser's settings where that option exists, installing a browser extension built specifically to block WebRTC IP exposure, or switching to a VPN that explicitly includes WebRTC leak protection as a feature. After applying any of these, re-run the test to confirm the leak is actually gone rather than assuming the fix worked.
Testing on Mobile Browsers
WebRTC leak checks work the same way on mobile browsers as on desktop — connect to your VPN, run the test, and compare the IP addresses shown. Mobile browsers vary more in how much control they give over WebRTC settings, so an extension or a VPN-level fix is often more practical on mobile than trying to disable the feature directly.
Make It a Habit, Not a One-Time Check
A browser update, a VPN app update, or a new extension can all silently change WebRTC behavior. Running this test occasionally, rather than only once when first setting up a VPN, catches leaks introduced by these changes before they go unnoticed for an extended period.
A Quick Sanity Check Before You Start
Before testing, double-check that your VPN app actually shows "Connected" and that you're testing in the same browser window you normally use, not a fresh one with different extensions or settings. A test run in the wrong context can produce a misleading result in either direction, so matching your real, everyday setup gives the most accurate picture.
Curious what a dedicated leak-blocking extension actually does compared to disabling WebRTC manually?
Read: What Is a WebRTC Leak Shield? →For more background, see MDN's WebRTC documentation (developer.mozilla.org).
Frequently Asked Questions
How do I test my browser for WebRTC leaks?
Connect to your VPN, then run a WebRTC leak test. If only your VPN's IP address appears in the results, WebRTC is not leaking. If your real IP also appears alongside it, a leak was detected.
Do I need to test every browser I use separately?
Yes. WebRTC behavior and any extensions or settings you've applied are specific to each browser, so a leak fixed in one browser can still be present in another installed on the same device.
What should I do if the test finds a leak?
Disable WebRTC in your browser settings if supported, install a WebRTC leak shield extension, or switch to a VPN with built-in WebRTC leak protection, then re-test to confirm the leak is closed.