IP Lookup · Public IP & Location

Public IP and location lookup

Open the page and your current public IP, country/region, ISP and proxy detection result appear right away. Lookups go through this site's own same-domain endpoint, and when no data comes back the page says "Temporarily unavailable" rather than pulling in a third-party lookup service.

  • No logs kept
  • No email address required
  • Real-time lookup on every page load
Checking…
Public IP Checking…
Country / Region Checking…
ISP / Network Checking…
Proxy detection Checking…

Querying this site's endpoint…

The result reflects your public IP only at the moment of the lookup; switch servers or reconnect and all four fields change with it.

Reading the results

What these details tell you

Each of the four fields answers a different question; together they give you a full picture of your current exit.

IP

Public IP

When you access services outside your region, this is the address they see. It determines which region those services place you in, and shapes which content library, interface language and sign-in risk checks you get.

GEO

Country / Region

The location comes from a reverse lookup against an IP database and may differ from where you actually are. Once a server is connected, it should match the exit location of the server you picked.

ISP

ISP / Network

This field shows who owns the IP and what kind of network it belongs to. Data-center and residential networks are labelled differently, and some platforms adjust how strictly they screen traffic based on that.

PROXY

Proxy detection

Some platforms check whether a visit comes from a data-center or proxy address. When it does, you'll usually see more CAPTCHAs or an extra sign-in confirmation rather than a dropped connection.

DNS leak self-check

Are your DNS lookups going through the tunnel?

A public IP outside your region doesn't mean DNS resolution happens there too. Three steps will show you which side your queries land on.

What a DNS leak is

When you open a website, your system first resolves the domain name to an IP address, then opens the connection. If that resolution request skips the tunnel and goes straight to your local network's resolver, your local network can see which domains you visited — the public IP sits abroad while the browsing record stays local. That's a DNS leak.

Three-step check

  1. Connect a server first and note the exit details. Go back to the top of this page and write down the Public IP and Country / Region values — for example, an exit showing Japan.
  2. Query your resolver from a terminal. On Windows, run nslookup example.com in Command Prompt or PowerShell; on macOS and Linux, run the same command in Terminal. Look at the Server line at the top of the output — that's the resolver address currently in use.
  3. Compare the two results. The resolver should belong to the region your exit is in. If the public IP is abroad but the resolver is still your local ISP's address, the queries aren't going through the tunnel.
$ nslookup example.com
Server:  198.51.100.10
Address: 198.51.100.10#53

Non-authoritative answer:
Name:    example.com
Address: 203.0.113.24

The addresses in the example above are illustrative and only show where to look in the Server line.

Two cases that are easy to misread

First, if the browser has secure DNS enabled, it may resolve names itself, bypassing your system settings. In that case the result from a system command doesn't reflect the resolver the browser actually uses, so check the browser settings separately.

Second, the resolver may show an address abroad but belong to a public DNS service in a different region from your exit. The thing to check is whether it still points to your local ISP, not just whether the address is outside your country.

What to do if DNS isn't going through the tunnel

  1. Disconnect and reconnect once — in most cases DNS queries will follow the tunnel again.
  2. Check whether any DNS-related option in the client has been turned off manually, restore the defaults and reconnect.
  3. If it still happens, submit the full nslookup output together with the exit details from this page in a ticket, so support can tell whether the problem is on the server side or on your local side.

Tickets are opened from the user panel: Open a ticket. For import and setup steps for each platform's client, see the Guides page.

Lookups aren't logged

Lookups on this page are used only to return the result to you: requests aren't written to logs, aren't linked to your account and aren't used for profiling or ad targeting. Checks run through this site's own same-domain endpoint and are never handed to a third-party lookup service; if the endpoint is temporarily unavailable, the page says so plainly instead of filling in data from another source.

  • No logs kept
  • No email address required
  • Payment Alipay / WeChat Pay / USDT
FAQ

IP Lookup FAQ

Why is the IP I see different from what I expected?

Your public IP depends on the server you're connected to. Different servers exit in different regions, so the result changes when you switch or reconnect; with no server connected, it shows your local network's public address.

What if the page shows "Temporarily unavailable"?

It means this site's GeoIP endpoint didn't return data that time. Try Check again, or come back later; until the endpoint recovers, the page won't fill the result with third-party data. If it keeps happening, you can report it in a ticket.

Does it matter if proxy detection flags the address?

It's just one assessment of the current IP's attributes and doesn't affect the connection itself. Some platforms screen such addresses more strictly, so if you see more CAPTCHAs or an extra sign-in confirmation, switch to another server and try again.

Can an IP lookup detect a DNS leak?

This page only shows the public IP, its location and proxy detection; it doesn't run a resolution test. To check for a DNS leak, follow the three steps above and compare results with nslookup on your own device.

For more questions, see the Help Center, or read the AI Tools access guide for more detail on how regions and risk checks are determined.

Free to Use