NETWORK CHECK

Public IP and location

See the network route your browser is using right now. After switching routes, run the check again and compare the results.

Current connection

GeoIP

Waiting for a check. JavaScript is required to retrieve your current connection details.

Public IP
Temporarily unavailable
Location
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Only the public IP is copied.

What these results mean

Public IP and route verification

Your public IP is the address visible to external services for this browser request. When a proxy is enabled, it may be the proxy route’s exit address. With split tunneling, this page may still use your local network. The result only describes the route used to reach this page’s lookup API; other apps may use different routes.

To verify a route, note the result before connecting, then connect to the route you want to test and run the check again. If the address hasn’t changed, make sure the client is connected and that your browser and this site’s domain match a proxy rule. See the Getting Started Guide for setup steps.

Location and internet service provider

The location is based on an IP address database, not your device’s location. Database updates, address allocation, and network routing can all affect what’s shown. The ISP field identifies the network organization associated with the address. When using a proxy, it may show the provider or hosting network at the exit point rather than your local broadband provider.

Proxy detection doesn’t prove a connection

The proxy field shows only the result returned by the API. No proxy detected doesn’t necessarily mean your browser isn’t using one, and a proxy detection result doesn’t mean other websites will reach the same conclusion. If the API returns no clear result, this page shows “Temporarily unavailable” rather than inferring one from the address or location.

Check for DNS leaks

DNS translates domain names into network addresses. A changed public IP alone doesn’t prove that DNS queries are following the expected route. This page’s GeoIP request doesn’t check DNS resolvers, so it can’t confirm that a DNS leak test has passed.

  1. Review your client settings. Check DNS, split tunneling, and system proxy settings to make sure domain resolution matches your current setup. A system proxy may not handle DNS requests from other apps.
  2. Check how your browser resolves domains. The browser’s secure DNS settings may differ from your system settings. Note your current configuration and compare it with your client’s DNS guidance before changing anything. Avoid changing multiple options at once.
  3. Compare DNS routes before and after connecting. Review your DNS settings in the system network preferences and use any DNS diagnostics available in your client to understand where requests go. Seeing an address in the settings alone doesn’t confirm the route taken by every query.
  4. Test apps with issues again. If only one app can’t connect, check its own proxy settings, cache, and routing rules. A working browser connection doesn’t rule out an issue with the app itself.

PRIVACY

Privacy note

Queries aren’t logged. This check retrieves connection details for the current request through our own API and doesn’t fall back to public third-party lookup services. If the API is unavailable, the page displays an error.

Your public IP is network information. Consider masking it before sharing screenshots or troubleshooting notes. The copy button copies only the IP; it doesn’t submit it to a support ticket or any other page. See our Privacy Policy for details.

Start Free