How to Check Your VPN Is Actually Working
To verify your VPN is working: visit ipleak.net or browserleaks.com and confirm your IP has changed to the VPN server's IP. Check DNS is not leaking your real ISP. Open a real app that you use — not just a browser tab.
Step 1
Visit ipleak.net in a browser and confirm the IP matches the VPN server location.
Step 2
Switch to TUN mode if testing in proxy mode — ensures all apps route through the VPN.
Step 3
Check DNS results on ipleak.net match the VPN server, not your ISP.
- The issue no longer reproduces in the network where you noticed it.
- Your critical service or workflow behaves consistently after the re-check.
- You know what context to send to support if the issue comes back.
- IP does not change even after re-importing config and reconnecting.
- DNS is leaking to your ISP despite VPN showing as connected.
- Apps that need to work through the VPN consistently fail even in TUN mode.
- Screenshot or results from ipleak.net.
- Client mode (proxy or TUN).
- Which apps are not working through the VPN.
- Device, OS and client version.
- On iPhone: iOS routes all traffic through VPN by default when the profile is active.
- On Android: in proxy mode, some apps bypass the proxy. Switch to VPN mode in the client.
- On Windows/macOS: TUN mode is required for full-device coverage — enable it in client settings.
How to recognize this issue
This issue usually appears through one or more of the following symptoms.
- VPN shows as connected but you are unsure if traffic is actually routing through it.
- Some apps seem to work normally, others appear to have no connection.
- IP check tool shows a different location than the VPN server.
Most common causes
Proxy mode selected instead of TUN mode — some apps bypass proxy settings.
Split tunnelling configured to exclude the app you are testing.
DNS leak — traffic routes through VPN but DNS queries still go to your ISP.
VPN connected but specific services are geo-blocked at the application level.
First checks
Start with the cheapest checks before changing everything at once.
- Visit ipleak.net in a browser and confirm the IP matches the VPN server location.
- Switch to TUN mode if testing in proxy mode — ensures all apps route through the VPN.
- Check DNS results on ipleak.net match the VPN server, not your ISP.
Diagnostic flow
If the fast checks did not help, localize the problem step by step.
- Open ipleak.net and note the displayed IP address and DNS servers.
- If the IP has not changed, the VPN is not routing your browser traffic — re-import config and reconnect.
- If the IP changed but specific apps still do not work, switch to TUN mode.
- Test the actual apps you need: email, work tools, messaging — not just the browser.
Device-specific notes
On iPhone: iOS routes all traffic through VPN by default when the profile is active.
On Android: in proxy mode, some apps bypass the proxy. Switch to VPN mode in the client.
On Windows/macOS: TUN mode is required for full-device coverage — enable it in client settings.
When to escalate to support
IP does not change even after re-importing config and reconnecting.
DNS is leaking to your ISP despite VPN showing as connected.
Apps that need to work through the VPN consistently fail even in TUN mode.
What to send to support
The more precise the context, the faster support can help.
- Screenshot or results from ipleak.net.
- Client mode (proxy or TUN).
- Which apps are not working through the VPN.
- Device, OS and client version.
Continue with the next logical step
The actions below follow the page intent: start with the primary next step, then use setup, support, or the travel checker if needed.
Frequently asked questions
The VPN client may have connected but failed to route traffic. Re-import the config and reconnect. Check TUN mode is enabled if you are in proxy mode.
A DNS leak means your DNS queries go to your ISP even though other traffic routes through the VPN. Your ISP can see which domains you visit. TUN mode typically prevents DNS leaks.
Streaming apps sometimes use hard-coded DNS or IP detection methods that bypass the VPN at the application layer. Contact support for which server currently works with that service.
It is a standard privacy tool. For verification purposes it is fine — it shows your public IP and DNS servers without collecting your data.