Current browser · Exit information

VPNXG IP Lookup

See the exit IP used for this request. After switching routes, check again to see whether its reported location has changed.

Exit lookup results

Our endpoint

No lookup yet. Enable JavaScript to retrieve your current exit information.

Exit IP
Temporarily unavailable
Country / region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

These results apply only to the connection your browser uses to reach our endpoint. They don’t represent the routes used by other apps or all network requests.

What this information means

Exit IP and location

The exit IP is the address our endpoint sees as the source of your request. It’s usually different from your device’s address on the local network. If your browser’s request to this site goes through a selected route while the client is connected, the result may show that route’s exit IP. If your split-tunneling rules send this site’s traffic directly, the result may still show your local network’s public IP.

Country and region are based on IP geolocation databases, not your device’s precise location. Changes to IP address allocations, database update schedules, and how ISPs register addresses can all cause results to differ from the region shown by your client. A location label alone can’t tell you whether your connection is working properly.

ISP and proxy detection

The ISP field shows the network provider or organization reported by the endpoint. This could be your local access provider or the data center hosting the exit IP. It won’t necessarily match the brand of the subscription service you’re using.

Proxy detection classifies the exit IP reported by the endpoint; it doesn’t scan your entire device for security issues. “No proxy detected” doesn’t mean you aren’t using a proxy, and “Proxy detected” doesn’t mean your connection has a problem. If the endpoint doesn’t return a clear result, this page will show “Temporarily unavailable” rather than infer an answer from other fields.

DNS leak checks

DNS translates domain names into network addresses. Web requests and DNS lookups can take different routes, so a changed exit IP alone doesn’t prove that DNS is using the expected route. This page’s IP lookup endpoint doesn’t test DNS resolvers, so it can’t determine whether a leak has or hasn’t occurred.

  1. Confirm your expected route. Check whether your client is set to global proxy, rule-based routing, or proxying for specific apps only, and review its DNS settings. With rule-based routing, resolving some domains locally may be intentional.
  2. Check your browser settings. See whether secure DNS is configured separately from your operating system. A resolver selected by the browser can behave differently from the one used by your client or other apps.
  3. Compare before and after connecting. If you need to investigate further, choose a DNS testing tool you trust and compare the reported resolvers under the same settings, both before and after connecting. You must start this test yourself; this page won’t send requests to third-party testing services automatically.
  4. Check the logs. Review your client’s local diagnostic information for its DNS mode and which routing rules were matched. A difference between the resolver’s name and the exit region isn’t enough to establish a leak. First confirm that DNS queries followed the route you expected.

For help importing a profile and connecting, read the Quick Start Guide. To understand protocol differences and the distinction between direct and relayed connections, see Protocol Guide.

First Month Free