EXIT ADDRESS / IP LOOKUP

Public IP Lookup

See the network exit used by your current browser request. Check again after connecting or switching routes to confirm where requests to this site are coming from.

Current connection details

VPNCD API lookup

Waiting to check your current connection.

Public IP address
Not checked yet
Country or region
Not checked yet
ISP / Network provider
Not checked yet
Proxy detected
Not checked yet

Results apply only to requests made to this site’s API. They don’t indicate whether every app on your device uses the same route.

What this information means

Public IP: the address seen by this request

The public IP is the address our API sees for this request, not usually your device’s address on the local network. Copy and compare the results before and after connecting. A change means this request is using a different exit. If the address hasn’t changed, check that your client is connected and that requests to this site aren’t set to bypass the proxy.

Location and ISP: clues to identify your connection

Location is based on IP geolocation data, not your device’s physical location. The ISP field may show an internet provider, cloud provider, or organization associated with the exit. These records can lag behind changes. If the reported location doesn’t match the route name, first check the region selected in your client, then verify using the destination service itself.

Proxy detection: an indicator, not proof of your connection

A proxy detection result means the API has marked the current IP as a proxy. No proxy detected doesn’t mean the request is definitely direct or prove anonymity. If the API doesn’t return this field, this page will show “Detection data unavailable” rather than infer a result. Destination websites may use different detection data; their own access rules determine whether a connection is allowed.

Check for DNS leaks

An IP lookup and a DNS leak check are different tests. An IP lookup shows the public exit for a request; a DNS check identifies the resolvers handling domain lookups. This page only uses our GeoIP API and does not run a DNS leak test. A location that matches your expectations does not confirm that your DNS settings are working correctly.

  1. Check your client’s DNS settings. Confirm whether its configuration handles DNS lookups and whether routing rules allow some domains to use local DNS. Keep a copy of the original settings so you can identify the cause if something goes wrong.
  2. Check your browser’s Secure DNS settings. A browser may use encrypted DNS independently, so its lookup path may differ from your client’s. Confirm the setting is what you expect, then compare the browser’s DNS behavior with your system’s.
  3. Run a dedicated DNS test while connected. If you choose an external testing tool, check its privacy policy first. This page won’t send requests to external testing services automatically. Note which resolvers the test reports and assess them against your client’s rules; don’t rely only on whether their reported location matches your exit.
  4. Review unexpected results and share relevant details. If the results don’t match your expectations, check your cache, app-specific proxy settings, and DNS routing rules. If you need help, open a support ticket in the user panel with your platform, selected region, and a description of the issue. Don’t share your subscription link publicly.

DNS resolvers may use distributed exits, so their reported location doesn’t show the full path of a DNS request. Assess possible leaks against your expected configuration and the test results; a location difference alone doesn’t mean something is wrong.

Open a support ticket

Lookup privacy

We don’t log lookups. This page uses our API to retrieve connection details for the current request and does not fall back to a third-party public API. Results are displayed only on this page. Copying happens only when you click the button, and lookup results aren’t saved in your browser’s local storage.

Network requests must send your current public IP to our API to retrieve location details. Cover your IP address and other connection details before sharing a screenshot. See our Privacy Policy for how we handle information.