Exit IP & route check

Check your current exit IP and location

Check the browser's current exit IP, country / region and ISP to confirm whether the route is really active. After you connect, run the lookup again — the exit address should match the route's location. If nothing changes, this visit isn't going through the route.

120+Countries / regions 240+Routes UnlimitedSimultaneous devices
GET /plane-api/geo

Current exit IP

Checking…

Country / region
ISP / Carrier
Proxy detection
Not checked

Looking up exit info…

Reading the results

What these details tell you

Each of the four items in the result card covers one dimension — read them together to confirm whether your traffic is really going through the route.

Exit IP

This is the address the destination site sees. After you connect, it should change to an address in the route's location. If the result still shows your local network's address, this visit isn't going through the route. There are three common causes: the system proxy is off, split-app routing doesn't include the browser, or the client never actually connected.

Country / region

Use it to check whether the exit location matches the route you selected. Different route types exit in different places, so when the result doesn't line up exactly with the route name, check that route's type description before judging — don't go by city name alone.

ISP / Carrier

Shows which network this IP belongs to. The difference between data-center IPs and residential broadband IPs is clearest in this row, and it's exactly this kind of ownership data that streaming platforms use to decide whether an IP counts as native. The same route performing differently across platforms often comes down to this.

Proxy detection

Flags whether this IP is identified as a proxy or data-center source. A flag doesn't mean the route is unusable, but some platforms restrict access on that basis. If a specific platform blocks you, switching to a route of a different type usually works better than refreshing over and over.

Self-check steps

How to check for DNS leaks

A DNS leak means domain lookups skip the route and go straight to your local network's DNS server. It won't change the exit IP shown on this page, but it makes the resolver that destination sites see inconsistent with your actual exit. This page only looks up the exit IP; to verify the resolution path, follow the steps below on your system.

  1. Connect to a route first, then come back to this page and run the lookup again. Note the exit IP and its region.
  2. Open your system's network settings and check the DNS server address currently in use. If it's your local ISP's address, lookups may not be going through the route.
  3. Back in the client, make sure System Proxy is enabled. If you use split-app routing, add the browser to the proxied apps and run the lookup again.
  4. Switch to a route of a different type (IEPL dedicated / relay / direct) and check again to see whether the exit IP changes with it. If the address stays the same, your traffic isn't really going through the route.

Order of checks

Confirm the exit IP has changed first, then look at DNS ownership, and only then troubleshoot a specific platform. If the exit IP hasn't changed at all, the later checks won't tell you anything.

Privacy note

Lookup requests on this page are used only to return the current result — they aren't used to build user profiles or for ad targeting. Results appear only in the current browser tab, and refreshing the page runs a new lookup.

Lookups are returned in real time by this site's own GeoIP service; the page doesn't use any third-party lookup service. See the Privacy Policy for details.

FAQ

How to read the results

The result matches my local network — am I not connected?

That means this visit isn't going through the route. Check three things in order: whether the client shows connected, whether the system proxy is on, and whether split-app routing includes the browser. Once all three check out, run the lookup again.

The exit IP is in a different city than the route I selected — is that normal?

It depends on the route type. What matters is whether the exit IP has left your local network and entered the route's region, not whether it matches an exact city. When the result doesn't line up exactly with the route name, check that route's type description before judging.

It says a proxy was detected — will that affect anything?

It means the IP is identified as a data-center or proxy source, and some platforms throttle on that basis. It reflects the IP's attributes, not connection quality. If a specific platform blocks you, try a route of a different type.

Can I run the lookup without connecting to a route?

Yes. You'll see your local network's exit IP and ISP, which makes a useful baseline: connect to a route and look up again — only if the two results differ is your traffic really going through the route.

For more on accounts, connections and billing, see the Help Center.

Keep reading

Related guides

Guides

Is Your VPN Actually Connected? A Three-Step Check of Exit IP, DNS and Split Tunneling

A client showing Connected doesn't mean your traffic is really going through the route. Verify it in three steps — exit IP, DNS ownership and a split-tunnel test — plus common cases where everything looks connected but nothing is, and how to handle them.

Read the full guide
Guides

Windows VPN from Scratch: Install, Import a Subscription, Launch at Startup

For first-time Windows users: get the client, import your subscription, pick a route, confirm it's working and set it to launch at startup. Every step spells out what to click and what you'll see, so you can follow along and get connected.

Read the full guide

When you need a different route, filter by region and route type on the Global Locations page.

First Month Free