How to Check If Your VPN Is Working: A 7-Step Test (2026)

A free, step-by-step way to confirm your VPN actually hides you: compare your IP before and after, then test for DNS, WebRTC and IPv6 leaks, check the kill switch, and fix common problems.

By CloakMyIPAddress Privacy Desk Published

Disclosure: Some links go to VPN providers via our /go/ links and may earn us a commission in future, at no cost to you. Disclosure

On this page
  1. What you need
  2. Step 1: Record your real IP (VPN off)
  3. Step 2: Connect and compare
  4. Step 3: DNS leak test
  5. Step 4: WebRTC leak test
  6. Step 5: IPv6 leak test
  7. Step 6: Test the kill switch
  8. Step 7: Check the apps you actually use
  9. Speed: is a slower connection normal?
  10. Troubleshooting table
  11. If your VPN keeps failing
  12. FAQ
  13. Related guides
  14. Sources

Last reviewed: 30 October 2026 · By the CloakMyIPAddress Privacy Desk

Short answer: a VPN is working when websites see the VPN’s IP address and provider, not yours, and nothing leaks around the tunnel. You can check that in about five minutes with free tools: compare your IP before and after connecting, then run DNS, WebRTC and IPv6 leak tests, and finally test the kill switch. All the tests below run in your browser on this site, without sign-up, and we don’t store results.

What you need

  • Your device with the VPN app installed (but disconnected for step 1)
  • A browser you normally use
  • Five minutes

Step 1: Record your real IP (VPN off)

Open What’s my IP? with the VPN disconnected. Note three things:

  1. Your public IP (IPv4 and, if shown, IPv6)
  2. The location shown
  3. The ISP / organisation name, such as your home broadband or mobile carrier

That’s your baseline. Everything that follows looks for these values.

Step 2: Connect and compare

Connect the VPN to a server in a different city or country, then reload the IP check.

Pass: IP, location and ISP all change. The ISP field usually shows the VPN provider or a hosting company. Fail: you still see your own ISP. The VPN isn’t routing traffic: reconnect, switch protocol, or restart the app.

Location looks wrong? Geolocation databases sometimes place VPN servers in the wrong city or country. If the ISP has changed, the tunnel is working; the database is just inaccurate.

Step 3: DNS leak test

Every time you visit a site, your device asks a DNS server for its address. If those lookups go to your ISP instead of through the VPN, your ISP can still see which sites you visit.

Run the DNS leak test with the VPN connected.

Pass: the DNS servers listed belong to your VPN provider (or a resolver it uses), not your ISP. Fail: you see your ISP’s name. Turn on DNS leak protection in the VPN app, disable custom DNS in your router or OS, or switch off “Secure DNS” in the browser if it overrides the VPN.

Step 4: WebRTC leak test

WebRTC lets browsers make video calls directly, and in doing so it can reveal IP addresses to the website even through a VPN.

Run the WebRTC leak test.

Pass: only the VPN’s IP (or nothing) appears. Local addresses such as 192.168.x.x or random “.local” names are harmless. Fail: your real public IP from step 1 appears. Use the VPN’s browser extension or WebRTC protection setting, or limit WebRTC in your browser (Firefox: media.peerconnection.enabled in about:config; Chromium browsers: an official extension from your VPN or a WebRTC-control extension).

Step 5: IPv6 leak test

Many networks now give you an IPv6 address as well as IPv4. If your VPN only tunnels IPv4, IPv6 traffic can go around it.

Run the IPv6 leak test.

Pass: no IPv6 address, or one that belongs to the VPN. Fail: your ISP’s IPv6 address appears. Turn on IPv6 leak protection in the app, choose a VPN that supports IPv6 tunnelling, or disable IPv6 on the device as a fallback.

Step 6: Test the kill switch

A kill switch blocks the internet if the VPN drops, so your real IP never appears even for a few seconds.

  1. Turn on the kill switch in the VPN app (on Android also use Settings > Network & internet > VPN > gear > Block connections without VPN).
  2. Start something continuous: a large download, a video, or ping 1.1.1.1 -t (Windows) / ping 1.1.1.1 (macOS, Linux).
  3. Force a drop: switch Wi-Fi networks, or end the VPN app’s process in Task Manager or Activity Monitor.
  4. Pass: traffic stops until the VPN reconnects. Fail: traffic continues. Check the setting again, or contact the provider.

Step 7: Check the apps you actually use

Browsers aren’t the only thing that can leak.

  • Torrent clients: bind the client to the VPN’s network interface, so it can’t send traffic if the tunnel drops. Some public “torrent IP check” tools show the IP your client reports to trackers.
  • Split tunnelling: apps you excluded (banking, for example) use your real IP. That’s expected; make sure the list is what you intended.
  • Phones: repeat steps 2–5 on mobile data and on Wi-Fi, since networks behave differently.

Speed: is a slower connection normal?

Some slowdown is normal, because traffic travels further and is encrypted. With modern WireGuard-based protocols it’s often small on a nearby server. If it’s dramatic, try a closer server, switch protocol (WireGuard, NordLynx or Lightway are usually fastest), or avoid TCP mode unless a network requires it.

Troubleshooting table

SymptomLikely causeFix
IP unchangedVPN not connected or app crashedReconnect, change protocol, reinstall
ISP shown in DNS testDNS leakEnable DNS leak protection; remove custom DNS
Real IP in WebRTC testBrowser WebRTCVPN extension or WebRTC setting
ISP IPv6 shownIPv6 not tunnelledEnable IPv6 protection or disable IPv6
Real city on a map siteBrowser or GPS location permissionDeny location permission for that site
Sites show CAPTCHAsShared VPN IP has poor reputationSwitch server; consider a dedicated IP
Streaming says “proxy detected”Service blocks VPN IPsExpected for many services; follow their terms

If your VPN keeps failing

Look for a provider with built-in DNS and IPv6 leak protection, a reliable kill switch and an independently audited no-logs policy, for example Proton VPN, Mullvad, NordVPN, Surfshark or ExpressVPN. Most offer 30-day refunds, so you can run this exact test before you commit. Independent comparisons are on our sister site, NetNinjaVPN.

FAQ

How do I know my VPN works? Your IP, location and ISP change, and the DNS, WebRTC and IPv6 tests show no trace of your real connection.

Why does a site still show my city? It may use GPS or browser location, or the database is wrong about the VPN server.

What is a DNS leak? Lookups going to your ISP instead of through the tunnel.

How do I test the kill switch? Force the VPN to drop during a download. Traffic should stop.

Questions or corrections? Use our contact form.

Sources