Guides

How to Test If Your VPN Is Working

A VPN that says connected can still leak your IP, DNS, or traffic. Run these free checks in minutes: IP change, DNS and WebRTC leaks, kill switch, IPv6, speed, and streaming. Know you are protected, do not assume it.

VPNRatings Editorial · Jun 29, 2026 · updated Jun 22, 2026
How to Test If Your VPN Is Working
Table of contents
  1. Step 1: Check your IP address changed
  2. Step 2: Test for DNS leaks
  3. Step 3: Test for WebRTC leaks
  4. Step 4: Verify the kill switch
  5. Step 5: Check for IPv6 leaks
  6. Step 6 and 7: Speed and streaming
  7. Quick test checklist
  8. Bottom line

Installing a VPN is easy; confirming it actually protects you is the step most people skip. A VPN that shows "connected" can still be leaking your real IP address, your DNS queries, or your traffic during a reconnection — and you would never know from the app's status light. The fix is a short routine of free checks you can run in a few minutes. This how-to shows you exactly how to test whether your VPN is working: your IP, DNS and WebRTC leaks, the kill switch, IPv6, speed, and streaming access.

Step 1: Check your IP address changed

This is the most basic test. With the VPN off, visit any "what is my IP" site and note the address and location — that is your real IP. Now connect the VPN to a server in another city or country and reload the page. The IP and location should now match the VPN server, not your home. If your real IP or true location still shows, the VPN is not routing your traffic and nothing else it does matters until you fix that.

Step 2: Test for DNS leaks

Even with a new IP, your device might still send domain lookups (DNS queries) to your ISP outside the tunnel — a DNS leak that quietly reveals which sites you visit and your real region. Use a free DNS-leak test site while connected. The servers it reports should belong to your VPN provider, not your ISP. If you see your ISP's name, enable the VPN's DNS-leak protection (most have it) or switch the setting that forces DNS through the tunnel.

Step 3: Test for WebRTC leaks

Browsers can expose your real IP through a feature called WebRTC, even while the VPN is connected — a common and sneaky leak. Run a WebRTC-leak test (many leak-test sites cover this too) with the VPN on. It should not display your real public IP. If it does, use a browser extension to disable WebRTC or your VPN's built-in browser protection.

Step 4: Verify the kill switch

The kill switch is your safety net: if the VPN drops, it should block all internet traffic so nothing leaks in the gap. To test it, connect the VPN, start something that uses the network (a streaming page or a continuous download), then forcibly cut the VPN — quit the VPN process or toggle airplane mode briefly. Your internet should stop entirely until the VPN reconnects. If traffic keeps flowing unprotected, the kill switch is off or not working; enable it in settings.

Step 5: Check for IPv6 leaks

Many VPNs are built around IPv4, and if your network uses IPv6, traffic can escape the tunnel over IPv6 and leak your address. A general leak-test site will flag an exposed IPv6 address. If you see one, enable IPv6 leak protection in your VPN app, or disable IPv6 on your device if the app does not handle it.

Step 6 and 7: Speed and streaming

Test How What good looks like
Speed Run a speed test VPN-off, then VPN-on (nearby and distant servers) Some drop is normal; still fast enough for your use
Streaming Connect to a relevant server, open the service Correct regional library loads, plays in HD

Expect a speed reduction — encryption and an extra hop always cost something. What matters is that a nearby server stays fast enough for HD streaming and video calls. For streaming, connect before opening the app, and if the wrong region loads, switch servers or clear the cache.

Quick test checklist

  • IP address changes to the server's location
  • DNS test shows the VPN's servers, not your ISP's
  • WebRTC test does not reveal your real IP
  • Kill switch cuts internet when the VPN drops
  • No exposed IPv6 address
  • Speed is acceptable; streaming loads the right library

Bottom line

A VPN is only doing its job if your IP, DNS, and WebRTC all point to the VPN rather than to you, the kill switch genuinely cuts traffic on a drop, and no IPv6 address slips out. Run this routine right after installing a new VPN and again after any big app update, since updates can reset settings. Ten minutes of testing is the difference between assuming you are protected and knowing it.

Get a VPN that passes every test