How to verify VPN behavior with two browser profiles

You want to know whether your VPN is actually changing what a website can see, and whether it works in every browser profile. A simple comparison can help, but the right test depends on whether your VPN is a browser extension or an app that routes the whole device.

Use the VPN Leak Test in both profiles. It checks whether your real IP address appears through IPv6 or WebRTC while the VPN is on. It does not test every kind of traffic or prove that all apps use the VPN.

Compare two browser profiles

1. Make two profiles in the same browser. Name them something easy to recognize, such as Regular and VPN check. A browser profile keeps its own extensions and settings. A private window is not a reliable substitute because extension behavior can differ there.
2. Set up the profiles for your type of VPN. For a browser extension, install and enable it in the profile you want to protect, and leave it off in the other profile. For a VPN app that connects the whole device, both profiles use the same system connection. Do not expect one profile to bypass a device-wide VPN.
3. Check the regular profile first. If you are comfortable doing so, disconnect the VPN and open the VPN Leak Test. Note whether it reports your usual public IP. You can skip this baseline if you do not want to expose your normal connection to a test page.
4. Test the VPN profile. Connect the VPN, open the test in the profile you configured, and review whether the IP shown through IPv6 or WebRTC matches the VPN connection or your usual connection. For a system-wide VPN, connect it and run the test in both profiles.
5. Repeat once in each profile. Keep the same browser, network, and VPN location. If the result changes, reconnect the VPN and test again before deciding that there is a leak.

Keep a private note of the result rather than posting your IP address in a screenshot or support forum. The VPN test needs to observe the address that reaches it, but your public IP can reveal information about your connection.

What the result means

The VPN profile shows the VPN connection, and the other profile shows your usual connection

This is the expected split when a browser extension protects only the profile where it is enabled. It confirms the tested profile's connection looks different for the checks the tool performs. It does not confirm that every website request or other app is routed through the VPN.

Both profiles show the VPN connection

This can be normal when a VPN app routes all device traffic. If you use a browser extension, check whether it was installed or enabled in both profiles, or whether another system VPN is running. A matching result alone does not prove that the extension is working.

The VPN profile shows your usual IP through IPv6 or WebRTC

This can mean that some browser traffic is not following the VPN route. First confirm the VPN says it is connected, then check its leak protection and routing settings. A result from this test is a reason to investigate, not a complete audit of the VPN.

The address differs between checks

VPN providers can use changing exit addresses, and your internet connection can change too. Compare whether the test sees your normal connection or the VPN connection, rather than expecting one exact address to remain constant.

How to fix a result that does not match your setup

1. Confirm which profile has the extension. Open the profile menu and check that you are testing the intended profile. In Chrome or Edge, open the browser menu and choose Extensions › Manage extensions to check whether the VPN extension is enabled for that profile.
2. Reconnect the VPN. Disconnect, wait a few seconds, and connect again. Check the extension or VPN app for a clear connected state before rerunning the test.
3. Check split tunneling and site rules. Split tunneling lets selected apps or websites bypass the VPN. Review the VPN's settings for excluded websites, bypass lists, or rules that apply only to certain browser profiles. Remove an exception only if you want that traffic to use the VPN.
4. Review leak protection in the VPN. Look for settings that specifically address IPv6 or WebRTC leaks. Names and availability differ by provider, so use its help instructions rather than changing unrelated browser settings.
5. Check whether the VPN is system-wide. On Windows 11, open Settings › Network & internet › VPN to review a built-in VPN connection. On macOS, open System Settings › VPN. A VPN app may manage its connection in its own window instead. A device-wide connection normally affects both browser profiles.
6. Close other VPN or proxy software. Two VPNs, proxy settings, or traffic-filtering apps can make results confusing. Disconnect other services one at a time, reconnect the VPN you intend to use, and repeat the test.
7. Retest after changing one setting. Change one thing at a time so you can tell what helped. If the result still exposes your usual IP while the VPN claims to protect the browser, contact the VPN provider with the browser name, profile setup, and test result. Avoid sending your full IP publicly.

What two profiles can and cannot prove

Profiles are useful for checking whether a browser extension is active in one place but not another. They do not create separate network connections by themselves. If a VPN runs at the operating-system level, both profiles generally share that connection. If it is a browser extension, only traffic the extension handles may be routed through it.

The VPN Leak Test checks IPv6 and WebRTC exposure. It does not establish whether DNS requests, non-browser apps, or every website request are protected. For a broader check of a browser-only VPN extension, see how to verify a browser-only VPN extension is working.

Use the same network and VPN location for each comparison, and rerun the test after a browser or VPN update.