OUTPOST / IP-LOOKUP
Reading public network information
- IP address
- Loading…
- Country or region
- Loading…
- ISP / network provider
- Loading…
- Proxy detected
- Loading…
NETWORK COORDINATE / GEO LOOKUP
My IP and public location
Shows the public address your browser uses when accessing this site. Use the result to verify the route location, ISP, and proxy detection signals.
FIELD NOTES / INTERPRETATION
What these results mean
Compare the results with your selected route, field by field. Each field answers a different question.
Public IP
This is the network address visible to websites and online services. Run the lookup again after changing routes to confirm whether the public address changes.
Country or region
The location is based on IP registration and geolocation data, making it useful for checking the approximate region of your public IP. It is not your device’s exact location and may be affected by update delays.
Network provider
This field identifies the network organization associated with the public IP. After connecting to a route, it should generally correspond to the current public network.
Proxy detection signal
Some address ranges are identified as proxies, hosted networks, or data centers. Results depend on the detection database and should be assessed alongside the IP, location, and actual connection status.
DNS CHECK / MANUAL ROUTINE
DNS leak check
An IP lookup confirms only the public address used for web requests. DNS requests may take a different path, so the resolver must be checked separately.
Confirm the target route
Connect to the route you plan to use, then return to this page and run the lookup again. Record the public IP, country or region, and ISP for comparison.
Check the DNS resolver
Use your system’s network diagnostics to check the current DNS servers, or run nslookup example.com in a terminal and review the server information in the output.
Compare location and source
Compare the DNS server’s network source with the public information shown here. If the resolver still clearly belongs to the original ISP, review the client’s DNS and tunnel settings, then disconnect and reconnect.