Network Check
Open this page to see your current exit IP, country and ISP, then run a DNS leak self-check with the steps below. Lookups go through our own same-domain endpoint, and query contents are never logged.
Exit IP
Loading…
Country / Region
Loading…
ISP / Network
Loading…
Proxy check
Loading…
Data comes from our own same-domain endpoint. If the endpoint doesn't respond, the four fields show “Temporarily unavailable” — there is no third-party public API fallback.
Reading the results
The four fields describe different sides of the same exit: address, ownership, network and public flags. Only by reading them together can you tell whether the route is actually in effect.
The address other sites see when this device reaches out. Once a route is connected it becomes the address of the landing node; disconnect and it reverts to the address your local carrier assigned. Check this one first when you want to know whether the route is really working.
The registered location of the exit IP. Many sites use it to choose interface language, currency and content region, so when it doesn't match the node you picked, pages will behave accordingly.
The network operator or data center that owns the exit IP. Seeing a data-center name is normal: routes land in data centers. If your local carrier's name shows up here instead, traffic is usually not going through the route.
A flag derived from the public registration records of the IP block — reference only. It reads address attributes, not the behaviour of this device; a hit doesn't mean the route is unusable, and a miss doesn't mean it suits every site.
Your exit IP and your local IP are not the same thing. The local IP is the address your carrier assigns to this connection; the exit IP is the address traffic presents to the outside world after it leaves the route's landing point. This page reads the latter, so if it changes, traffic really did take a different exit.
Self-check steps
A correct exit IP doesn't guarantee your DNS queries follow it. A DNS leak means resolution still goes out over the local network instead of through the route's landing point. The five steps below need nothing more than this page and your system settings.
A DNS leak won't stop pages from loading, but it exposes your resolution requests to the local network and can make some sites show content for your local region. The point of a self-check is to confirm that resolution follows the same path as your route, not to chase a pretty result on any one test.
Privacy
Lookup requests from this page go to our own same-domain endpoint. Nothing redirects to a third-party domain, and your IP is never handed to an address outside this page. Results are shown on this page only: they aren't written to your account and aren't tied to sign-in status — you can run a lookup without being signed in.
This service keeps no logs. Lookups are used only to render the result back onto this page — nothing is retained, and nothing feeds profiling or ad targeting.
Clicking “Copy IP” only writes the current exit IP to the system clipboard and sends no extra request; the clipboard is managed by the operating system, and this page can't read it back.