How to check browser privacy on public Wi-Fi

You connect to public Wi-Fi and see a login page. Before you sign in to email, banking, or another account, it is sensible to check what your browser is exposing. A VPN can help protect your connection, but it does not make every login safe or hide every kind of activity.

The VPN Leak Test checks whether your real IP address is exposed through IPv6 or WebRTC while your VPN is on. Use it after the Wi-Fi allows internet access, then check that the page you plan to use is legitimate and secure.

Check browser privacy before signing in

1. Connect to the correct Wi-Fi network. Confirm its name with the business, hotel, school, or venue. If a captive portal blocks internet access, you may need to accept its terms or enter an access code before any online test can load. Do not enter an unrelated account password or payment details unless you have verified the portal with the organization.
2. Turn on your VPN before opening personal accounts. On a phone or computer, use the VPN app or the VPN profile you normally trust. If the portal will not load with the VPN on, pause it only long enough to complete the verified network access step, then turn it back on.
3. Open the VPN Leak Test with the VPN connected. Run the test and check whether it reports a possible real IP leak through IPv6 or WebRTC.
4. Before entering an account password, check the address bar. Make sure the domain is the one you expect and the page uses HTTPS. A lock icon does not prove a site is genuine, so read the domain carefully.

If the Wi-Fi requires a browser sign-in before it grants internet access, the leak test cannot run until that step is complete. A captive portal's access page and your personal account login are different things. Use only the information needed to obtain network access, then test your VPN before signing in elsewhere.

What the result means

The test does not report a real IP leak

The test did not detect your real IP address leaking through the IPv6 or WebRTC paths it checks while the VPN is active. That is useful, but it is not a full privacy audit. It does not confirm that a website is trustworthy, check every browser setting, or prevent tracking through cookies and account activity.

The test shows your usual public IP address

Your VPN may be disconnected, may not cover this browser, or may be allowing an address path outside the tunnel. Check the VPN connection and settings, then run the test again. If the result still shows your usual address, avoid sensitive activity on that connection until you understand why.

The test cannot complete

The network may still be blocked by its login page, the VPN may prevent access to the test, or the browser may not support a required feature. A failed test is not proof that your connection is private. Try again after the portal grants internet access, or use cellular data or another trusted connection if you need to sign in now.

A private or local address appears

An address used inside a local network, such as one beginning with 192.168 or 10, is not the same as your public IP address. Do not treat a local address by itself as proof that the public IP has leaked. Focus on whether the test identifies your normal public address outside the VPN.

What to change if the test finds a leak

1. Reconnect the VPN. Open its app and confirm it says connected, not merely installed. For a system VPN profile, Windows 11 has Settings › Network & internet › VPN. On macOS, check System Settings › VPN, or System Settings › Network › VPN on some versions. On iPhone, check Settings › VPN or Settings › General › VPN & Device Management. On Android, look under Settings › Network & internet › VPN, though labels vary by device.
2. Check what the VPN covers. Some browser extensions route only selected browser traffic, while other VPNs cover the whole device. Make sure the browser you are testing is included and that the VPN is not set to exclude the site or connection.
3. Turn on the VPN's leak protections. Look in the VPN app for options that block traffic if the tunnel drops, or prevent IPv6 or WebRTC leaks. Names and availability differ by VPN. Reconnect after changing a setting, then repeat the test.
4. Check for a dropped connection. If the VPN disconnects when Wi-Fi changes or the computer wakes, reconnect it and enable its connection-blocking option if available. On a public network, do not assume the VPN stayed active just because it connected earlier.
5. Use another connection if you are unsure. Switch to cellular data or wait until you can use a trusted network. This is safer than entering a sensitive password while the test result remains unclear.

What a VPN test cannot protect

A VPN leak test checks a narrow question: whether your real IP address is exposed through the IPv6 or WebRTC paths it examines while the VPN is on. It does not verify the Wi-Fi operator, inspect a login page for phishing, or stop a fake website from stealing a password. It also cannot prevent a service you sign in to from associating your activity with your account.

HTTPS protects information sent between your browser and a site when the site uses it correctly, but it does not make a deceptive domain safe. Avoid installing a certificate or profile just because a public Wi-Fi page requests it, and leave if the browser shows a security warning you cannot explain.

For a more detailed explanation of IP leak checks, see How to check whether your VPN leaks your IP address. Nothing in a browser test can guarantee complete privacy on a public network.