How to Verify Your VPN Is Working: Check Your Exit IP and DNS

Learn how to check your public IP, test for DNS leaks, and verify apps one by one. Find out why a connection may look active even when traffic isn’t using the VPN, and how to troubleshoot it.

How can you tell if your VPN is really working? Check your public IP before and after connecting on the same network, then test DNS and confirm that the app you’re using follows the expected route. A client showing “Connected” doesn’t mean all traffic from your device has a new exit IP. First, clarify your goal: should only one app use the proxy, or should all system traffic go through the tunnel? The right result depends on which you expect.

Check Your Exit IP Before and After Connecting

Your public IP is the address a lookup site sees as the source of your request. It’s not the local address your router assigns to your device. Choose a reputable public IP lookup site, and keep the device, browser, and network the same throughout the comparison. If you record a result on Wi-Fi and then switch networks before testing the connection, you won’t know what changed your exit IP.

  1. Record your direct-connection baseline. On a network where direct-connection testing is allowed, disconnect the VPN, open the lookup site in your browser, and note your public IPv4 or IPv6 address. If your device is required to stay on a managed tunnel, skip disconnecting and ask your administrator which exit IP to expect.
  2. Make a fresh request after connecting. Choose a route, open a new tab, and reload the lookup site rather than relying on an old result in an existing tab. If you can test both IPv4 and IPv6, compare them separately. A changed IPv4 address doesn’t mean IPv6 is using the same route.
  3. Check which rule matched the request. If the lookup site is set to connect directly under your current rules, an unchanged address is expected. First, check whether the client provides connection logs, then look up the actual outbound route for the site’s domain. If there are no logs, you can briefly switch to a global proxy rule for comparison in an environment where that’s allowed, then restore your original settings.

Global proxy rules control how requests handled by the client are routed; they may not capture traffic from every app. Another clue that can be misleading is the location associated with an IP address: if the IP changes but the city or route label doesn’t match, the difference may be down to the geolocation database. Check the address and connection logs first, and use city labels only as a supporting clue.

Check DNS: Find Out Which Route Resolves Your Queries

DNS translates domain names into IP addresses. Web requests and DNS lookups don’t always use the same route: your web traffic may use a new exit IP while lookups still follow your system’s original settings. Browsers may also use their own encrypted DNS, separate from the resolver used by other apps.

Run a reputable DNS test in the same browser before and after connecting. These tests usually have your browser look up temporary test domains, then list the recursive resolvers based on the queries they receive. Compare resolver addresses and networks, not just their locations on a map. If DNS is expected to go through the tunnel but you keep seeing resolvers from your original network provider, check whether some requests are still using the original DNS route. If the same public DNS provider appears both times, that alone neither proves a leak nor confirms that queries went through the tunnel.

Troubleshoot Connection and Routing Issues

It looks connected, but where might traffic actually be going?
What you see Check first How to verify
Public IP hasn’t changed The lookup domain may match a direct-connection rule, or the browser may not be using the current proxy. Check the client’s connection logs, then test a request that should clearly use the proxy.
IPv4 changed, but IPv6 didn’t Check whether the current mode handles IPv6 and whether the original network’s IPv6 route is still in use. Retest with a site that checks each address type separately, then review the client’s routing settings.
Exit IP changed, but DNS results didn’t Check the browser’s encrypted DNS, system DNS settings, and the client’s DNS policy. Retest with a fresh test domain. If the client provides DNS logs, check which route the lookup actually used.
Browser works, but desktop app doesn’t Check whether the app follows the system proxy, has its own proxy settings, or is reusing an existing connection. Fully quit and reopen the app, then compare a new action with the client’s connection logs.
Exit IP changed, but the site still says it’s unavailable Check whether the message points to account region, a server-side access restriction, or a connection error. First confirm that the request reached the site. Then troubleshoot the specific error rather than assuming every message is caused by the route.

A system proxy usually works only with apps that follow the relevant settings; some apps manage their own network connections. Modes that support a virtual network adapter can route more traffic through the system, but direct-connection rules or address ranges may still apply. If you’re not sure which mode is active, start with the client setup guide. Avoid changing the route, rules, and traffic-capture mode all at once while troubleshooting.

Test Each App You Actually Use

A browser lookup only confirms the route your browser uses to reach that lookup site. To test a streaming client or desktop AI tool, quit and reopen the app, then trigger an action that clearly requires a network connection, such as refreshing a list that isn’t cached. If the client shows the process, destination domain, or route, compare its logs with the time of the action. Without those logs, you can confirm whether the action succeeded, but success alone doesn’t reveal the app’s exit IP.

  • ✅ Browser: Confirm that a fresh request uses the expected exit IP, and check that DNS results match the current DNS policy.
  • ✅ Desktop apps: Check sign-in and content loading separately. They may contact different domains and match different rules.
  • ✅ Restore your usual settings: If you temporarily changed a rule or mode, restore it and repeat the test action so you don’t mistake test settings for your everyday results.

If the issue only appears after waking from sleep or switching networks, repeat the comparison after it happens. The client may still show a connected status even though the app needs to establish a new connection. If you still can’t pinpoint the cause, check the troubleshooting guidance on the support page and include your platform, traffic-capture mode, affected app, and the time of the error. Before sharing screenshots, hide account details and subscription links; leave only the error and rule names needed to explain the issue.

What counts as working: Requests expected to use the proxy follow the selected route, DNS lookups match the expected policy, and fresh requests from the target app have been verified. Traffic expected to connect directly using its original exit IP means the routing rules are working—not that the connection has failed.

First Month Free