Public IP Lookup

What this information means

Public IP: where this request came from

The public IP is the source address seen by the lookup API. After connecting a client, it may differ from your network's original egress. With rule-based routing, VPNTrain and the target app may use different rules, so this result can't replace checking the target app's actual connection.

Location and ISP: reference details for the IP address

Location is based on IP geolocation databases, not your device's location. IP assignments, provider changes, and database updates can all affect accuracy. ISP usually refers to the network provider or address holder associated with the IP. Its name may differ from your selected route and doesn't by itself indicate a connection problem.

Proxy detection: not proof a platform will work

Databases may classify proxy and data center IP addresses differently. The result shown here can't confirm that a particular streaming service or AI tool will work, and doesn't replace the target platform's own location or account requirements. To troubleshoot access, first check the active route and routing rules in your client, then review the message shown by the service.

After switching routes: Wait for the client to connect, then click “Run lookup again.” If the egress hasn't changed, check whether requests to VPNTrain match a proxy rule and whether your browser has a separate proxy configured.

DNS Leak Check

DNS translates domain names into network addresses. Even when web traffic uses your selected egress, DNS queries may take a different path. This tool only checks egress details; it does not run a DNS leak test or automatically conclude that there is “no leak” based on your egress location.

1. Check your client settings. Review DNS, system proxy, or tunnel mode settings to confirm that domain lookups are handled as intended. Setting names vary by client and version.
2. Check your browser settings. See whether Secure DNS or encrypted DNS is configured to use a separate resolver. Browser settings may differ from your system or client settings, so checking the system DNS address alone isn't enough.
3. Check the resolver and query path. Use your operating system's network diagnostic tools to review DNS settings and actual queries. The local resolver address shown by the system may only be a forwarding endpoint. Check the client's DNS forwarding settings too; don't draw conclusions from the resolver name or location alone.
4. Compare with your intended setup, then test again. Confirm which domains should connect directly and which should use a proxy. After changing settings, reconnect and try again. If you use a separate DNS testing tool, read its data handling policy first; this page does not send requests to external test services.

If you're still unsure, describe your operating system, client settings, and the circumstances in which the problem occurs in a support ticket in the user portal. Before sharing screenshots, hide subscription links, passwords, and other account details.