Browser egress · Network diagnostics
Public IP
Network Check
Check your browser’s current public IP, then confirm whether your connection is working as expected. This shows the network details seen by our API when your request reaches it—not the route used by every app.
Current connection details
Waiting for lookup- Public IP
- Country / region
- Temporarily unavailable
- ISP / network provider
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Enable JavaScript to run the lookup automatically, or use the button to check again.
Run another lookup after switching routes. This page doesn’t refresh continuously or access your clipboard automatically.
What these results mean
Public IP: the address seen by our API
Your public IP is the public source address seen by our API, not your device’s address on the local network. Copy the result before connecting for comparison, then run another lookup and check whether the address and expected location have changed. If not, confirm that your client is connected and your browser is routed through the intended route.
Country / region and ISP: database classifications
Location comes from an IP database, not device geolocation. Database updates may lag, and different websites may show different locations. The ISP usually refers to the provider or data center network associated with the public IP, not necessarily your local broadband provider. A matching location also doesn’t guarantee that a website will classify it the same way.
Proxy detection: an indicator, not a verdict
Proxy detection relies on a flag returned by the API. “Proxy detected” doesn’t tell you whether your connection is secure, and “No proxy detected” doesn’t mean you aren’t using an accelerated route. If the API doesn’t return this field, we’ll show “Temporarily unavailable” rather than treating missing data as a negative result.
View routes and learn how to choose one → · Get help with connection issues →
DNS Leak Check
DNS translates domain names into network addresses. If DNS requests don’t follow the expected route, they may use another network even when your web traffic exits through a different IP. This page’s GeoIP lookup doesn’t test DNS, so it can’t confirm that there are no DNS leaks.
- Confirm the expected route. Check your client’s DNS and routing settings to see whether it should handle DNS requests. Note whether your browser uses its own Secure DNS setting and whether your system has a custom DNS provider configured.
- Check DNS records after connecting. Look in your client’s connection logs or DNS logs, if available, to see where requests go when you open a domain. If the client doesn’t provide this information, check the current DNS configuration in your system’s network diagnostics. The configuration is only a clue, not a substitute for actual request logs.
- Compare the resolver and exit location. If you use a trusted DNS test, read its privacy policy and check whether the DNS provider matches your configuration. A resolver in a different location from your exit IP doesn’t necessarily indicate a leak; public DNS networks and encrypted DNS can produce this difference.
- Test again after making changes. Check for conflicts between your browser’s Secure DNS, system DNS settings, and the way your client handles DNS. Adjust them according to the client’s instructions, clear relevant caches, then repeat the test. Don’t disable security features just because you see an unfamiliar provider.
Lookup Privacy and Result Limitations
We don’t log queries. This page uses our GeoIP API to retrieve information about the current request. It doesn’t use a third-party public lookup API as a fallback or proactively upload lookup results. Clicking Copy only writes the current public IP to your clipboard.
Results stay on this page and are replaced when you run another lookup. If the API is unavailable, we’ll show “Temporarily unavailable”—never a sample IP or an estimated location. Before sharing a screenshot, consider whether you need to reveal your public IP.