Network Diagnostics · Current Browser Connection

IP Lookup

See the network endpoint for your current request. Check before and after connecting to compare the IP address and location details.

Current Exit IP

Waiting for lookup

IP address

Temporarily unavailable

Country / Region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Enable JavaScript to look up your current connection details.

Results apply to this browser request and don’t show how traffic from every app is routed. This tool does not automatically test for DNS leaks.

What this information means

Exit IP and location

Your exit IP is the address our API sees as the source of your request. When network acceleration is enabled, the address will usually change if your browser traffic goes through the selected route. For a useful comparison, save the results before and after connecting in the same browser, then compare them with the region selected in your client.

Country and region are based on an IP geolocation database, not your device’s location. Database update schedules, IP allocation, and ISP registration practices can all affect the result. If the location isn’t what you expected, first check whether your browser is excluded by a routing rule, then reconnect and check again. Don’t diagnose a route failure from the location label alone.

ISP and proxy detection

The ISP field shows the network operator associated with the IP address. It may identify an internet provider, data center, or upstream network, and may not match the route name in your client. If the API doesn’t provide a field, it stays marked “Temporarily unavailable” rather than being inferred from the location.

Proxy detection is a classification provided by the API; on its own, it can’t confirm whether your connection is working. “No proxy detected” doesn’t mean your traffic isn’t routed through a proxy, and “Proxy detected” doesn’t necessarily indicate a problem. To verify your setup, check the exit IP, your client’s routing rules, and whether the target app works as expected.

For app-by-app checks, see our guide to verifying your exit IP, DNS, and individual apps.

DNS Leak Self-Check

An IP lookup and a DNS test are different things. The former shows where a web request reaches us from; the latter checks which resolver handles domain lookups. This page doesn’t run a dedicated DNS test, so the results above can’t confirm that DNS is leak-free.

  1. Check your client settings first. Confirm whether you’re using a global proxy or rule-based routing, and whether DNS requests are handled by the client as intended. Available options vary by client.
  2. Check your browser’s secure DNS settings. A browser may use its own DNS settings instead of the system resolver. Note the current setting and make sure it works with your client’s DNS setup. Changing the system setting alone may not be enough.
  3. Use a DNS test tool that explains how it works. Compare the resolver details shown before and after connecting, and read the tool’s notes about encrypted DNS, caching, and forwarded lookups. The resolver name or location alone isn’t enough to determine whether there’s a leak.
  4. Review your traffic rules. If DNS requests still use your local network when they’re expected to go through the selected route, check your routing rules, DNS hijacking settings, and other network software. After making changes, reconnect and run the checks again.

Privacy Notice

We don’t log lookups. This tool requests results only from our GeoIP API and doesn’t use third-party public APIs as a fallback. The lookup script doesn’t save results to your browser’s local storage. Your IP is only written to the clipboard if you click “Copy IP.”

Displaying results requires the API to process the exit IP for your current request. Before sharing a screenshot or pasting diagnostic details, check who will receive them and avoid exposing unnecessary network information. Learn more about our Privacy Policy and VPN97’s no-logs policy.

First Month Free