Same-site lookup with no third-party public services
This page reads publicly available network information about your current connection to show where traffic exits the network, which provider the address belongs to, and whether the endpoint detects proxy indicators. The result applies only to this lookup and does not mean other apps use the same route.
Connection result
Fetching current connection details through this site's endpoint.
Understanding the results
GeoIP results can help confirm your exit location and network ownership, but different databases may update at different times. If the city or region is inaccurate, treat it as a database classification rather than the device's precise location.
This is the public address visible to websites. After connecting through an international route, the public IP should generally match the destination region of the selected route. If your browser and other apps show different results, they may be using different per-app rules, system proxy scopes or connection methods.
The country or region comes from the database associated with the public address; the ISP is the network provider registered for or identified with that address. After a data-center, relay route or address range changes, databases may need time to update, so use the result as a troubleshooting clue.
The endpoint may identify proxy signals based on the address type and network characteristics. “Not detected” does not rule out every forwarding method, while “Detected” does not by itself indicate a connection problem. Consider the exit region, the actual app route and the route's purpose together.
Connection self-check
Your public IP and DNS provide two different diagnostic clues. A changed public address does not automatically mean DNS queries follow the same route. This page's GeoIP result alone cannot determine whether DNS is leaking; compare your system network details before and after connecting.
Pay particular attention to whether the DNS servers still point to your original network provider and whether the connection client has taken over DNS resolution for the system or browser. Secure DNS enabled in the browser may also produce results that differ from the system settings.
Open your system network details, check the current DNS configuration, and note the country or region and ISP associated with your public IP. This gives you a baseline for comparison after connecting.
Reopen this page and refresh the results, then check the DNS entries in your system network details. Refreshing alone may be affected by the existing connection cache; reopening the browser makes troubleshooting easier.
If your public IP has changed but DNS still clearly points to the original network provider, check the client's DNS takeover, system proxy scope and split-routing settings.
Browsers, desktop apps and system services may use different DNS resolution methods. If only one app has access problems, check that app's network and Secure DNS settings separately.