IP Lookup
Exit IP and DNS leak self-check
Once connected, the exit IP, location and ISP should match the region of the route you picked. If they still show your local carrier, traffic is not going through the proxy. This page reads the current exit details from our own endpoint and adds a DNS leak self-check list.
Current exit details
Waiting for lookup- Exit IP
- Looking up…
- Country / Region
- Looking up…
- ISP / Carrier
- Looking up…
- Proxy detection
- Looking up…
The lookup runs through our own endpoint; results are shown for this visit only and are not written to any query log.
Reading the results
What these details mean
The four fields cover different layers of the connection; only together do they show whether the proxy is actually working.
01 · Exit IP
The address sites see
After you connect, the exit IP should change to an address in the route's location. If it still matches the address your local carrier assigned, traffic is not going through the proxy — check whether the client is connected and whether the routing rules exclude the current app.
02 · Country / Region
How services place you
Streaming and AI tools decide your region from where the exit address is registered, so pick a route by the region the target service cares about rather than grabbing whichever looks convenient. If the region shown doesn't match the route you chose, the client is usually still on the previous one.
03 · ISP / Carrier
Who holds the address
Seeing a data center or cloud provider is normal — it confirms traffic really leaves through the route's exit. Seeing your local broadband carrier basically means the connection went direct. On some routes the carrier name is the upstream data center, so it can legitimately differ from the route name shown in the client.
04 · Proxy detection
Flagged as a data center?
Some sites check whether the exit address belongs to a known data center range. A flag doesn't mean the route is unusable — it only means the address is identified as data center space. If a streaming or AI service says your region is restricted, switching to another route works better than refreshing the same address over and over.
DNS check
DNS leak self-check steps
A changed exit IP doesn't mean domain lookups also go through the route. The five steps below separate two cases: the route isn't working, or lookups still resolve locally.
Disconnect, then reconnect
Disconnect the current route in the client, wait a few seconds and connect again. Reconnecting pushes the DNS configuration down again, and some lookup problems disappear right after.
Come back to this page and check the exit
Click Check again at the top of the page and confirm the exit IP matches the region of the chosen route. This only verifies where traffic exits — it doesn't prove lookups use the route too.
Make sure DNS follows the route
Open the client settings and leave DNS at its default, or set it to follow the route. If you previously entered your local carrier's address by hand, reset it to default and reconnect once.
Retest on a different route
If the lookup region and the exit region disagree twice in a row on the same route, test another route in a different region. If results are normal on the new route, the problem is in that route's configuration.
Write down what you saw
Once you've confirmed it's a route problem, note the route name, the time it happened and both lookup results, and attach them to your ticket. Complete details make it much faster to pin down.
| Symptom | Likely cause | What to do |
|---|---|---|
| Exit IP is still the local carrier | The client isn't connected, or routing rules exclude this browser from the proxy | Check the connection status, switch the rule mode to global and test again |
| Exit IP is correct, but lookups still resolve locally | DNS wasn't pushed down with the route | Set the client DNS to follow the route, disconnect and reconnect, then test again |
| Exit IP doesn't match the chosen route's region | The client is still on the previous route | Disconnect and reconnect, then confirm the current route name and region |
| The page says results are temporarily unavailable | The endpoint is temporarily unavailable, or this network can't reach the site | Try again later; first confirm other pages on this site load normally |
FAQ
Lookup and troubleshooting Q&A
If a result looks wrong, read these first before opening a ticket.
Why is the result different from the IP my browser shows?
This page reads the current network exit; a browser extension may be caching an old result or routing through its own proxy layer. Disable the extension and look up again — if it still differs, trust the result returned by this page's endpoint.
Why does it say results are temporarily unavailable?
The endpoint returned no data. Common causes are that this network can't reach the endpoint, the request timed out, or the endpoint is briefly down. Click Check again later; if it keeps failing, confirm other pages on this site load, then judge whether the problem is on the network side.
Does the lookup record my IP?
Results on this page are shown for this visit only and are not written to a query log. An IP address is basic network information every site sees when a connection is made; this page doesn't store it separately or reuse it.
If it says proxy detected, is the route unusable?
No. It only means the exit address is identified as a data center range. Some streaming and AI services restrict access on that basis; when you see such a notice, switching routes usually works better than refreshing the same address.
The exit IP didn't change after connecting — is the route broken?
Most often routing rules exclude the current app from the proxy, or the client is still on the previous route. Disconnect and reconnect, check the rule mode, then test another route — if it still fails after those three steps, open a ticket.