Same-Origin Network Diagnostics

Public IP Check

See the address, location, and network provider information presented to external services by your current connection. Results come from this site’s same-origin API and can help confirm whether a route change has taken effect.

No third-party lookup services Lookup results are not stored

CURRENT EGRESS

Current lookup result

Checking
Public IP
Fetching
Location
Fetching
ISP
Fetching
Proxy detected
Fetching

Keep your current network connection unchanged while the check runs.

Result notes

What this information means

An IP lookup shows the network exit point presented when the current request reaches this site. It helps confirm route status, but cannot represent your entire network environment on its own.

Public IP

Your public IP is the source address external services see for a request. Run the check again after changing routes. If the address and location change, the new exit point is usually handling the connection. If nothing changes, check the client connection, refresh the subscription, and select a route again.

Location and ISP

Location and ISP data comes from an IP geolocation database and indicates the exit point’s approximate location and network operator. Database updates may be delayed, so treat the displayed location as a diagnostic reference rather than precise location data.

Proxy detection

Proxy status is an assessment returned by the API based on available network signals. Detecting a proxy does not mean the connection is faulty, and not detecting one is not a substitute for a complete privacy check. When investigating access issues, consider the exit location, DNS resolution path, and client status together.

DNS review

DNS Leak Check

DNS converts domain names into network addresses. Even after the public IP changes, the system may continue using resolvers from the original network configuration, leaving the domain lookup path inconsistent with the current route.

This page’s GeoIP result checks exit-point information only; it does not present DNS findings as part of the same result. A DNS self-check requires reviewing system network settings, the client’s takeover status, and browser diagnostics.

  1. Confirm the client’s takeover scope

    Check whether the client uses full takeover, a system proxy, or rule-based split routing. Each mode may handle system DNS requests differently, so identify the mode before interpreting the result.

  2. Check system DNS settings

    Open the details for the operating system’s active network connection and check whether DNS is still assigned automatically by the original network. If the client offers DNS takeover, confirm that the setting matches the current connection mode.

  3. Rule out browser-level DNS resolution

    Some browsers can use secure DNS independently of the system. During troubleshooting, check the browser’s network settings to avoid changing the resolution path in both the system and the browser at once.

  4. Check again after reconnecting

    After adjusting settings, disconnect and establish the route connection again, then refresh this page to confirm the exit information. If domain access is still abnormal, switch routes and update the subscription before continuing troubleshooting.

First Month Free