Same-Origin GeoIP Lookup
IP Address & Network Check
View the public address, network details, and proxy signals currently used by your browser. Results come from this site’s same-origin API and are intended only to troubleshoot connection paths.
NETWORK / GEOIP
Checking
Current Public IP Details
Network Details Unavailable
The site’s GeoIP API could not return a result. Please try again later; this page will not fall back to a third-party public API.
Understanding the Results
What These Details Mean
The results card shows the public address used when your browser’s request leaves the network. It is not the same as your device’s local network address.
Public IP
This is the public address that target websites can typically see. After switching routes, run the check again to confirm whether the public IP has changed. If it has not, first verify the client connection, then check whether the browser is still using the previous session.
Location
The location is inferred from the public address using a GeoIP database and is useful for identifying the approximate region of the route. Address assignments and database updates can differ in timing, so this indicates network ownership rather than a precise physical location.
ISP
The ISP field identifies the network operator or autonomous system associated with the public address. Cloud networks, home broadband, and business networks may show different organization names, providing additional context about the route’s exit type.
Proxy Classification
This result comes from address classifications in the GeoIP data. “Detected” means the database has labeled the current exit as a related network type; “Not detected” does not establish a privacy or security conclusion. Classifications for shared exits, business networks, and cloud networks may change as the database is updated.
DNS Self-Check
How to Check for DNS Leaks
A public IP that matches expectations does not necessarily mean domain lookups use the same path. A DNS self-check should verify both the connection settings and the ownership of the DNS resolver.
Confirm the public route
After connecting, refresh this page and confirm that the public IP and location have switched to the expected region. If the public IP itself has not changed, resolve the connection issue before checking DNS.
Check the DNS resolver
Review the DNS settings in your client or system network settings, then use a trusted DNS testing tool to verify the resolver’s ownership. If DNS requests are still handled by the original network provider while the public IP has switched to another region, the paths may not match.
Review browser settings
Some browsers enable Secure DNS independently, which can bypass system settings. During troubleshooting, make sure the browser and client policies are consistent. After changing settings, close old pages and run the check again to avoid cache-related results.
Assess the results together
Ideally, both the public IP and DNS resolution path should match the current connection settings. If their network ownership differs significantly, reconnect the route, update the client configuration, or check for leftover network settings in the operating system.
PRIVACY NOTICE
Query Privacy
To determine the ownership of your public IP, the address must be sent to this site’s same-origin GeoIP API. NeuVPN does not record the results from this page and will not forward requests to a third-party public lookup service if the API fails.