Your VPN is working if websites see the VPN server’s IP address, your DNS requests stay inside the VPN tunnel, and your real IP does not return when the VPN disconnects. A VPN should encrypt traffic between your device and the VPN server, which is the basic privacy function described by Google [source: Google]. The good news: you can test the essentials in a few minutes. The annoying news: one “Connected” badge in your VPN app proves almost nothing.
TLDR: Connect to your VPN, search “what is my IP,” and confirm the location matches the VPN server, not your real city. Then run a DNS leak test and a WebRTC leak test; if either shows your internet provider or home IP, something is wrong. For example, if you live in Boston and connect to a VPN server in Amsterdam, every test should show the Netherlands, not Massachusetts. A solid 5-minute check should include 3 tests: IP address, DNS leaks, and kill switch behavior.
Table of Contents
1. Check Your Public IP Address First
The fastest test is also the most obvious. Before turning on your VPN, search for “what is my IP” or use an IP lookup site. Write down the IP address and location. Then connect your VPN to a server in another city or country and check again.
If the VPN works, the result should change. Your real IP should disappear. The new IP should match the VPN server location, at least roughly. If you chose Paris, seeing France is fine. Seeing your actual town is not.
- Good result: Your IP changes and the location matches the VPN server.
- Bad result: Your original IP still appears.
- Suspicious result: The IP changes, but the VPN app says Canada while the lookup shows your real country.
Do not panic if the city is slightly wrong. IP databases are not perfect. A VPN server in New York may appear as New Jersey. That is normal. What matters is whether your real residential IP is hidden.
2. Run a DNS Leak Test
DNS is the system that turns website names into IP addresses. When you visit a site, your device asks a DNS server where to go. If your VPN is working properly, those DNS requests should go through the VPN or through privacy-safe DNS servers controlled by the VPN provider.
A DNS leak happens when your browser traffic goes through the VPN, but your DNS requests still go to your internet provider. That means your ISP may not see the full content of encrypted sites, but it can still see the domains you request. Honestly, it feels like locking the front door while leaving a side window open.
To test it, connect to your VPN and use a DNS leak testing website. Run the standard test first. If available, run the extended test too. Look at the servers listed in the result.
- If the results show your VPN provider, that is usually good.
- If they show Cloudflare, Google, Quad9, or another DNS provider you selected yourself, that may be fine.
- If they show your home internet provider, your VPN may be leaking DNS.
If you find a leak, open your VPN app settings. Look for options such as DNS leak protection, use VPN DNS, or block outside DNS. Turn them on. Then restart the VPN and test again.
3. Test for WebRTC Leaks
WebRTC is a browser feature used for video calls, voice chat, and peer-to-peer connections. It can sometimes reveal your real IP address, even when a VPN is active. This problem is more common in browsers than in apps.
Run a WebRTC leak test while connected to the VPN. The result should not show your real public IP. If it does, your browser is leaking information outside the VPN tunnel.
You can reduce the risk by doing one or more of these:
- Disable WebRTC in your browser settings, if the browser allows it.
- Use a trusted browser extension that blocks WebRTC leaks.
- Switch to a browser with stronger privacy controls.
- Check whether your VPN app includes WebRTC leak protection.
The Electronic Frontier Foundation has long warned that browsers can expose identifying data through fingerprinting and related tracking methods [source: EFF]. WebRTC is one more reason not to trust a VPN connection blindly.
4. Check the Kill Switch
A kill switch blocks internet access if the VPN connection drops. This matters more than people think. Wi-Fi hiccups. Laptops wake from sleep. Mobile devices switch from Wi-Fi to cellular data. Without a kill switch, your real IP may flash online during those tiny gaps.
Here is a simple test:
- Connect to your VPN.
- Open a page that refreshes your IP address.
- Start a download or stream a video.
- Manually disconnect the VPN from inside the app.
- Watch what happens to your internet connection.
If the kill switch works, your internet should stop until the VPN reconnects or until you allow normal traffic again. If the video keeps playing and your real IP appears, the kill switch failed or is turned off.
Expect to waste time here with some VPN apps. A few bury the kill switch under “advanced protection,” “network lock,” or some vague label that adds 30 seconds of menu hunting for no good reason. Still, find it. Turn it on.
5. Test IPv6 Protection
Many VPN problems come from IPv6. Some VPNs handle IPv4 traffic well but ignore IPv6 traffic. If your home network uses IPv6 and your VPN does not protect it, websites may still see your real connection details.
Run an IPv6 leak test while connected to the VPN. If the test shows no IPv6 address, that is usually safe. If it shows your real IPv6 address, you have a leak.
Fixes vary. Your VPN may have an IPv6 leak protection setting. If not, you may need to disable IPv6 on your device or router. That sounds clunky, but it can be effective.
6. Confirm the VPN Works on the Right Apps
Do not only test your browser. Some VPNs have split tunneling, which allows certain apps to bypass the VPN. That can be useful for banking apps or local printers, but it can also create surprises.
Check your VPN’s split tunneling settings. Make sure the apps you care about are covered. If you use torrent software, messaging apps, game launchers, or remote work tools, test them separately. The browser test does not prove every app is protected.
7. Try a Geo Location Test
Geo location checks are not perfect, but they are useful. Connect to a VPN server in another country, then open a site that changes content by region. A search engine, news site, or streaming service can show whether your apparent location changed.
If you connect to a Japanese server and still get local search results from your home city, something may be off. Browser cookies and account settings can also affect this, so test in a private window. Clear location permissions too.
8. Measure Speed, but Do Not Obsess Over It
A working VPN often lowers speed. That is normal because traffic travels through an extra server and gets encrypted. What you want to avoid is a huge drop that makes the VPN unusable.
Run a speed test with the VPN off. Then run it with the VPN on. Test nearby and distant servers. A nearby server should usually be faster. If your speed drops from 300 Mbps to 12 Mbps on every server, try switching protocols. WireGuard-based options are often faster than older protocols.
Quick Checklist
- IP address changed: Your real IP is hidden.
- DNS test passed: Your ISP is not handling DNS requests.
- WebRTC test passed: Your browser is not exposing your real IP.
- Kill switch works: Traffic stops if the VPN drops.
- IPv6 is protected: No hidden IPv6 leak appears.
- Apps are covered: Split tunneling is set correctly.
If your VPN fails one test, do not ignore it. Change servers, switch protocols, update the app, and enable leak protection. Then test again. A VPN is only useful when it protects you during normal browsing and during messy moments like dropped Wi-Fi, browser quirks, and app updates.