Public IP
Websites typically use the public IP to determine where a request comes from. If the address changes after connecting to a different route, the network exit used by the browser has changed.
Current connection · Same-origin lookup
Public IP and DNS check
Reads the network exit used by the current request and displays the IP, location, ISP, and proxy status. If the lookup fails, the page only shows “Temporarily unavailable.”
Check results
Current network exit
Fetching network information through this site’s endpoint.
Public IP
Loading…
- Location
- Loading…
- ISP
- Loading…
- Proxy detection
- Loading…
Understanding the results
What this network information means
The result describes the exit used when the current browser request leaves the network. It is not the device’s local network address.
Location
The location comes from network address data and is useful for checking the approximate region of a route exit. Data may be updated with a delay, so city-level results should not be treated as precise location data.
Internet service provider
The ISP field identifies the network operator associated with the address range. Different routes may show a data center, backbone network, or local access provider.
Proxy detection
This field is based on the interface’s identification of the address attributes. Databases may contain omissions or delayed updates, so use the result only as a troubleshooting reference, not as a conclusion about connection quality.
Connection check
DNS leak check
The public IP and DNS resolution path are separate matters. Browser requests may use the selected route while domain resolution still uses the original network. Check both together when testing for leaks.
-
Keep the current connection active
First complete the public IP lookup above and note the location. Do not switch routes or networks during the check, or the results may come from different connections.
-
Review your system’s DNS settings
Check the active DNS servers in your operating system’s network details, client connection logs, or browser Secure DNS settings. If the client uses automatic split tunneling, also verify that the DNS rules take effect with the selected route.
-
Compare the exit and resolution paths
If the exit is in the selected route’s region while DNS still clearly points to the original access network, check the client’s DNS takeover, system proxy mode, and browser Secure DNS settings.
-
Reconnect after changing settings
After adjusting the settings, disconnect and reconnect, then run the public IP lookup again and review the DNS settings once more. The comparison is meaningful only when both checks use the same route.
Privacy notice
Anonymous, no-log lookup details
Results are shown only on this page
Lookup requests are sent only to this site’s same-origin endpoint. This site does not record lookup results or fall back to third-party public lookup services when the endpoint fails. After you close or refresh the page, the current result is not retained by this page.