What Is My IP?

Public IP: the address seen by this site

Your public IP is the address used when this request reaches our site. Check it before and after connecting to see whether it changes. If your browser uses a proxy while other apps connect directly, they may have different public IPs. With split tunneling, this site may also use a direct connection.

Location and ISP: clues from IP records

Your country or region and ISP can help identify the connection’s exit point. The ISP field may show a data center or network operator rather than your current access provider. Database updates can lag, so these results can’t pinpoint your exact location or replace a destination website’s own regional checks.

Proxy detection: a clue, not proof of connection status

“Proxy detected” means the lookup service identified this connection’s exit point as a proxy. “No proxy detected” means only that it wasn’t identified this time; it doesn’t prove the connection is unencrypted. If the service returns no detection data, this page won’t treat the missing value as “No proxy detected.” Check your client’s status and whether the destination service is accessible to confirm the connection.

DNS translates domain names into network addresses. If you want DNS queries to use your selected route but they’re still handled by your local network’s resolver, check the DNS path. A difference between the resolver’s location and your public IP location isn’t, by itself, a leak. Consider your client mode and browser settings too.

1. Confirm the expected route. Open your client and check the selected route and proxy mode. Split-tunneling rules may let some domains resolve or connect directly. First check whether that’s intentional.
2. Check your client’s DNS settings. See whether DNS interception or remote resolution is enabled. Setting names vary by platform; follow your client’s documentation, and don’t enable options you’re unfamiliar with.
3. Check your browser’s Secure DNS settings. A browser-selected resolver may differ from your system or client settings. Note the original setting before making changes, so you can restore it if needed.
4. Reconnect and check again. Follow your client’s instructions for clearing the DNS cache, then reopen the destination page. Check where queries are going using your client’s connection logs or system network diagnostics. If you use a separate testing tool, read its privacy policy first. This page does not automatically send requests to external testing services.

If your public IP still doesn’t match your expectations, first check whether your site’s domain is covered by a direct-connection rule, then review your client’s system proxy or tunnel settings. For setup instructions, see Guides. To gather troubleshooting details, see Frequently Asked Questions.