IP Lookup

IP Lookup & Leak Check

Look up your current exit IP, location and ISP, then compare two results to see whether DNS resolution follows the route you're connected through. Results come from our GeoIP API; if none are available, the page says so instead of estimating.

100+ countries / 230+ routes No device limit 14-day refund, no questions asked

Current exit details

Data comes from our GeoIP API and reflects only the exit address of this request; if the API returns no usable result, all four fields show the same unavailable notice.

Checking
Exit IP

—

Country / Region

—

ISP

—

Proxy check

—

Reading the results

What these details tell you

Each of the four fields answers one question. None of them on its own proves whether a route is working — read them together.

Exit IP

Websites and services see the source address of this request. Switch routes, reconnect or change device and look up again: the address usually changes. If it stays exactly the same, first confirm the client really is connected.

Location

IP databases estimate country, region and city from an address block's registration and routing data. City-level results are often off, especially near borders; go by the country / region field instead.

ISP

Shows the network the address block belongs to. Data center and cloud addresses usually show a hosting provider name, while home broadband shows the local ISP — this is the field that best separates residential exits from data center exits.

Proxy flags

Public IP databases tag addresses as data center, proxy or Tor. Each database applies its own criteria, so the same route often gets different verdicts in different places — treat this as a hint only.

Self-check

DNS leak check

If DNS requests are still resolved by your local network, domain names and lookup times stay on the local link, and you may be resolved to a node that isn't the route you're connected through. The four steps below need no extra tools — just compare them with the results on this page.

  1. Record a baseline first

    Disconnect the route, run a lookup on this page, and note the exit IP, country / region and ISP. That's what things look like with no route active — every later comparison uses it as the reference.

  2. Look up again with the route connected

    Connect the route and look up again; compare whether all four fields changed together. If only the IP changes while location and ISP stay the same, the request may have a new address while DNS resolution still happens locally.

  3. Repeat with another route type

    Run one lookup on a relay route and one on an IEPL dedicated line; location should follow where each route exits. If the difference always shows up on one particular route, suspect that route's DNS configuration before blaming the client.

  4. Check the DNS settings on your device

    If your system or browser has a local DNS server set manually, domain resolution can bypass the tunnel even when traffic goes through the route. Set DNS back to automatic and repeat steps one to three.

This page only reads public registration data for the exit address. It doesn't send DNS queries and can't see your device's DNS settings — you'll need to do the comparisons in the four steps yourself.

Privacy

Lookups & privacy

The lookup is a public tool and needs no sign-in. These three points explain how the data is used.

  • VPN31 doesn't log your lookups. Results are used only for display on this page; nothing is retained or linked to an account.
  • Only public registration data is read. Country / region, ISP and proxy flags come from public IP databases; the page doesn't read device information, browser fingerprints or local network settings.
  • Every refresh is a new lookup. Results aren't cached: each time you open the page or hit Check again, the exit address is looked up fresh.
FAQ

About your results

Results don't match my actual location — is that normal?

Yes, that's normal. Location is estimated by IP databases from an address block's registration and routing data, and city-level results are often off; a cross-border route's registered exit can also differ from where the data center really is. When checking whether a route is working, country / region and ISP changing together is a more reliable signal than the city.

Connected, but the location still looks local — what should I check?

First confirm the client shows as connected, then switch to another route and look up again. If several routes all show your local area, the client's split-tunnelling rules are probably excluding this page from the tunnel, or a local DNS server is set manually in your system; set DNS back to automatic and check once more.

The proxy check says a proxy or data center signature was detected — does that affect anything?

It doesn't affect the connection itself. Data center and cloud address blocks are often tagged as hosting or proxy by public IP databases, and each database applies its own criteria, so the same route getting different verdicts in two places is normal. Treat this field as a hint only.

Does the lookup record my IP?

VPN31 doesn't log lookups; results are used only for display on this page. The lookup is a public tool — no sign-in and no email address required.

View all routes How to choose a route View plans