Compare full-device and browser-only VPN coverage

Your VPN may protect every app on your computer, or it may route traffic only from one browser. The difference matters when you open another browser, use a game or call app, or rely on a VPN for privacy outside web pages.

Use the VPN Leak Test to compare what the browser shows with each setup. It checks for exposure through IPv6 and WebRTC, but it cannot inspect every app or prove that all device traffic uses the VPN.

Compare the two VPN setups

1. Open the VPN Leak Test in the browser you want to check. First disconnect any VPN and note the public IP address shown in the test. This is your baseline for comparison.
2. Turn on your full-device VPN app. Turn off any VPN or proxy browser extension so the two methods do not overlap. Check that the app says it is connected, then run the test again.
3. Note whether the test now shows a different public IP and whether it reports an IPv6 or WebRTC leak. Compare these results with the baseline, not just with the VPN app's map or country label.
4. Disconnect the full-device VPN. Turn it off in the VPN app, then enable the browser-only VPN extension. Run the test again in the same browser and compare the IP and leak results.
5. If you use more than one browser, repeat the browser-only check in each one. An extension installed in one browser does not automatically cover the others.

Keep the same network and browser for each run. VPN servers and addresses can change, so focus on whether your normal connection's public address appears, not whether every run has the exact same VPN address.

What the results mean

The public IP changes and no leak is reported

The tested browser appears to be using a different public route, and the test did not detect exposure through the IPv6 or WebRTC checks it performs. This is useful evidence about that browser session. It does not prove that other apps use the VPN, or that the VPN protects against every kind of leak.

Your normal public IP still appears

The browser's connection may be bypassing the VPN, or the VPN may not be connected. With a browser-only extension, check that it is enabled for this browser and that the test page is not excluded. With a full-device VPN, check for split tunneling, a feature that deliberately leaves selected apps or traffic outside the VPN.

The test reports an IPv6 or WebRTC leak

Some traffic is revealing your regular connection details even though the public IP changed. A VPN may route IPv4 traffic while leaving IPv6 outside its tunnel, or the browser may expose connection information through WebRTC. Review the relevant protection settings in the VPN app or extension, then run the test again.

The browser-only and full-device results look the same

That can be expected for this test. Both setups may route this browser through a VPN, while other programs still use your normal connection when only the extension is active. The test cannot compare traffic from apps it does not run. For more on checking an extension, see how to verify a browser-only VPN extension is working.

How to fix a mismatch

1. Check which VPN is active. For a clean comparison, disconnect the full-device VPN before testing the browser extension, and disable the extension before testing the device VPN. Two active VPN routes can make results hard to interpret.
2. Confirm the full-device connection. Check the VPN app itself for a connected status. On Windows 11, open Settings › Network & internet › VPN to review system VPN connections. On macOS, open System Settings › VPN if that option is available. Many VPN services manage the connection in their own app, so verify it there too.
3. Review split tunneling. In the VPN app, check whether the browser is excluded or whether only selected apps are sent through the VPN. Turn off exclusions for the test browser if you want it protected. Menu names differ between VPN apps.
4. Check the browser extension. Make sure the extension is enabled and connected in the browser you are testing. Check its site or traffic exclusions, and confirm that a second extension is not changing proxy settings. If you need help with extension behavior, compare the result with VPN behavior in normal and private tabs.
5. Look for IPv6 protection. If the test reports an IPv6 leak, check whether your VPN offers IPv6 leak protection and enable it. Do not disable IPv6 across your computer unless you understand the effect on your network and have a specific reason to do so.
6. Recheck WebRTC protection. If WebRTC is the issue, look for a WebRTC or IP leak protection option in the VPN app or extension. Browser controls can affect calling and video features, so retest those services after changing a setting.
7. Reconnect and test again. Disconnect and reconnect the VPN, reload the test page, and repeat the check. If the regular address still appears, contact the VPN provider with the result and whether you used the full-device app or browser extension.

Know what this comparison cannot prove

A browser leak test checks connections made in the tested browser. It does not inspect traffic from a desktop app, another browser, or a device on your local network. A clean result therefore cannot confirm that your full computer is covered. For that, review the VPN's routing and split-tunneling settings, then test the specific apps you rely on.

The VPN Leak Test checks IPv6 and WebRTC exposure. It is not a complete audit of VPN security, account privacy, DNS behavior, or every connection your device makes. A VPN can also change your visible IP without making you anonymous. See what a VPN test cannot prove about online anonymity for the limits of an IP check.

The test runs in your browser, and its results describe the browser session you tested, not every app on your device.