IP Lookup and Connection Check

What These Details Mean

Public IP: where this request enters the internet

This is the source address our API sees for your request, not your device’s local network address. Run a lookup before and after connecting to a route to see whether your public IP changes. If your client uses rule-based routing, requests to this site may take a different path from traffic to your target app. The result only describes the route your browser uses to reach this site.

Country / Region and ISP: check the reported location

Location is generally estimated using IP databases. Data may be out of date, and the reported location doesn’t necessarily match your device’s physical location. The ISP is the provider identified by the database; it may show a data center or upstream network rather than S4VPN. To check whether a route is working as expected, consider both the region selected in your client and the target service’s actual behavior.

Proxy Detection: an indicator, not a verdict

“Proxy detected” means the API flagged this public IP as a proxy. “No proxy detected” means only that this lookup returned no such flag; it doesn’t prove your traffic isn’t routed through a proxy. If the API doesn’t provide this field, the page shows “Temporarily unavailable” rather than treating missing data as a negative result.

DNS Leak Check

DNS translates domain names into network addresses. A changed public IP doesn’t mean DNS requests are using the same network route. This page’s API only returns details about the current request; it can’t list the DNS servers that actually resolve domain names.

1. Note your settings before connecting. Check the DNS settings currently used by your system, and see whether your browser has Secure DNS enabled separately. Your system and browser may use different resolution methods.
2. Check your client settings after connecting. Confirm that DNS interception or remote DNS resolution is enabled as described in your client’s instructions. Changing the system proxy alone may not route DNS requests from every app on your device.
3. Check the actual DNS route. For further verification, use a trusted, dedicated DNS leak test or review your client’s DNS request logs. Compare the DNS servers in use with your expected settings; a different server name or reported location alone doesn’t prove a leak.
4. Test again after making changes. Reconnect after adjusting your settings, then reopen the app you want to check. If you still have questions, submit your operating system, client settings and steps to reproduce the issue through a support ticket in the dashboard. Hide account credentials before sharing screenshots.

Don’t conclude there’s a leak solely because the DNS server and public IP are reported in different regions. Public DNS services may use distributed networks, and database labels may vary. Check whether requests are taking the expected route rather than comparing region names alone.