Seeing “connected” in a VPN app is a good start, but it is not a complete privacy test. A leak test checks whether your normal IP address or DNS requests are visible outside the encrypted connection.
You do not need to be an expert to run one. The key is to record what your connection looks like before you connect, then compare it with what a testing site reports after the VPN is active.
Before you test
Write down your normal location and internet provider. Disconnect the VPN, open a reputable IP or DNS leak-testing service in your browser, and note the visible IP address and country. Then close the browser tabs, connect your VPN, and run the same checks again.
If the VPN app includes a kill switch, turn it on before testing. The kill switch is designed to help prevent traffic from leaving outside the VPN tunnel if the VPN connection drops.
Also Read: https://vpnkeen.com/blog/vpn-free-class-action-claims-explained/
Test 1: Check your public IP address
With the VPN connected, an IP-checking service should show the IP address and general region associated with the VPN server, not your original home or mobile connection.
If it still shows your usual provider or approximate home region while you are connected to a different VPN location, disconnect and reconnect. Check whether the app is actually connected and whether another network or browser extension is interfering.
Test 2: Check DNS requests
DNS converts website names into internet addresses. A DNS leak can happen when your device sends DNS queries outside the VPN tunnel, potentially exposing the DNS service used by your normal internet connection.
Run an extended DNS test with the VPN connected. Look for results that match the VPN connection rather than your regular internet provider. One result does not always mean a leak; some networks use third-party DNS infrastructure. What matters is whether the results reveal your usual local provider or location unexpectedly.
Read more about leak and DNS protection before changing settings.
Test 3: Check WebRTC behavior
WebRTC is a browser technology used for real-time voice, video, and peer-to-peer connections. In some configurations, WebRTC can expose network information to websites. Run a WebRTC leak test in each browser you use, because browser settings and extensions can produce different results.
If a result exposes a local network address, that is not always the same as exposing your public IP. Still, it is worth reviewing the tester's explanation and checking your browser's privacy settings. Do not install an unknown extension simply because it claims to fix WebRTC leaks.
What to do if a test looks wrong
1. Disconnect and reconnect to the VPN.
2. Update the VPN app, browser, and operating system.
3. Confirm that leak protection and the kill switch are enabled where supported.
4. Test another server location.
5. Disable unneeded proxy settings or browser extensions temporarily.
6. Retest in a second browser.
7. Contact support with screenshots, device/OS, app version, selected server location, and test time.
FAQ
What is a DNS leak?
A DNS leak happens when DNS requests use a service outside the VPN tunnel, potentially revealing information about the network you normally use.
Is a local IP address in a WebRTC test always dangerous?
Not necessarily. A local IP address is different from your public IP address. Check the test explanation and focus on whether your original public IP or usual DNS provider is unexpectedly exposed.
How often should I test my VPN connection?
Test after setting up the VPN, after major app or operating-system updates, and whenever you notice unusual disconnects or routing behavior.
Suggested related links:
https://vpnkeen.com/leak-protection.html
https://vpnkeen.com/transfer
https://vpnkeen.com/privacy.html
