Network Egress / Lookup Tool

Public IP Lookup

See the public IP address used for this browser request. After switching routes, run the lookup again to compare the results.

Lookup Results

VPNLD GeoIP API

Waiting for lookup. Results load automatically when JavaScript is enabled.

Current public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet Service Provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

The result reflects the egress route used by this request, not necessarily the route used by every app. Missing fields remain marked “Temporarily unavailable”; no values are guessed.

Understanding the Results

What the Results Mean

Your public IP, its geographic location, and the proxy indicator each answer a different question.

Public IP: the source of this request

Websites usually see your public IP address, not your device’s local network address. Run a lookup before and after connecting to see whether the address used by your browser to reach this site changes. With split tunneling enabled, requests to this site may still use your local connection, so an unchanged address doesn’t prove that your client is disconnected.

Location: an estimate from an IP database

Country and region are estimated from an IP address database, not your device’s location. IP assignments, network routing, and database updates may not align. Use this information to check an egress address’s approximate location, not your device’s actual whereabouts. A service may also determine your location differently.

ISP: details about the egress network

The ISP field shows the provider reported by the API. On an international route, it may differ from the provider for your local connection. When troubleshooting, note the IP and ISP together to help distinguish egress routes. The provider name doesn’t indicate route speed or reliability.

Proxy indicator: a detection result, not proof of your connection

Proxy detection relies on classifications provided by the API. “No proxy detected” means the API didn’t identify proxy characteristics; it doesn’t mean the request definitely used your local network. “Proxy detected” doesn’t indicate whether quantum encryption is enabled. Check your connection status and rule matches in your client.

DNS / What This Check Can’t Tell You

Check for DNS Leaks

DNS translates domain names into network addresses. Web requests and DNS queries may take different routes: a changed public IP doesn’t mean DNS queries are using the expected route. This page only calls the GeoIP API; it doesn’t run a dedicated DNS test and can’t determine whether your DNS is leaking.

  1. Confirm the expected route. Check your client’s connection mode and split-tunneling rules to see which route should handle the target app and its domains. Checking your browser’s public IP alone isn’t enough to determine how other apps resolve domains.
  2. Review your DNS settings. Check your client’s DNS interception settings, your system’s resolver settings, and your browser’s Secure DNS options. If the browser chooses its own DNS resolver, it may not follow the client’s DNS settings. Check your rules to confirm whether the route is as expected.
  3. Check your client logs. Open the target page in a new tab to generate requests, then review the rule matches for domain lookups and connections. Cached results may temporarily keep lookups from appearing in the logs. Follow your client’s instructions to clear the cache and check again; missing logs alone don’t prove a DNS leak.
  4. Distinguish access problems from DNS leaks. A page that won’t load may be caused by a DNS failure, but it could also be a route, app, or destination service issue. If you can’t confirm the route from settings or logs, save the relevant details and contact support. A single failed visit isn’t proof of a leak.

Any conclusion should be based on the actual DNS resolution path. The country / region and proxy fields on this page are not a substitute for a DNS leak test.

View Troubleshooting Guide Open a Support Ticket

Privacy Notice

How Lookup Data Is Handled

VPNLD doesn’t log lookups. Requests are handled through VPNLD’s API. If the API is unavailable, the page displays an error instead of fetching results from a third-party public API.

The copy button copies only the IP currently shown, not the other fields. Before sharing screenshots or logs, check for your public IP, account details, or subscription links. A subscription link is an account credential and shouldn’t be shared publicly as troubleshooting material.

Read the Privacy Policy