NETWORK CHECK
Current exit IP and DNS leak self-check
Opening this page sends one query to the site's own same-domain API, which returns your current exit IP, country/region, ISP and proxy detection results. The result is shown on your device only and is never written to your account; if the API is temporarily unavailable, the page says so plainly and never falls back to a third-party service.
- 7-day money-back guarantee
- Quantum encryption
- Alipay / WeChat / USDT
- Unlimited devices
QUERY RESULT
Current exit information
Querying the site's own same-domain API for exit information…
SCOPE
Query scope and network overview
This page reads only the current exit information for this device — no speed tests, no query history. The network covers 100+ countries / 250+ routes with unlimited devices, supports Alipay / WeChat / USDT payment, and includes a 7-day money-back guarantee; sign-up needs only a username and password, no email address.
- 100+Countries covered
- 250+International routes
- 7 days money-back guarantee
READ THE RESULT
What these fields tell you
All four fields answer one question: who does the destination site see as the source of this visit? The exit IP is the address it reads directly. Country/region and ISP come from public IP database records for that address. Proxy detection is a rough call that combines IP block attributes with protocol fingerprints. Together they show whether your traffic is really taking the route you expect.
| Field | Meaning | How to read it |
|---|---|---|
| Exit IP | The source address the destination site sees | Should match the region of the route you selected once connected |
| Country / Region | The IP database's record of where the exit address belongs | Country-level results are fairly reliable; city-level results can be off |
| ISP / Carrier | The organization registered as the user of that IP block | Datacenter routes often show a datacenter name — that's normal |
| Proxy detection | A rough assessment of the IP block's attributes | For reference only — platforms use different criteria |
Exit IP vs. your local network's exit
On a direct connection, the exit IP shown here is your local network's public address, and its location usually points to your local carrier. After you connect to a route, the exit IP becomes an address in the route's location, and the location record changes with it. To confirm the switch worked, watch this field — not the connection status icon in your client. If the client shows connected but the exit IP is still your local address, your traffic isn't actually going through the route.
When to check again
Three situations are worth another check: right after you first set up a route, when you switch to a new network (from home to the office or a public network, for example), and when video playback or an AI tool shows an unexpected error. No extra tools needed — just refresh this page and compare the two results.
DNS CHECK
DNS leak self-check: the two-step comparison
A DNS leak means your traffic goes through the accelerated route while domain lookups are still handled by your local network, leaving the lookup records exposed on your local exit. You don't need extra tools to spot it — one before-and-after comparison on this page is enough.
- Disconnect the accelerated connection, refresh this page, and note the "Exit IP" and "Country / Region" results.
- Connect to the route you selected (Japan · Tokyo, for example), refresh this page again, and note the same two fields.
- Compare the two "Country / Region" results: if the second one matches the route's region, both traffic and lookups are following the route; if it still shows your local region, lookups aren't following the route and you should keep troubleshooting.
- If you hit the second case in step 3, switch to another route (an IEPL dedicated line first) and test again. If it still doesn't follow, open a ticket in the panel and include the two exit IPs and locations you recorded so support can pinpoint the issue.
Note: If other acceleration tools, your browser's built-in secure DNS, or a local DNS cache are running on the same device, a single result can be misleading. Keep only one route active, clear the browser cache, and test once more before drawing conclusions.
PRIVACY
Privacy note: queries are not written to your account
Queries on this page return only the exit IP and location information needed for the current display. Nothing is written to your account, and the data isn't used for profiling or statistics. The API doesn't accept account credentials, so query records can't be linked to a username, and the copy button copies only the address shown on the page.
Sign-up: VPNDU needs only a username and password — no email address required. Plans support Alipay / WeChat / USDT payment and come with a 7-day money-back guarantee; data packs last until used up and never expire.
FAQ
FAQ
Four common questions about the results and the self-check steps.
What if the result keeps showing "temporarily unavailable"?
It means this request didn't get a response from the API — usually just a brief outage, and it doesn't affect your route. Click "Check again" first; if it still fails, run the two-step comparison above or open a ticket in the panel and describe what you see.
Is it normal that the location shows only a country, not a city?
Yes. IP databases vary widely in city-level accuracy, while country/region results are more reliable, and this page doesn't treat city-level data as a basis for judgment. To tell whether a route is active, just check whether the country/region changes with the route.
Does "datacenter or proxy detected" affect streaming?
Some streaming platforms run extra checks on datacenter IP ranges. If playback throws an error, try another route — an IEPL dedicated line first. Whether a title plays is up to the platform's own check at that moment; the result on this page is for reference only and doesn't represent the platform's final call.
Does the query expose my local exit?
The page only shows the current exit address: on a direct connection that's your local network's exit, and after you connect to a route it's the route's exit. Results are displayed on your device only — never written to your account, and never shown on any public page.