DX · Exit IP Check

What Is My IP Address

The page reads your current exit IP, country/region and carrier as soon as it opens, with a proxy detection reference; DNS leak self-check steps are on the same page. Test requests go from your browser to our own same-domain API, and no guessed values are shown before a result arrives.

120+ countries / 220+ routes
Unlimited simultaneous devices
30-day money-back guarantee
No email address required

IP LOOKUP

Current Exit Test Results

The page runs a check automatically when it opens. After you switch routes, reconnect or change networks, click “Check Again” to refresh the values.

Test Results

Checking…

Exit IP: —
Country / Region: —
ISP / Carrier: —
Proxy Detection: —

Fetching data from our own API, please wait.

How to Use These Results

Note the exit IP and its location. This is the address and region your web traffic shows to the outside world, and the first thing to check when confirming a route is working.
Switch to another route and test again. Change region in your client, reconnect, come back to this page and click “Check Again” to see whether the location matches the route you picked.
Check the ISP and the proxy flag. A data-center ISP and a proxy flag are normal and do not affect the route; a residential ISP usually means traffic is leaving through a local broadband connection.

If the Check Fails

When the API is unavailable, the result fields all show “Temporarily unavailable”. The page never fills in guessed values and never falls back to third-party public APIs. Try “Check Again” later, or check the routes page first to confirm the current status of your route.

Results are a snapshot of that single request; values may change after you reconnect, which is normal.

FIELD GUIDE

Reading the Test Results

The four fields answer different questions: exit IP is about the address itself, country/region is where it lands, ISP is the nature of the route, and proxy detection is how that IP is flagged in public databases.

Exit IP

The address shown to the outside

The source address web requests show to the destination site when they leave your device. When you access cross-border services, it should be an address in the region your chosen route lands in; if it is still a local carrier address block, your traffic is not going through the route. Reconnecting on the same route may give you another exit in the same region — as long as the region stays the same, that is normal.

Country / Region

Landing Location

The registered location of the exit IP, resolved by IP databases from the allocation records for that address block. It determines the regional content you see and whether some services are available: if you want to watch streaming from a certain region or use AI tools that only open in specific regions, confirm this field shows the right region before opening the site.

ISP / Carrier

Who Holds the Address Block

The organization that holds this IP block. A data center or cloud provider means you are on a data-center route, which suits use cases that need stability and bandwidth; a residential broadband carrier usually means traffic leaves through a home connection. Some platforms use this field to judge where a visit comes from, but it does not affect the encryption or speed of the route itself.

Proxy Detection

Database Flag Reference

A reference judgment based on IP block characteristics and public databases: it only says whether this address is flagged as a data-center or proxy source. It does not say whether the route is encrypted, nor does it reflect connection quality. A proxy flag does not stop you from using the route; a few platforms may ask for extra verification because of it, and switching to another route usually clears that.

DNS CHECK

DNS Leak Self-Check

Web traffic and domain resolution take two different paths. Your exit IP may have changed while resolution requests are still handled by the resolver handed out by your local network, so this step needs a separate check.

First note your current exit region. Connect to a route, open this page and note the location shown in “Country / Region” — it is the baseline for the steps below.
Look at the resolver your system is currently using. On Windows, check the IPv4 properties of your network adapter under Network & Internet → Adapter options; on macOS, look under System Settings → Network → Details → DNS. Write down the addresses in the list.
Verify the resolution exit from the command line. Run the command below in a terminal and see whether the resolver address it returns matches the region of your current route. If it returns the set handed out by your local network by default, resolution is not going through the route.
If they do not match, change how DNS is resolved and test again. In your client settings, choose to resolve DNS on the route side, or manually set a resolver address in your system network settings that matches the route's region, save, reconnect, then come back to this page and re-check the exit IP and the resolution result.

$ nslookup example.com
Server:  <resolver address>
Address: <resolver IP>

The example domain is a placeholder — replace it with the domain you want to check.

Why Pages Load but DNS Resolution Can Still Go Local

Web traffic and domain resolution are handled by different stages. The former goes through the route; the latter may still be done by the resolver handed out by your local network, which shows up as some sites loading slowly or resolving to a distant node. The thing to judge is who owns the resolver, not whether pages open.

PRIVACY

Query Privacy Notes

Query contents are never logged

Test requests on this page go straight from your browser to our own same-domain API and are used only to return that one result; query contents are never logged or tied to your account. VPNDX routes use military-grade encryption, allow unlimited simultaneous devices, accept Alipay / WeChat Pay / USDT, come with a 30-day money-back guarantee, and require no email address to get started.

FAQ

Frequently Asked Questions

The region detected is different from the city I am in — is that normal?

Yes. The exit IP is determined by the data center where your current route lands, not by where your device is. To confirm the route is working, check whether “Country / Region” matches the landing region of the route you selected — not how close it is to you.

Proxy detection says “proxy detected” — do I need to do anything?

Usually not. This field only says that the IP block is flagged as a data-center or proxy source in public databases; it has nothing to do with encryption or connection speed. A few platforms may ask for extra verification because of it, and switching to another route or region usually gets around that.

The results did not change after I switched routes — what should I do?

Disconnect, reconnect, then come back to this page and click “Check Again”. Your browser and system may cache resolution from the previous connection; waiting a minute and testing again usually refreshes it. If the old address still shows, your traffic is not going through the new route — check the client's connection log to confirm which route is actually in use.