First check where your current request is coming from, then review your routing and DNS settings. This shows the egress used when your browser visits this site; other apps may use different routes.
Enable JavaScript to run the lookup automatically, or click “Check again.”
Proxy detection is based on classification data returned by the API. It does not confirm that a connection is working or that your privacy is protected. If the relevant data is unavailable, this field will show “Temporarily unavailable.”
Assess your IP location, network provider, and app routing separately.
Your public IP is the address this site’s API sees as the source of your request. Its country or region is usually estimated using an IP database, which may be out of date and cannot pinpoint your device’s exact location.
Run another lookup after switching routes to see whether your browser’s public IP changes. If it stays the same, first check whether your routing rules send this site through a direct connection.
The ISP field identifies the provider or network organization associated with your public IP. When using a route, it may show a data center or upstream network instead of your local internet provider.
“No proxy detected” doesn’t mean you aren’t using one, and “Proxy detected” doesn’t mean the route is faulty. Results depend on the database and its classification methods.
The result applies only to this request. System proxy settings, routing rules, app-specific proxies, and tunnel modes can send different apps through different connections.
To check AI Tools or Streaming, also test the connection within the relevant app. An expected IP location doesn’t guarantee that a particular platform will work.
This page checks your public IP, not for DNS leaks. A changed public IP alone doesn’t confirm where your DNS requests are going.
Check whether international domains are resolved through the expected route in your current mode. Split tunneling can send different domains through different DNS paths, so checking whether the system proxy is enabled isn’t enough.
Encrypted DNS configured in your browser may follow a different policy from your system or client. Note the current settings and compare them with your client’s documentation. Avoid leaving encrypted protection disabled just to troubleshoot.
If you use a dedicated DNS test, compare the organizations associated with the resolvers against your expected policy. A difference between the resolver’s location and your egress location alone doesn’t prove a leak; public DNS services may use distributed servers, and databases can be inaccurate.
If only one app has an issue, first check its network settings, routing rules, and cache. If the connection is established but access still isn’t as expected, see the Public IP and DNS Testing Guide or consult Routes and Protocols.
A failed lookup on this page means only that no result could be retrieved; it doesn’t mean your connection is down. Check your network and try again later. This page won’t fall back to a third-party public API.