A VPN can change the public IP address that websites see, but it does not automatically make every browser signal private. A correct VPN test compares several layers: the page-visible public IP, WebRTC candidates, browser fingerprint signals, account state, and location clues. Start with the IP check tool, then use the WebRTC leak test to look for unexpected public candidates.

How to test

First test without the VPN and record your normal public IP, country, provider, time zone, and browser. Then connect to the VPN and reload the same pages. The public IP should change to the VPN exit network. If WebRTC shows the same VPN public IP, that is not a leak by itself. A possible leak is when WebRTC shows a different public address that appears to come from your real network.

How to interpret the result

The key question is not whether a public IP exists. The question is whether the public IP matches the network identity you expect. VPNs also do not erase cookies, logged-in accounts, browser language, time zone, or device fingerprint signals.

Limitations

Some VPN apps protect the whole device, while browser proxies may protect only browser traffic. Corporate networks, mobile carriers, and dual-stack IPv4/IPv6 setups can also make results look different from simple tutorials.

What you can do

Enable your VPN app's leak protection, test IPv4 and IPv6 if available, clear old site permissions, and use a separate browser profile for sensitive sessions. Retest after browser or VPN updates.

FAQ

Is every WebRTC public IP a leak? No. It must be compared with the page-visible public IP.

Does a VPN hide my browser fingerprint? No. It mainly changes network routing.

Should I panic if the city is wrong? No. IP geolocation is approximate.