A connected VPN isn't always a working VPN. Leaks happen: your real IP slips through DNS, WebRTC exposes it via the browser, or the kill switch silently fails. Here's a four-step verification you should run every time you install or update a VPN.

Step 1: IP change check

Before connecting the VPN, open our IP checker and note your real IP and city. Connect the VPN. Reload the page. The IP and country/city should both change. If only the IP changes but the city still matches home, the VPN is lying about the server location.

Step 2: DNS leak test

Your browser asks DNS servers to translate domain names to IPs. If the VPN isn't forcing DNS through its tunnel, your ISP's DNS still sees every site you visit. Test at dnsleaktest.com → Extended Test. Every server returned should belong to the VPN, not your ISP. See why VPNs leak DNS for fixes.

Step 3: WebRTC leak check

WebRTC is a browser feature that can reveal your real local and public IP even through a VPN. Run our WebRTC leak check. If your real IP shows up, disable WebRTC or install an extension that blocks it.

Step 4: Kill switch test

Start a large download. Force-kill the VPN app (Task Manager / Activity Monitor). If the download keeps going, your kill switch is off or broken — your traffic just started flowing unprotected. A working kill switch drops all internet the instant the VPN disconnects. Enable it in the VPN settings.

Quick recap

• Public IP changed? ✓
• Location changed? ✓
• DNS belongs to VPN? ✓
• WebRTC not leaking? ✓
• Kill switch actually cuts traffic? ✓

All five green = you're protected. Any red = fix it before it matters.

Try it now

Curious what your IP is showing the world right now? Check your IP address & location instantly with our free tool — no signup, nothing stored. Or trace any other IP to see its geolocation, ISP, and network details.