How to Check Whether Your VPN Is Working: Public IP, DNS, and App Routing

A connected status doesn’t guarantee your traffic is routed through the VPN. Check your public IP, test for DNS leaks, verify apps individually, and troubleshoot common routing issues.

How can you tell if your VPN is working? Compare your public IP before and after connecting, check which resolver handles your DNS queries, then make a fresh request from the app you actually want to use. The goal isn’t to change every address: traffic meant for the VPN should use it, while traffic set to connect directly should follow the rules.

Check your public IP: Establish a baseline before connecting

Your public IP is the address remote websites can see—not the local address shown in your system’s network settings. Keep the device, network, browser, and IP-checking site the same throughout the test. Pause sensitive activity such as online banking and syncing, then disconnect the VPN client for comparison. If your device is managed under a workplace network policy, don’t disable mandatory protection to establish a baseline; ask your administrator what egress address to expect.

  1. While disconnected, visit a trusted public IP-checking site and note the address and network operator it reports. If it checks IPv4 and IPv6 separately, record each result; mark an address family as untested if the site can’t detect it.
  2. Connect to your chosen route and check whether the client is in rule-based or global mode. Refresh the IP-checking page to send a new request. If the result looks off, fully quit and reopen the browser so an existing connection doesn’t skew the test.
  3. Compare the results and check the client’s connection log to see whether the site was assigned to the expected route. If a direct-connection rule applies to the site, an unchanged address is normal. Instead, check a destination that should use the VPN, or briefly switch modes for comparison if permitted.

A changed address only shows that the egress address for that particular request changed. A browser proxy extension or another network service on your system could also affect the result. If the address matches expectations but the location label differs from the route name, check the network operator and client logs first. Geolocation databases can be out of date, so a city label alone doesn’t prove you’re connected to the wrong route.

Check for DNS leaks: Make sure DNS resolution follows the expected path

DNS resolves domain names to IP addresses. The route used to load a webpage and the resolver handling its domain lookup are two separate things. If an app’s domain lookups should use a specific resolver, but a test shows they’re going to a network resolver that shouldn’t handle them, investigate a DNS leak. Conversely, sending local network domains to a local resolver under an explicit rule isn’t automatically a leak.

Use a trusted DNS leak test to compare results before and after connecting. These sites typically ask your browser to look up temporary test domains, then report the recursive resolvers visible to the domains’ authoritative servers. Before testing, note whether Secure DNS is enabled in your browser and whether the client handles DNS. Run a fresh test after connecting; don’t treat results left on a previously loaded page as new.

If you still see your original network’s resolver after connecting, first check whether the test domain matches a direct-connection rule. Then check your browser’s Secure DNS provider and the client’s DNS policy. Change one setting at a time, rerun the test, and record the result. Don’t disable split DNS required for company domains just to make the report show a particular resolver name; internal services may become inaccessible.

Check apps individually: A working browser doesn’t mean desktop apps are covered

With system proxy settings alone, usually only apps that follow those settings use the proxy. A browser extension may cover even less, affecting only that browser. Tunnel mode can capture more system traffic, but apps may still be excluded, destinations may have exceptions, or some address families may not be included. Check the setup method for your platform in the setup guide, then test according to the mode you’re using. Don’t infer actual coverage from the mode’s name.

  • ✅ Browser: Make a fresh request using your usual browser setup, note the time, and check the client log to confirm that the same destination matched the expected rule. If the browser has a separate proxy extension, you can disable it temporarily for comparison if permitted.
  • ✅ Desktop app: Fully quit and reopen it, then trigger a recognizable network action, such as a manual sync. Check the connection log by time and destination. If the app or a managed server can report the source address, compare it with the expected egress address.
  • ✅ Direct-connection exception: Choose a destination that should connect directly, such as an allowed local network service, and confirm it still works over its usual route. This helps ensure you haven’t routed all traffic through the VPN just to get one app working.
  • ❌ Don’t use one app’s results to stand in for another. A changed browser IP doesn’t prove background syncing uses the VPN. If there’s no entry in the client log, the log may simply not record that type of connection.

If an app connects to separate login, update, and content services, don’t just check whether its main screen opens. If the client lets you inspect logs by destination, reproduce the failing action and find the corresponding connection. A successful login only proves the login request got through; it doesn’t mean content requests matched the same rule.

Connected, but traffic isn’t using the VPN: Troubleshoot by symptom

What you seeCheck firstHow to verify
Public IP is unchangedCheck whether the destination matches a direct-connection rule and whether the app uses the proxy provided by the client.Review the rule match for the destination, then make a fresh request to a destination that should use the VPN.
IPv4 changed, but IPv6 still uses the original routeCheck whether the client handles IPv6 and whether there are exceptions for that address family.Test both address families separately. If both are expected to be protected, don’t treat an IPv4-only result as a pass.
Browser works, but a desktop app doesn’tCheck the app’s own proxy settings, app exclusions, and whether it’s reusing an existing connection.Fully quit and restart the app, repeat the failing action, and check the new connection log.
Egress matches expectations, but DNS results look wrongCheck whether Secure DNS in the browser, system DNS settings, and the client’s DNS rules are consistent.Compare the settings one by one and run the test again. Record changes in DNS resolver egress separately from changes in webpage egress.

If your egress, DNS, and routing rules all look right but one site still won’t load, don’t keep reinstalling the client. First identify whether DNS resolution failed, the connection timed out, or the site returned a login or access restriction message. The last case means you received a response from the remote site, but it doesn’t tell you whether your account has permission or whether the site supports that egress address. If you need help, use the contact page and include your system, client mode, destination domain, error time, and redacted routing logs. Don’t share subscription links, credentials, or complete logs.

What counts as a pass: A fresh request from the target app matches the expected rule, the visible egress matches expectations, and DNS resolution follows your configuration. If you tested only a browser, your conclusion applies only to that browser request. After changing networks or modes, retest the apps that matter most.

Get Started Free