Is Your VPN Actually Working? The 2-Minute Test (4 Checks, No Tech Skills)
Published July 3, 2026 · 2:03 · vpnrank.io editorial team
A VPN that says “connected” is not automatically protecting you. This two-minute video walks through the four checks that prove it — an IP address check, a DNS leak test, a WebRTC leak test and a kill-switch test — all using free browser tools and requiring no technical skills.
What you'll learn in this video
- Why “connected” doesn't mean “protected”
- How to confirm your IP address and location actually change
- How to run a DNS leak test and read the results
- The WebRTC leak — how your browser can expose your real IP even with the VPN on
- How to test your kill switch by briefly cutting the Wi-Fi
- What to do if your VPN fails any of the four tests
Full video transcript
The complete narration of the video, section by section, with timestamps.
Why “connected” doesn't mean “protected” (0:00)
Your VPN says it's connected. But is it actually protecting you? In the next two minutes, you'll run four quick tests that prove it — no technical skills needed. Let's go.
Test 1 — the IP address check (0:12)
Test one: your IP address. Before you connect the VPN, search “what is my IP” and write down what you see. Now connect the VPN and check again. If the IP address and the location both changed, you're passing test one. If it still shows your real city — your VPN isn't doing anything at all.
Test 2 — the DNS leak test (0:34)
Test two: DNS leaks. A VPN can hide your IP and still leak every website you visit through DNS requests. Run a DNS leak test and choose the extended option. Every server in the results should belong to your VPN provider. If your home internet provider shows up in that list — that's a leak, and it needs fixing.
Test 3 — the WebRTC leak, the sneaky one (0:57)
Test three: WebRTC. This is the sneaky one. Your browser itself can reveal your real IP address, even while the VPN is on. Open a WebRTC leak test page and look carefully. If your real IP appears anywhere on that page, turn on WebRTC protection in your VPN app — or disable WebRTC in your browser.
Test 4 — the kill switch (1:21)
Test four: the kill switch. While the VPN is connected, switch your Wi-Fi off for a few seconds, then back on. A good VPN freezes all traffic until the secure tunnel is restored. If pages kept loading during that gap, your real IP was exposed. Make sure the kill switch is enabled in your VPN's settings.
What to do if you failed a test (1:44)
Passed all four? You're solid. Failed any of them? It might be time to switch providers. At vpnrank.io we run speed tests and track live VPN prices every single day, so the rankings are never stale. You'll find the full comparison in the description below. See you there.
Beyond the video
Extra context from our written guides that didn't fit in 2:03 of video.
The tools used in the video (all free, no signup)
Every check in the video runs in an ordinary browser tab — and we now host free versions of them right here on vpnrank.io. The IP check is our What Is My IP tool at vpnrank.io/tools/what-is-my-ip: what matters is comparing the location before and after you connect, and our Is My VPN Working test at vpnrank.io/tools/is-my-vpn-working automates that comparison. The DNS check is any extended DNS leak test, which sends several rounds of DNS queries and lists every server that answered. You are not looking for a specific company name in the results — you are looking for the absence of your own internet provider. If your ISP answers your DNS queries while the VPN is on, websites you visit are being resolved outside the tunnel, and your browsing history is visible to the ISP even though your IP is hidden.
The WebRTC check is our free test at vpnrank.io/tools/webrtc-leak-test. WebRTC is the browser technology behind in-browser video calls, and it can be tricked into revealing your device's real addresses through a side channel the VPN tunnel never sees. That is why it deserves its own test: your IP check can pass while WebRTC still gives you away. Most good VPN apps and browser extensions now ship WebRTC leak protection, but it is frequently off by default.
How often should you re-run these tests?
Once is not enough, because leaks are usually introduced by change. Re-run the four checks after a VPN app update, after switching protocol (say from OpenVPN to WireGuard), after installing a new browser or browser profile, and whenever you join a network you don't control — hotels and airports are exactly where a silent failure costs you the most. The whole routine takes about two minutes once you've done it twice, which is the point of the video: make verification a habit, not a project.
It's also worth re-testing per device. A VPN configured perfectly on your laptop says nothing about the same account on your phone, where the kill switch and auto-connect options live in a different place and default to different values.
What a failed test actually means — and the fix
A failed IP check means the tunnel isn't up at all: reconnect, switch servers, or reinstall the app before assuming anything worse. A failed DNS test usually means the app isn't forcing its own DNS servers — look for a “DNS leak protection” toggle, and flush your system's DNS cache after enabling it. A failed WebRTC test is fixed in the VPN app's settings or, more bluntly, by disabling WebRTC in your browser. A failed kill-switch test means the feature is off or absent — turn it on, and if your provider doesn't offer one, that alone is a reason to move on.
If the same test keeps failing after the fixes, the honest conclusion is that the provider — not your setup — is the problem. Every premium VPN we rank comes with a 30-day money-back guarantee, so switching to one that passes all four checks costs nothing to try. Our rankings are re-tested continuously, with speed data and live prices updated daily.
The four tests at a glance
Test one, the IP check, proves the tunnel exists: a “what is my IP” page (ours is at vpnrank.io/tools/what-is-my-ip) must show the VPN server's location, not your city, and the before/after comparison is the whole method. Test two, an extended DNS leak test, proves your lookups travel inside the tunnel: the pass condition is that your own internet provider appears nowhere in the results. Test three, the WebRTC check at vpnrank.io/tools/webrtc-leak-test, proves your browser isn't bypassing the tunnel: your real IP must not appear anywhere on the page. Test four, the kill switch, proves the failure mode is safe: cut the Wi-Fi for a few seconds mid-connection (or use our monitor at vpnrank.io/tools/vpn-kill-switch-test), and nothing should load until the tunnel is back.
Notice what the four tests have in common: none of them trusts the VPN app's own status indicator. The green “connected” badge reports that a tunnel was negotiated — it says nothing about DNS routing, browser side channels, or what happens during a drop. Independent verification outside the VPN app is the only version of “it works” that counts, and it is deliberately the same standard we apply in our own reviews.
Related Guides
Everything in this video is grounded in our own testing — speed runs, streaming checks and live prices, updated continuously.
See the VPNs we actually tested →