Your current public network endpoint

My IP and public network endpoint

Results come from this site’s same-origin GeoIP API to identify your current public endpoint, network provider, and proxy status. No third-party public API is used to supplement or replace the results.

Current network exit

Public IP lookup results

Checking…
IP address
Checking…
Country or region
Checking…
ISP
Checking…
Proxy detected
Checking…

Result guide

IP information: what does it mean?

A single lookup contains several layers of information. Understanding each field is more useful than simply checking whether the IP address changed.

IP

Public endpoint

Websites see the public endpoint used by your current connection, not the device’s private address on a local network. The endpoint may change when you switch routes, change network access, or reconnect.

Region

Approximate location

Country or region data is derived from IP range registrations and database mappings. It can help check whether the endpoint broadly matches the selected route. Databases may lag behind current changes, so city-level results may differ from the actual data-center location.

ISP

Network provider

The ISP field generally identifies the network operator, data center, or autonomous system associated with the address range. It can help distinguish a residential endpoint from a cloud network or route provider, but it cannot determine connection quality on its own.

Proxy

Interface detection status

Proxy detection is an auxiliary signal provided by the GeoIP data source. “Not detected” does not mean that no forwarding path exists, while “Detected” does not necessarily indicate a connection problem. Interpret it alongside whether an acceleration route is actively in use.

DNS check

DNS leak check methods

A changed public IP does not necessarily mean that DNS requests are following the expected path. A DNS check should examine the endpoint region, resolver provider, and client settings together.

  1. Confirm that the route is connected

    Confirm in the client that the current route is connected, then return to this page and run the lookup again. Note the displayed endpoint country or region for comparison.

  2. Check DNS settings in the system and client

    Check whether the client is managing DNS and whether the system network settings still contain resolvers supplied by the original network. If the client offers DNS modes, use its default recommendation where possible.

  3. Check whether the resolver location is significantly different

    Use a trusted DNS testing method to identify the resolver provider actually handling requests. If the endpoint is in the selected route region but DNS requests continue to be handled by the original network operator, review DNS management and split-routing settings.

  4. Reconnect after changing settings

    After adjusting DNS or split-routing rules, disconnect and reconnect the route, then repeat the check. Browsers and operating systems may retain DNS caches, so refreshing the current page alone may not show the change.

Start Free