The check runs automatically when the page opens: public IP, country/region, ISP, and whether the address carries proxy traits. Results come from our own server API and are used for this display only.
We can't retrieve the lookup results right now. This page doesn't fall back to third-party APIs, so when data isn't available it won't show guesses. Try “Check again” in a moment, or first confirm the route in your client is connected.
Field guide
All four results come from the same server-side lookup record. Most of the time you only need the first two: which country/region the public address sits in, and what kind of network it belongs to.
The public IP is the address a request uses when it leaves the route exit. Your device's address on the local network (something like 192.168.x.x) is only valid inside that network, so the two were never going to match. Cross-border acceleration forwards traffic on the server side, so websites see the route exit's address, not the address of your physical location.
This field comes from the address's registration data and usually resolves down to country and city. If the region shown matches the route you picked manually in the client, traffic really is leaving through that route. If it doesn't match, first check whether auto-select is on — auto-select switches between routes, so the region changes with it, and that's not a fault.
This column shows the carrier or data center the address belongs to. A data-center name means a data-center route; streaming services and risk-control systems judge it differently from home broadband, so some sites may run a different verification flow.
Proxy detection is a server-side result that reflects whether the address carries proxy traits. A “detected” flag doesn't mean anything is wrong with your connection — only that a few sites may ask for extra verification, such as a CAPTCHA or email confirmation. Everyday browsing and video playback are unaffected.
| Field | Meaning | Common misreadings |
|---|---|---|
| Public IP | The public address used when a request leaves the route exit | Not the same thing as your device's LAN address — no need to compare them |
| Country / Region | The address's registered location, usually down to country and city | If it differs from your chosen route, check whether auto-select is on |
| ISP | Name of the carrier or data center the address belongs to | A data-center name means a data-center route, judged differently from home broadband |
| Proxy detection | Server-side result on whether the address carries proxy traits | A “detected” flag doesn't mean a broken connection — it's just how risk control sees it |
Self-check steps
A DNS leak means your web traffic goes through the route, but domain resolution is still handled by your local network or ISP. The self-check takes three steps, needs no extra tools, and uses commands already built into your system.
Pick a route in the client and confirm the status shows as connected. Then open Terminal (macOS / Linux) or Command Prompt (Windows) ready for the next command.
On Windows run nslookup example.com; on macOS and Linux run dig example.com. The Server or SERVER line in the output is the resolver address actually used for this lookup.
Compare this address with the public IP location shown at the top of the page. If both are in the same region, resolution and forwarding are travelling the same route; if the resolver shows a local ISP address, resolution isn't going through the route.
# Windows (Command Prompt)
nslookup example.com
# macOS / Linux (Terminal)
dig example.comexample.com in these commands is just a sample domain — swap in any domain you normally visit. The line to watch is the resolver, not the list of resolved addresses.
Once connected, our client hands domain resolution to the route side and doesn't rely on your local network's DNS settings. If the self-check doesn't match expectations, quit any other proxy tools, disconnect and reconnect the route, then run the commands above again.
Privacy notes
Lookups on this page are handled instantly by our own server API. Results are returned to the current browser for display only, are not written to access logs, and are not linked to any account. No login is needed to use this page, and you can run a lookup without an account.
KimiVPN's logging policy is anonymous and log-free: no browsing content and no destination records. Creating an account needs only a username and password — no email address. Plans start at ¥9.9/month with 60GB of traffic, and a 7-day money-back guarantee.
FAQ
The page shows the public address used when a request leaves the route exit. Your device's LAN address is only valid inside the local network, so the two were never going to match. If another proxy tool is running at the same time, the address shown may be that tool's exit.
First check whether auto-select is on in the client — it switches between routes, so the region changes with it, and that's normal. If you've pinned a specific route and it still doesn't match, quit any other proxy tools, hit “Check again” and look once more.
Most often the API request timed out or the current network is unreachable. This page doesn't fall back to third-party APIs, so when data isn't available it only shows a notice and never guesses. Hitting “Check again” a little later usually fixes it; if it keeps failing, first confirm the route in your client is connected.
No. Lookups are handled instantly by our own server API, and results are returned to the current browser for display only — not written to access logs and not linked to any account. No login is needed to use this page.
Keep reading: Route and protocol reference See all routes Setup guide