NETWORK CHECK
View the public address, location, ISP, and proxy detection status currently used by your browser. Results come from this site’s same-domain lookup API and do not connect to third-party public lookup services.
CURRENT EXIT
RESULT GUIDE
The lookup card shows the network information visible to external services after your browser’s request leaves your local network. It can help confirm whether a route switch took effect, but it does not represent your complete privacy status on its own.
This is the address a website sees when it receives your request. After connecting to a VPNDG route, run the lookup before and after switching and compare the results. If the address changes, the current web request is using a different network exit.
The location is based on registration records and geolocation database mappings for the network address; it is not the device’s precise location. Database updates can lag, so the city or region may differ slightly from the actual data center location.
This field identifies the network organization associated with the public address. After connecting to a route, the displayed name may belong to a data center, cloud network, or carrier, helping indicate what type of network exit handled the request.
The result is based on network characteristics returned by the API. Detection criteria vary between databases, so “not detected” does not provide an additional privacy guarantee, while “detected” does not mean the connection has failed.
DNS CHECK
DNS converts domain names into network addresses. Even when web traffic uses a new public exit, the domains you visit may still pass through the original resolution path if DNS queries are handled by the original network provider.
This page only reads public-exit information returned by a GeoIP API and does not run an external DNS probe. It therefore does not present a standard IP lookup as a DNS test. Use the method below to check for leaks yourself.
Disconnect from the accelerated route first, then record the resolver’s network and region in a trusted DNS testing tool. Do not publicly share complete screenshots containing personal network information.
Connect to the required route and refresh the test results. If the original network provider’s DNS servers continue to appear, check the client’s DNS settings and reconnect to the route.
If your public IP has changed but the resolver has not, check the DNS settings in your system, browser, or client. These two types of information should be verified separately; neither alone is enough to draw a conclusion.