DNS Leak Checker
Running live test…

Is My VPN Working? 3 Tests to Check Right Now

You're paying for a VPN. The app says you're connected. But are you actually protected? The uncomfortable truth is that many VPNs show a green "connected" badge while silently leaking your data through DNS queries, WebRTC, or IPv6 traffic.

The only way to know for certain is to test. In this guide, we'll walk you through three critical tests that take less than two minutes combined. If all three pass, your VPN is doing its job. If any one fails, your privacy is compromised — and we'll show you exactly how to fix it.

The 3-Step VPN Verification Checklist

A properly functioning VPN must pass all three of these tests. Passing one or two isn't enough — each test checks a different aspect of your privacy, and a failure in any one of them means your real identity or browsing activity is being exposed.

Test 1: IP Address Check

What it tests: Whether your real IP address is hidden and replaced with your VPN server's IP address.

How to do it: Visit our IP Checker tool. It will display the IP address that websites see when you visit them.

How to read the results: The IP address shown should match the location of the VPN server you're connected to. If you connected to a server in Germany, you should see a German IP address. If you see your actual home IP address or your real city/ISP, your VPN is not masking your IP correctly.

Common issue: If the IP shows your real location, try disconnecting and reconnecting your VPN. If the problem persists, your VPN may have a broken connection or your traffic might be using split tunneling that excludes your browser.

Test 2: DNS Leak Test

What it tests: Whether your DNS queries (the requests that translate website names into IP addresses) are going through your VPN or leaking to your ISP.

How to do it: Run our DNS Leak Checker on the homepage. It identifies which DNS servers are handling your queries.

How to read the results: The DNS servers listed should belong to your VPN provider — not your ISP. If you see server names containing your ISP's name (like "comcast," "att," "bt," or "vodafone"), your DNS is leaking. Even if your IP test passed, a DNS leak means your ISP can see every website you visit.

Common issue: Windows users often experience DNS leaks due to Smart Multi-Homed Name Resolution, which sends DNS queries through all network adapters simultaneously. See our Windows DNS leak fix for a step-by-step solution.

Test 3: WebRTC Leak Test

What it tests: Whether your browser is exposing your real IP address through WebRTC, a technology used for real-time communication (video calls, file sharing) that can bypass VPN tunnels.

How to do it: Run our WebRTC Leak Test. It checks whether your browser's WebRTC implementation is revealing your real IP address.

How to read the results: If the test shows your real public IP address (the one from Test 1 with VPN disconnected), you have a WebRTC leak. The IP addresses shown should either be your VPN's IP or local/private addresses (starting with 192.168, 10., or 172.16-31).

Common issue: Chrome and Chromium-based browsers are particularly vulnerable to WebRTC leaks. See our Chrome WebRTC fix or Firefox WebRTC fix guides.

Why Your VPN Shows "Connected" But Isn't Protecting You

This is one of the most common — and most dangerous — VPN issues. Your VPN app displays a reassuring "Connected" status, but one or more of the tests above fails. Here's why this happens:

The VPN Tunnel Exists, But Traffic Leaks Around It

A VPN creates an encrypted tunnel for your traffic. But "connected" only means the tunnel exists — it doesn't guarantee that all your traffic goes through it. DNS queries, WebRTC connections, and IPv6 traffic can all take different paths that bypass the tunnel entirely. Your VPN app has no way to detect this because it only monitors its own tunnel.

Split Tunneling Is Excluding Your Browser

Some VPNs offer split tunneling, which lets you choose which applications use the VPN. If your browser isn't included in the tunnel, all your web traffic — DNS queries, IP address, everything — goes through your regular ISP connection. Check your VPN's split tunneling settings and make sure your browser is included.

Your OS Is Overriding VPN DNS Settings

Both Windows and macOS can override VPN DNS settings in certain situations. Windows' Smart Multi-Homed Name Resolution is a common culprit — it queries all available DNS servers simultaneously for speed, which means your ISP's DNS gets queried alongside your VPN's DNS. The result: your VPN is "working," but your browsing history is still visible to your ISP.

The VPN Connection Dropped and Reconnected

VPN connections can momentarily drop due to network instability, switching between Wi-Fi networks, or when your device wakes from sleep. Without a kill switch, all traffic flows unprotected during these gaps. The VPN reconnects quickly, so you never notice — but any DNS queries or connections made during the gap are exposed.

Understanding False Positives in VPN Testing

Before you panic about test results, understand that not every unexpected result means your VPN is broken. Here are common false positives:

What to Do When Tests Reveal Problems

If any of the three tests failed, here's what to do next based on which test showed a problem:

If multiple tests fail or if your VPN consistently shows leaks despite configuration changes, it may be time to consider a more reliable VPN. Our comparison of VPNs with the best leak protection covers what to look for and which services pass all three tests consistently.

Frequently asked questions

How can I tell if my VPN is actually working?

Run three tests: check your IP address to confirm it matches your VPN server location, run a DNS leak test to ensure DNS queries go through your VPN, and run a WebRTC leak test to verify your browser isn't exposing your real IP. If all three pass, your VPN is working correctly.

Why does my VPN show connected but my IP hasn't changed?

This can happen if the VPN connection failed silently, if you're checking your IP on a cached page, or if your VPN is using split tunneling and your browser traffic isn't going through the tunnel. Reconnect and test again in an incognito window.

Can my VPN be connected but still not protecting me?

Yes, absolutely. A VPN can establish a connection but still leak DNS queries, WebRTC data, or IPv6 traffic. The VPN app shows 'connected' because the tunnel exists, but certain types of traffic may bypass it entirely.

How do I test my VPN on my phone?

The same tests work on mobile. Connect to your VPN, then visit a DNS leak test and IP checker in your mobile browser. For Android, also check Private DNS settings. For iPhone, verify the VPN profile is active in Settings > VPN.

What is split tunneling and can it cause leaks?

Split tunneling lets you choose which apps use the VPN and which connect directly. If your browser is excluded from the VPN tunnel, all your browsing traffic — including DNS queries — will bypass the VPN. Check your VPN's split tunneling settings.

Should I test my VPN on every network I connect to?

Yes. Different networks can cause different behavior. A VPN that works perfectly on your home Wi-Fi might leak on a public hotspot or corporate network. Always re-test when switching networks.

Stop leaks for good

A VPN with private DNS on every server, a kill switch and WebRTC protection closes every leak this site tests for.

Get NordVPN →

30-day money-back guarantee · We may earn a commission