Why websites can still see your IP with a VPN
Learn why a website can see an IP address while your VPN is on, how to tell a VPN server address from a leak, and what to check next.
A website has to receive your internet connection to load a page, so it can always see an IP address. When your VPN is working, the site should normally see the VPN server's address, not the public address assigned to your home or phone connection.
If a site shows your usual location or internet provider while the VPN is connected, check whether your browser traffic is bypassing the VPN or whether IPv6 or WebRTC is exposing your real address. The VPN Leak Test checks for real IP leaks through IPv6 and WebRTC.
Check what your browser reveals
- Connect to your VPN, then open the VPN Leak Test in the same browser you use for the website in question.
- Run the test while the VPN remains connected. If your VPN has a browser extension, confirm that the extension is connected in this browser too.
- Review the addresses and any leak findings. Compare the address shown with the VPN server address or location shown by your VPN app. The VPN may use a different address from the one you expect for its selected city.
- If the test indicates that your real IP is exposed, note whether the finding relates to IPv6 or WebRTC. These point to different things to check below.
- Reload the test and repeat once. If the result changes, reconnect the VPN and check whether the test was interrupted by a brief disconnect.
Do not compare only the city name. IP location databases can be inaccurate, and a VPN server can be registered in a different city or region from the one you selected. Compare the address itself, and whether it belongs to your VPN provider or your normal internet provider.
What the result means
The website sees a VPN server address
This is the expected result. The VPN routes your browser connection through its server, and websites see that server's public IP address. Some sites recognize VPN addresses and may show a security check, block access, or offer content for the server's location. That does not by itself mean your real IP leaked.
Your usual internet provider or home address appears
Your browser may be connecting outside the VPN, or a route may be exposing your regular public address. Check for split tunneling, where a VPN sends only selected apps or sites through its tunnel. Also check whether the connection dropped while the page or test was loading.
The test reports an IPv6 exposure
Your connection may have an IPv6 route that the VPN does not cover. IPv6 is a type of internet addressing used alongside the more familiar IPv4. Look for IPv6 support or leak protection in the VPN app. For more detail, see why an IPv6 address may appear while a VPN is on.
The test reports a WebRTC exposure
WebRTC is browser technology used for real-time calls and audio or video sharing. Under some network and browser configurations, it can reveal an address that a website could use to identify your connection. A VPN that handles WebRTC traffic correctly should prevent your real public IP from appearing through it. Changing WebRTC settings can affect calls, so test your meeting apps afterward.
The test finds no real IP leak, but a site still knows who you are
An IP address is only one part of online identification. If you sign in, use the same account, or allow a site to store cookies, it can recognize you without seeing your home IP. A VPN does not erase account history or make browsing anonymous. A site can also see the VPN server address and use that to infer that a VPN may be in use.
How to fix a real IP exposure
- Reconnect the VPN before opening the site. Disconnect and reconnect in the VPN app, wait for its connected status, then reload the page. If the VPN keeps disconnecting, check its connection or kill switch settings.
- Check that this browser uses the VPN. If you use a browser VPN extension, make sure it is enabled for the current browser profile and has not been paused for the site. A browser extension may route only browser traffic, while a VPN app can route traffic from other apps too.
- Turn off split tunneling for the browser. In your VPN app, look for split tunneling, excluded apps, or bypass rules. Remove the browser from the excluded list, or route all browser traffic through the VPN. Setting names differ by provider, so use the app's own help if you cannot find them.
- Check the system VPN connection. On Windows 11, open Settings › Network & internet › VPN and confirm the connection is active if it is managed by Windows. On macOS, check System Settings › VPN if the connection is configured there, or use the VPN app's own controls. On Android, look under Settings › Network & internet › VPN. On iPhone, check Settings › General › VPN & Device Management › VPN. Menu names can vary by device and operating system version.
- Enable IPv6 protection or support. If the test specifically reports IPv6, check the VPN app for an IPv6 option or leak protection. Prefer the provider's supported setting rather than changing network settings at random. Retest after making a change.
- Review WebRTC privacy without breaking calls. If the test identifies WebRTC, check your browser and VPN app for a setting that prevents WebRTC from exposing the real public IP. Avoid disabling WebRTC entirely if you rely on browser-based voice or video calls, unless you have tested that those calls still work.
- Use the VPN provider's next steps if the leak remains. Repeat the test after updating the VPN app and browser. If your usual public IP still appears, contact the VPN provider with the type of exposure and the browser you tested. The guide VPN leak detected: what to do next covers follow-up checks.
What a VPN leak test cannot prove
A browser test checks what is visible from that browser at that moment. It cannot prove that every app on your device uses the VPN, that the VPN never disconnects, or that a website cannot identify you through an account or cookies. Run the test in each browser you use, especially if you have separate VPN extensions or profiles.
DNS is another part of VPN privacy, but it is not the same as a website seeing your IP. A DNS leak may let a network operator or DNS provider learn which domain names your device requests. It does not automatically mean the website itself received your home IP. Check your VPN provider's DNS protection separately if that is your concern.
If you need to confirm what a particular website sees, run the test in the same browser and VPN setup, then check whether the site is showing the VPN's address or your regular public address.
