How to Check if Your VPN Is Working: 5 Tests to Run Right Now

Why You Shouldn't Assume Your VPN Is Working

Most people install a VPN, turn it on, and assume they're protected. That assumption is often wrong. VPNs can fail in several ways that aren't immediately obvious: your real IP address can leak through WebRTC even when the VPN tunnel is active, DNS queries can bypass the VPN entirely and reveal your browsing activity to your ISP, and kill switches don't always activate when they should.

The only way to know your VPN is actually protecting you is to verify it. These five tests take about ten minutes total and will tell you definitively whether your VPN is doing its job.

Test 1: IP Address Check

This is the most basic test and the first one to run. Your IP address identifies your location and your ISP to every website you visit. A working VPN should replace your real IP with the VPN server's IP.

How to run it:

1. With your VPN disconnected, visit limevpn.com/tools/what-is-my-ip and note your real IP address and location
2. Connect to your VPN and select a server
3. Refresh the page — or visit it again
4. Your IP address should now show the VPN server's IP, not your real one. The location should match the VPN server location you selected.

What if it fails? If your real IP still shows after connecting, the VPN tunnel has not established correctly. Try disconnecting and reconnecting, switching servers, or switching protocols (try WireGuard if you were on OpenVPN). If the problem persists, contact your VPN provider's support.

Test 2: DNS Leak Test

DNS leaks are more common than IP leaks and more dangerous in some ways. Even if your IP address is successfully masked, your DNS queries might still be going to your ISP's DNS servers — revealing every domain you visit. Your ISP can see (and in many countries, is legally required to log) your DNS queries.

A DNS query is made every time you visit a website: your browser asks a DNS server "what's the IP address for example.com?" If that query goes to your ISP's DNS resolver instead of your VPN's, your ISP sees your browsing activity regardless of the VPN.

How to run it:

1. Connect to your VPN
2. Visit limevpn.com/tools/dns-leak-test
3. The tool will show you which DNS servers your queries are going to
4. All DNS servers shown should belong to your VPN provider — not your ISP

What to look for: If you see DNS servers associated with your ISP (Comcast, BT, Telstra, etc.) or Google/Cloudflare public DNS that you haven't configured yourself, your DNS is leaking. The DNS servers shown should be operated by your VPN provider.

How to fix a DNS leak: In your VPN app, look for a DNS leak protection setting and ensure it's enabled. On Windows, you may also need to manually set your DNS servers to your VPN provider's DNS under network adapter settings. Contact your VPN provider's support if DNS leak protection isn't working correctly.

Test 3: WebRTC Leak Test

WebRTC is a browser technology that enables real-time communication features — video calls, voice chat, file sharing — directly in the browser without plugins. It's built into Chrome, Firefox, Edge, and Safari. The problem: WebRTC can bypass your VPN tunnel and expose your real IP address to websites, even when your VPN is active.

This happens because WebRTC uses STUN (Session Traversal Utilities for NAT) servers to discover your network configuration, and this process can reveal your real IP even when all your other traffic is routed through the VPN.

How to run it:

1. Connect to your VPN
2. Visit limevpn.com/tools/ip-leak-test
3. The tool checks for WebRTC leaks in addition to standard IP checks
4. Your real IP address should not appear anywhere on the page

What a WebRTC leak looks like: The page will show both your VPN IP and — if leaking — your actual IP address. Any appearance of your ISP-assigned IP is a leak.

How to fix WebRTC leaks: Many VPN apps include WebRTC leak protection. Enable it in your VPN's settings. Alternatively, in Firefox, you can disable WebRTC entirely by navigating to about:config and setting media.peerconnection.enabled to false. In Chrome, browser extensions like "WebRTC Leak Prevent" can help, but a VPN with built-in WebRTC protection is more reliable.

Test 4: Kill Switch Test

A kill switch blocks all internet traffic if the VPN connection drops unexpectedly. Without a working kill switch, any brief VPN disconnection — during a server change, network interruption, or app crash — exposes your real IP and unencrypted traffic for the duration of the outage.

The only way to know your kill switch works is to test it.

How to run it:

1. Ensure your VPN kill switch is enabled in the app settings
2. Connect to a VPN server
3. Start a continuous activity that will immediately show if connectivity is lost — a speed test at limevpn.com/tools/speed-test works well, or a large file download
4. Disconnect the VPN connection from the app while the activity is running (don't just pause — fully disconnect)
5. Your internet should stop immediately. If the speed test continues or the download keeps going, your kill switch is not working.
6. Reconnect the VPN — internet should restore promptly

Why this matters most for torrent users: If you're using a VPN while torrenting and the VPN drops without a kill switch, your real IP is briefly visible to every peer in the swarm. Torrent monitoring organizations log these IPs continuously — even a few seconds of exposure can result in a logged record of your real IP associated with the torrent.

Test 5: Speed Test

A VPN should protect you without crippling your connection speed. While some speed reduction is expected — your traffic is traveling through an additional server and being encrypted — a good VPN using WireGuard protocol should reduce your speed by less than 10-15% on a nearby server.

How to run it:

1. Disconnect your VPN and run a baseline speed test at limevpn.com/tools/speed-test. Note your download speed, upload speed, and ping.
2. Connect to your nearest VPN server using WireGuard protocol
3. Run the speed test again
4. Calculate the reduction: (baseline speed − VPN speed) / baseline speed × 100

Benchmarks to expect:

• WireGuard on nearest server: 5–15% speed reduction
• OpenVPN on nearest server: 20–40% speed reduction
• Connecting to a distant server: add 10–30% more reduction depending on distance

When a VPN makes you faster: If your ISP throttles specific types of traffic — video streaming, gaming, peer-to-peer — your speed with VPN may actually be higher than without. ISPs can only throttle traffic they can identify. Encrypted VPN traffic is opaque to your ISP, so if they throttle Netflix or YouTube specifically, the VPN prevents that throttling.

What to Do If Your VPN Is Leaking or Underperforming

1. Switch protocol to WireGuard — it's faster, more stable, and has fewer leak issues than OpenVPN or IKEv2
2. Enable all leak protection settings — DNS leak protection, WebRTC protection, IPv6 leak protection
3. Check your kill switch settings — ensure it's set to system-level (not app-level only) if the option exists
4. Try a different server — server overload can cause both leaks and speed issues
5. Reinstall the VPN app — corrupted installations can cause intermittent leaks
6. Contact support — if tests consistently fail, the problem may be a configuration issue the VPN provider can diagnose

Quick Reference: LimeVPN Test Tools

• IP address check: limevpn.com/tools/what-is-my-ip
• DNS leak test: limevpn.com/tools/dns-leak-test
• WebRTC / IP leak test: limevpn.com/tools/ip-leak-test
• Speed test: limevpn.com/tools/speed-test

Run all four tests whenever you switch VPN providers, update the app, or change your network configuration. Ten minutes of verification protects against weeks of assumed-but-failed privacy.