Network Check: Exit IP and DNS Leak Test
Open this page and it reads the country and ISP behind your current exit IP, then reports whether that address block carries proxy flags. The lookup goes only to a same-domain endpoint on this site; when no result comes back it says “Temporarily unavailable” instead of padding the page with third-party data.
Current exit details
CheckingA lookup runs automatically when the page loads, and “Check again” takes another sample. Run one before and one after switching routes — the change in exit is the clearest signal.
- Exit IP
- —
- Country / Region
- —
- ISP / ASN
- —
- Proxy flags
- —
What these fields mean
Each of the four fields answers a different question, and reading them together is how most misjudgements happen. Below is each field on its own, with the most common misreading called out.
| Field | The question it answers | Common misreading |
|---|---|---|
| Exit IP | The source address the destination site sees | Treating it as your machine's network card address. They are not the same thing: switch routes and the exit IP changes. |
| Country / Region | The registration and announcement owner of that IP block | Treating it as device location. Address databases update by block, and newly allocated or cross-border announced blocks often differ from where the address is actually used. |
| ISP / ASN | The carrier or data center that block belongs to | Seeing a data center name and assuming it is “flagged as a proxy”. Who registered the block and how good the route is are two separate things. |
| Proxy flags | Whether the address database marks this block as a hosting range or a public proxy range | Treating “not detected” as a guarantee of anonymity. It reflects flags only, and says nothing about encryption or logging policy. |
Geolocation is a database record, not device location
GeoIP derives country, province and city from where an IP block is registered and announced. Newly allocated blocks, cross-border announcements and block migrations can put the displayed city tens to hundreds of kilometres away from where you actually are. Border cities and submarine cable landing points are especially prone to this, so treat the location here as a reference, not a precise fix.
Proxy flags are block-level records, not a live verdict
This column summarizes what the address database records about hosting ranges, public proxy ranges and Tor exit nodes. A “detected” flag only means the block has been recorded before; it does not mean the current connection is unusable. A “not detected” flag is not a guarantee of anonymity either. To tell whether a route is working, check whether the exit IP has moved to the target region and whether the target service opens normally — that is more direct than this column.
The ASN and carrier name may not match a brand you recognize
One carrier can hold several autonomous system numbers, and one number can span several countries. When a data center leases a block to a downstream provider, the registration stays under the upstream name, so an unfamiliar name is not unusual. Ownership and route type are two different dimensions: the same country can have direct, relayed and dedicated routes at the same time.
DNS leak self-check: verify three places in order
A changed exit IP does not mean domain lookups are going through the route too. If resolution requests still go to your local carrier, both the queries and the answers stay on the local network, and a CDN may hand you a node far from your route and slower in practice.
-
Record a baseline before connecting
Disconnect the route client, open this page and note the “Exit IP” and “Country / Region” fields. That is the raw exit of your current network, and every later comparison uses it as the reference. You only need to record the baseline once; after that you can compare against it every time you switch routes.
-
Reconnect and reload this page to verify
Connect to a route in the target region and hit “Check again”. The exit IP should become an address in that region, with the geolocation following it. If it matches the baseline exactly, traffic is not going through the route — fix connectivity first, then look at DNS. Doing it the other way round means you never find the cause.
-
Check which DNS servers the system actually uses
The exit may have changed while resolution still goes local. Run the command for your platform below to see the current DNS server addresses; if they are still in your local carrier's range, turn on the remote resolution or DNS takeover option in the client and run the check again.
Windowsipconfig /alllook at the “DNS Servers” linemacOSscutil --dnslook at the nameserver[0] lineLinuxresolvectl statuslook at the “Current DNS Server” line
| What you see | What it means | Next step |
|---|---|---|
| Exit IP changed, DNS is still a local carrier address | Domain resolution is not following the route; queries stay on the local network | Enable remote resolution / DNS takeover in the client, then check again |
| Exit IP did not change | Traffic is not being captured, or the client is in rule mode and this page matches no rule | Switch to global mode and retry, and confirm the client shows as connected |
| Exit IP and DNS both point to the route side | Traffic and resolution both follow the route; the configuration is as expected | Make the final call based on whether the target site actually loads |
What this page does and does not check
This page only reads ownership information for the exit IP. It does not read the DNS configuration on your device and does not make an automatic leak verdict. DNS routing has to be checked on your own device using the steps above — a web page cannot read system settings, so here you get the method, not a conclusion.
Lookups are not logged
Check pages like this easily turn into data collection funnels. The boundaries for this one are listed below, and you can verify each of them.
- Results are rendered on this page only; nothing is written to your account or to subscription records.
- The lookup is not linked to a username, order or payment details, and the result is not kept after you close the page.
- Requests go only to a same-domain address on this site. No third-party lookup API is involved, and there is no fallback to a public API.
- “Copy results” writes to your own clipboard; this page never reads anything from it.
Five questions about the network check
These are the questions that actually come up: why the results disagree, what to do when it fails, and what this page can and cannot test.
Why does the page show “Temporarily unavailable”?
It means this request got no result from the site's endpoint. The usual causes are a dropped connection, the endpoint being briefly unavailable, or a timeout (this page waits about 9 seconds). Try “Check again” once, and confirm other pages on this site still open.
This page will not fall back to a third-party API, so a failure is reported as a failure rather than dressed up as a result of unknown origin.
The exit IP differs from the IP shown in system settings — which one is correct?
Both are. They are just different layers. What the system shows is usually the network card address (a LAN address), while this page shows the source address the other end sees when you reach the internet. After you connect to a route, the second one becomes the route exit address and the first usually stays the same.
Why is the location shown as the city where the data center sits?
GeoIP locates an address by the registration and announcement records of its IP block, not by device location. Hosting blocks are registered in a handful of cities, and cross-border announcements and block migrations both make the displayed location differ from where the address is actually used. Whether the exit IP has moved to the target region and whether the target service opens normally is a more reliable test than the city name.
Does “not detected” under proxy flags mean the connection is more secure?
No. That field only reflects how the address database has flagged the IP block; it has nothing to do with the encryption or logging policy of the current connection. To judge whether a route works, check whether the exit IP has switched to the target region and whether the target service opens normally.
Can this page test speed?
No. It only reads ownership information for the exit IP; it does not run bandwidth or latency tests and shows no fluctuating speed numbers. If you want your own measurements, compare at fixed times of day, take several samples, and hit the same target site each time — a single result tells you nothing.