Network Check
Open this page and you'll see the exit IP, location and ISP of the current browser, plus the proxy-detection flags returned by the API. Results come only from our own same-domain endpoint; when a value can't be retrieved, the page says so instead of filling in an estimate.
This is the exit address used when this request reached our site. Switch routes or disconnect, then hit “Check again” — the address and location change with it, which tells you whether the current connection is actually in effect.
Field guide
Four fields, four questions: which address the request came from, where that address is registered, who holds it, and whether it has been flagged as a proxy exit.
The source address used when this request reached our site. With no route connected it is usually the public address of the network you are on; once connected it becomes the exit address of the route you selected. The address itself does not point to a person, but it does reflect the network this request belongs to.
Derived from the registration data of the IP block, accurate to country and city level — never down to a street or building. Route exits are usually held by data centers, so the registered location and the actual facility may not match exactly; the result shown follows the registration record.
Shows who holds this address block. Home broadband usually shows the local ISP; a route exit usually shows a data center or network provider. This line is the most direct reference for telling whether a request really went through the route.
Some address blocks are flagged in public databases as data center, proxy or VPN exits. This line only displays the flag returned by the API; it does not mean the destination site will block you. With services that are sensitive to network environment, switching to another route type is usually the quicker fix.
| What you see | Likely cause | What to do |
|---|---|---|
| Location matches the region of the selected route | The request is exiting through the selected route | Nothing to do — just use it |
| Location still shows your local ISP | The connection is not active, or this app is not using the route | Disconnect, reconnect, check again, and confirm the client is in global mode |
| A proxy detection flag is shown | The exit address is flagged as a data center or proxy in public databases | Switch to another route type — dedicated, relayed or direct — and check again |
| All four fields show temporarily unavailable | The lookup endpoint returned no result this time | Hit “Check again”; make sure the current network can load this site, then retry |
This table describes common patterns rather than any specific route; the page display is the authoritative result.
Self-check steps
A DNS leak means the web traffic already goes through the route, but domain lookups are still sent by the resolver on your local network. The two requests take different paths, so the location a site sees ends up inconsistent.
Web traffic and domain resolution are two different kinds of request. Once the client sends web traffic into the route, if the system resolver settings still point at the local network, lookups go out locally. The site receives a visit from the route's location while being told a local one — so its judgement naturally disagrees.
Typical signs: on the same device, some services already show the route's location while others still say the region is unsupported; or everything works right after connecting, then asks for verification again after you switch networks. This kind of inconsistency usually means the resolution path and the traffic path are out of sync.
Disconnect the route, open this page and note the exit IP and location. This is your baseline; every later comparison is against it.
Connect the route you normally use, come back to this page and hit “Check again”. If the page has been open without a refresh, reload it first so you don't read a stale result.
If the second result shows the route's location, the request really did go through the route; if it still shows your local ISP, this path is not working and you should check the connection state in the client.
Dedicated, relayed and direct routes have different exit characteristics. When one shows a local location, checking again with another type separates a route problem from a client setting problem.
The self-check is about where requests leave from, not how fast lookups are. Fast resolution does not mean no leak, and slow resolution does not mean a leak — the two are unrelated.
If repeated checks still show a local location, first confirm the client is in global mode: in split-tunnel mode only apps that match the rules use the route. If it still doesn't match, note the route name and the time of the check and report it to the support center — that is far easier to trace than “it won't connect”.
Privacy
This page is a lookup tool that requires no login. Results are used only for the current display and never enter the account system.
Lookups made here are used only to generate the result shown for this visit; refreshing runs a new lookup, and we keep no history of your queries.
This page requires no login. Even if you are signed in on another tab, results here are not linked to your account profile and do not affect your plan or data usage.
Lookup requests go only to our own same-domain endpoint, and the response is rendered directly in your browser; the page keeps no copy of it.
Subscription traffic is quantum-encrypted between the client and the route. If you need a route you can switch at any time to compare against these results, you can start free or view plans first: monthly plans from ¥9.9 with 60GB, unlimited devices, a 30-day money-back guarantee, and no email address required to get started.
FAQ
IP blocks are registered under the organization that holds them, and route exits are usually held by data centers, so the registered location and the actual facility may not match exactly. That is normal for registration data and does not mean the check failed. To judge whether a connection is active, whether the location has left your local ISP is the more reliable signal.
This line only displays the flag returned by the API. Some services take such flags into account; when you hit a restriction, switching to another route type is usually the quicker fix. This page makes no blocking decisions and the flag does not change your connection.
The usual reasons are that the client is still reusing an old connection, or that you are in split-tunnel mode and this page is not going through the route. Disconnect and reconnect, then hit “Check again”; if it still doesn't change, check whether the client is in global mode and whether the browser is using the system proxy.
This page requires no login. Results are used only for the current display, are not written to your account profile, and no query history is kept. Refreshing the page runs a new lookup.