Does My VPN Work?

Connecting to a VPN app and actually having a working VPN are different things. A VPN can appear connected while leaking your real IP through WebRTC, DNS, or IPv6. This page explains how to test your VPN properly.

Signs Your VPN Is Working

Check	Passed Result	Failed Result
Public IP address	IP belongs to the VPN provider's network, not your ISP	Your real ISP IP is still visible - VPN is not routing traffic
ISP name shown	Shows the VPN provider's ISP or datacenter name	Shows your home ISP (e.g., Comcast, BT, Telstra)
Country shown	Matches the VPN server location you connected to	Shows your real country - Tunnel is not working
WebRTC IP	No public IP leaked, or only the VPN IP appears	Your real IP or local network IP appears via WebRTC
DNS servers	DNS queries resolve via the VPN provider's resolvers	ISP's DNS servers appear - DNS leak present

Common Reasons a VPN Stops Working

• VPN client crashed silently: The app may show connected but the tunnel has dropped. Enable the kill switch to block all traffic when this happens.
• Network change: Switching from Wi-Fi to mobile data or changing networks can break the VPN tunnel without the app reconnecting.
• Split tunnelling misconfiguration: If your browser is excluded from the VPN tunnel, your browsing traffic bypasses the VPN entirely.
• Protocol blocked: Some networks (hotel Wi-Fi, corporate firewalls) block certain VPN protocols. Switch to OpenVPN TCP port 443 or a stealth protocol.
• IPv6 not tunnelled: If your VPN only handles IPv4, your IPv6 traffic bypasses the VPN. Disable IPv6 in your OS or use a VPN with full IPv6 support.
• Outdated client: VPN client updates often include leak fixes. Keep your client up to date.

How to Fix a VPN That Isn't Working

1. Disconnect and reconnect the VPN.
2. Switch to a different server in the same country.
3. Change the protocol (try WireGuard, then OpenVPN TCP).
4. Restart the VPN client completely (not just the connection).
5. Reboot your device.
6. Disable and re-enable your network adapter, then reconnect.
7. Contact your VPN provider's support with the results of our leak test.

See also: What Is a VPN Kill Switch? | VPN Protocols Explained.

Frequently Asked Questions

My VPN says connected — is that enough?

No. 'Connected' only means the client established a tunnel. It says nothing about whether DNS queries, IPv6 traffic, or WebRTC requests are bypassing that tunnel, and all three commonly do.

What are the three leaks I should test for?

IP leak (your real address still visible), DNS leak (queries going to your ISP's resolvers rather than the VPN's), and WebRTC leak (the browser exposing your local address directly to a page).

How often should I re-test?

After every major client update, after switching protocols, and after any operating-system upgrade. Leak protection regresses more often than people expect.

What should I do if I find a leak?

Enable the provider's built-in DNS-leak protection and kill switch first, then disable IPv6 if the provider does not support it, and block WebRTC in your browser. If leaks persist, the provider is the problem.

How we evaluate VPNs: every provider on this site is judged on audited no-logs claims, leak-test results, protocol support, jurisdiction, and price transparency — never on commission. See the criteria in full →

ⓘ Affiliate disclosure: Some links to VPN providers in these guides are affiliate links - We may earn a commission at no extra cost to you. This never affects rankings or evaluations.

Last updated: 2026-08-02