After switching routes, check where your browser is accessing the internet from. This shows the egress IP for this request; other apps may use a different route.
Checking… Please wait.
Proxy status comes from the category returned by the API. It isn’t a security rating, and no proxy detected doesn’t necessarily mean your route isn’t active.
Websites typically see the public IP address used when a request leaves the network, not your device’s local address. Check before and after connecting to see whether your browser’s egress IP changes.
If the address hasn’t changed, check your client’s connection status and routing rules. This page may be set to connect directly, and other apps may use different proxy settings.
The location is an estimate from an IP address database; the ISP is the provider associated with that address. Neither necessarily reflects your device’s actual location or shows the brand of your current subscription service.
IP databases can take time to update. Different sites may identify the same address differently, and platforms may also use account region or other information to determine access.
“Proxy detected” means the API classified the current egress IP as proxy-related. It doesn’t identify the route type or indicate connection quality.
“No proxy detected” means only that the IP didn’t match that category. If the API returns no result, this page shows “Unable to retrieve results” rather than treating missing data as a negative finding.
DNS translates domain names into network addresses. This page checks egress information only; it doesn’t test DNS automatically or report that a leak test has passed.
Check which service handles DNS lookups in the current mode and whether DNS requests follow the expected route. A “Connected” status alone doesn’t show where DNS requests actually go.
Check for custom system DNS, Secure DNS in your browser, and other network tools that may also handle DNS. Understand what each setting does before making changes, and follow your client’s instructions to avoid overlapping configurations that make request routing harder to determine.
If you use a DNS testing tool of your choice, read its data-handling policy. Check whether the listed DNS providers are what you expect. A DNS server in a different location from your egress IP doesn’t necessarily mean there’s a leak; public DNS services may operate across multiple regions.
After making changes, reopen the target app and check the egress IP and DNS route again. Change one setting at a time to make differences easier to pinpoint. DNS cache may also affect results; follow your system or client’s instructions for clearing it.
We don’t log queries. Checks are made through our API. Results aren’t saved to your browser’s local storage, and if the API fails, we don’t switch to a third-party public API.
The copy action runs only when you click “Copy IP.” Before sharing a screenshot, check for your public IP and ISP details, and share only what’s needed to troubleshoot. See our Privacy Policy for details on data handling.