Connection Check

Public IP and Location

Check your current public IP first, then connect to a route and check again. This shows the network exit used by your browser’s request, not your device’s local network address.

Current lookup results

Checked via our API
Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet Service Provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Temporarily unavailable. The lookup requires JavaScript and our API to be available.

Proxy detection is a classification provided by the API, not a verdict on privacy, security, or streaming access. This page does not automatically test for DNS leaks.

What this information tells you

Use these results as troubleshooting clues; no single field can confirm that your connection is working as expected.

Public IP: the address websites see

Before connecting to a route, copy your current address for comparison. After connecting, select “Check again” to see whether your public IP has changed. If it hasn’t, first confirm that the client is connected, then check whether your browser is set to bypass the route. With split tunneling, different websites may use different exits; this page only shows the path taken by the lookup request.

Location: an estimate from an IP database

The country or region comes from an IP database, not your device’s location. IP allocation, network routing, and database updates can all affect accuracy. If the result doesn’t match your selected route, check the route and rules in your client first. Don’t rely on a city name alone to decide whether something is wrong.

ISP: the network associated with your public IP

This may show the name of an internet provider, hosting network, or egress network operator. It’s possible for this to differ from your local broadband provider when connected to a route. This field alone can’t confirm that an IP is residential or that a particular platform will work.

Proxy detection: a limited classification

“Proxy detected” means the API returned a matching indicator; “No proxy detected” only means that this indicator wasn’t found in this lookup. If data is missing, the result will show “Temporarily unavailable” rather than defaulting to “No proxy detected.” Target websites may use different detection methods and reach different conclusions.

DNS Leak Check

An IP lookup answers “where is this request going out from?” A DNS check looks at “who is resolving the domain?” They’re different checks.

This page’s GeoIP API can’t observe the full domain resolution process, so it won’t claim that a “DNS test passed.” A changed public IP also doesn’t prove that DNS requests and browser traffic use the same route.

  1. Check your client’s DNS and routing settings. See whether the client has DNS interception or a relevant resolution mode enabled, and read the documentation for your current rules. Options vary by client; a single toggle’s label doesn’t prove that all traffic uses the route.
  2. Check your browser’s Secure DNS settings. A browser may use DNS settings separate from your operating system. Confirm that they match your client’s configuration, and don’t enter an unfamiliar DNS address just to troubleshoot. Keep a record of your original settings so you can restore them.
  3. Cross-check with diagnostics from your operating system or client. Check which resolver is actually in use and how requests are routed. If you use a trusted, dedicated test tool, read its privacy policy first and compare the results. A resolver’s reported location alone doesn’t prove that a leak has occurred.
  4. Include what you observed and your settings when asking for help. Share your platform, connection mode, target website, and the issue you noticed, then contact support through the dashboard ticket system. Before sharing screenshots, hide your full IP address, username, and subscription details.

If you only want to confirm that a route was imported correctly, first follow the guide to check your connection status and public IP, then troubleshoot DNS settings. Change one type of setting at a time to make the cause easier to identify.

Lookup privacy

We don’t log queries. Lookups use an API on our own domain; we don’t fall back to third-party public lookup APIs. The API must see your public IP to return location information.

This tool doesn’t save results to your browser’s local storage or put your IP in the page URL. When you select Copy, only your public IP is written to the clipboard. You decide what to do with the clipboard contents. Remember that an IP address is network-identifying information when sharing results publicly.

Read our Privacy Policy