If you use a VPN on Android, it is not enough to see a “connected” status and assume everything is working.
This guide shows how to check if VPN on Android is working using simple tests that reveal IP leaks, DNS leaks, and split-tunneling issues.
What a Working Android VPN Should Do
A properly functioning VPN on Android should route your internet traffic through a remote VPN server, replace your public IP address, and encrypt data between your phone and the VPN provider.
In most cases, that means websites, apps, and network tools see the VPN server’s location instead of your real one.
On Android, a working VPN also needs to handle mobile data and Wi‑Fi consistently.
Because Android devices may switch networks, sleep in the background, or optimize battery usage aggressively, a VPN can appear active while specific traffic still bypasses it.
Quick Signs Your VPN Is Working
- The VPN app shows an active connection to a server.
- Your public IP address changes to match the VPN server location.
- Your DNS requests no longer reveal your ISP’s resolver.
- Websites and streaming services show the VPN region instead of your physical location.
- Your connection remains protected after switching from Wi‑Fi to mobile data, or after waking the phone.
These signs are helpful, but they are not enough on their own.
A reliable check requires confirming both the IP address and the DNS path.
How to Check if VPN on Android Is Working
1. Confirm the VPN connection inside Android
Open Settings and look for the VPN status icon in the notification area, then verify the active profile under Network & internet or Connections, depending on your Android version and manufacturer.
Samsung, Google Pixel, OnePlus, and Xiaomi devices may label menus differently, but the key is to confirm the VPN is actively connected and not merely configured.
If your VPN app includes a “connected” indicator, compare it with Android’s system status.
A mismatch may signal that the app thinks it is connected while the OS has dropped the tunnel.
2. Check your public IP address
The simplest real-world test is to open a browser and search for “what is my IP” or visit an IP lookup site such as WhatIsMyIPAddress, IPinfo, or similar services.
If the VPN is working, the displayed IP address should belong to the VPN provider’s network and not your internet service provider.
For a better check, compare the location shown by the IP lookup with the server location selected in your VPN app.
If you connected to a server in New York, the website should show a New York-based IP or at least a nearby region used by the provider.
- If the IP still matches your home ISP, the VPN is not routing traffic.
- If the IP changes but the location is wrong, the provider may use shared infrastructure or a nearby data center.
- If the IP changes only in the app but not in the browser, some traffic may be bypassing the tunnel.
3. Run a DNS leak test
A VPN can hide your IP address while still exposing your DNS activity.
DNS leak tests check which servers are resolving your domain requests.
If the results show your ISP, mobile carrier, or local network provider, your VPN is not fully protecting your browsing.
Use a trusted DNS leak test site and run both standard and extended tests.
A correct result should show DNS resolvers associated with the VPN provider or a privacy-focused DNS service configured through the tunnel.
Watch for these warning signs:
- Your ISP appears in the resolver list.
- The test shows your real country instead of the VPN location.
- Different DNS servers appear when switching from Wi‑Fi to 5G or LTE.
4. Verify with a WebRTC leak test
WebRTC can reveal local or public IP information in browsers that support real-time communication features.
While Android browsers are less likely than desktop browsers to leak aggressively, the test is still useful if you browse on Chrome, Firefox, or Brave.
Search for a WebRTC leak test and compare the addresses shown.
If the page exposes your real public IP or local network information while the VPN is connected, the browser may be leaking data outside the tunnel.
5. Test on both Wi‑Fi and mobile data
Many VPN issues only appear when Android changes networks.
Connect to Wi‑Fi, confirm the VPN works, then switch to cellular data and repeat the same IP and DNS checks.
A strong VPN setup should maintain the tunnel during the transition or reconnect immediately without exposing your real IP.
This is especially important on devices with battery optimization features that restrict background apps.
Some phones pause VPN apps when the screen is off, which can create short unprotected windows.
Use the VPN App’s Built-In Diagnostics
Most reputable providers such as Proton VPN, NordVPN, ExpressVPN, Surfshark, and Private Internet Access include status details, server health indicators, or connection logs.
These tools can help you identify whether the tunnel is active, which protocol is in use, and whether the app detected packet loss or reconnect events.
- Protocol: WireGuard, OpenVPN, or IKEv2 usually performs better and is easier to verify than unstable custom setups.
- Kill switch: Confirms that traffic stops if the VPN drops, reducing exposure.
- Split tunneling: May intentionally exclude certain apps, so not all traffic will appear routed through the VPN.
If split tunneling is enabled, some apps may still show your real IP by design.
That is not necessarily a failure, but it should match your intended configuration.
Common Reasons an Android VPN Appears Connected but Is Not Working
Sometimes the VPN icon is active while traffic still leaks outside the tunnel.
Common causes include expired subscriptions, app crashes, outdated Android network permissions, or aggressive battery optimization.
Router-level restrictions, captive portals on public Wi‑Fi, and unstable mobile signals can also interrupt tunneling.
Another frequent issue is private DNS.
Android’s Private DNS feature can conflict with some VPN setups if the provider does not support it correctly.
If DNS leak tests look wrong, check whether a custom DNS setting is overriding the VPN’s resolver path.
Android Settings That Can Interfere with VPN Testing
- Battery optimization: May stop the VPN app in the background.
- Always-on VPN: Helps keep traffic protected after drops.
- Block connections without VPN: Forces all traffic through the tunnel.
- Private DNS: Can change how DNS lookups behave.
- Data saver modes: May limit background network activity.
To reduce false results, temporarily disable battery restrictions for the VPN app while testing.
On many Android devices, you can find this under Battery, App battery usage, or Optimized app settings.
A Simple Verification Checklist
- Connect to a VPN server in a known location.
- Confirm the VPN is active in Android settings and the app.
- Check your public IP address in a browser.
- Run a DNS leak test and compare resolver locations.
- Repeat the same tests on Wi‑Fi and mobile data.
- Optionally run a WebRTC leak test in your browser.
- Verify the result again after screen lock, app switching, and airplane mode toggles.
If all tests point to the VPN server and no leaks appear, your Android VPN is working as expected.
If any result shows your ISP, home location, or real DNS resolver, revisit your app settings, protocol selection, and Android battery permissions before relying on the connection.
What to Check When You Need Stronger Privacy
For higher-risk use cases, go beyond basic IP checks.
Review whether the provider publishes independent audits, supports WireGuard, offers a kill switch on Android, and clearly documents DNS handling.
Also confirm whether the app supports per-app routing, split tunneling controls, and automatic reconnect behavior after network changes.
If privacy is the priority, test your VPN regularly rather than once.
Android updates, app updates, and carrier network changes can alter how traffic behaves over time, so periodic verification is the most reliable way to stay protected.