Public IP Lookup

What These Results Mean

Public IP: where this request reached our service from

The IP shown is the source address seen by our endpoint, not your device's address on its local network. When network acceleration is enabled, only browser requests routed through the selected connection will show a corresponding change. Per-app proxies, split-tunneling rules, and browser proxy settings can send browser traffic and other apps along different paths.

First, check your IP without a route connected. Then connect to the route you want to test and select “Check Again.” A changed IP means this browser request took a different route; it doesn't confirm that other apps use the same one. To check an AI tool or video service, verify access within that app or service.

Location and ISP: network ownership in IP databases

The country or region shown is an IP database's estimate of network location, not your device's live location. Address assignments, changes by network providers, and delayed database updates can all lead to inaccuracies. The ISP usually identifies the provider or network organization associated with the exit point. After connecting through a route, it may show a data center's network name rather than your current access provider.

Proxy detection: an indicator, not a connection verdict

This page shows “Proxy detected” or “No proxy detected” only when the endpoint explicitly provides a proxy result. If that field isn't returned, the result is “Temporarily unavailable.” Detection depends on the database and its criteria, so it can produce false positives or miss proxies. “No proxy detected” doesn't mean you're not using an acceleration route or indicate how well your privacy is protected.

DNS Leak Check

DNS translates domain names into network addresses. If you expect both DNS lookups and web traffic to use an acceleration route, but DNS requests still go through your local network, the DNS path may not match your expectations. This page's GeoIP lookup doesn't test for DNS leaks, and your public IP alone can't show where DNS requests are sent.

1. Confirm your intended routing. Check the proxy mode and DNS settings in your client first. Determine whether it handles selected apps, routes traffic by rules, or covers all device traffic. Keeping DNS requests local under split-tunneling rules isn't necessarily a problem; compare the behavior with your configuration goals.
2. Check your system and browser settings. Review the DNS configuration in your system's network settings, then check your browser's Secure DNS settings. Browsers may use a separate encrypted DNS channel, so system settings alone won't show what the browser is actually doing.
3. Check DNS resolution after connecting. If your client provides DNS request or connection logs, check them while opening the domain you want to test. On Windows, run nslookup example.com; on macOS or Linux, run dig example.com to see what the command-line resolver returns. These commands don't show a browser's separate DNS resolution path.
4. Adjust your settings and test again. If the observed path doesn't match your expectations, check DNS routing, split-tunneling rules, and browser settings using your client's guide, then reopen the service you're testing. With virtual DNS addresses or local forwarders, a local address in the logs may not be the final upstream resolver; consult your client documentation.

A DNS server name, its reported location, or a single lookup isn't enough to determine whether a leak occurred. For further help, visit the Support page for connection guidance, or submit a support ticket in the user panel with your intended route, current mode, and the issue you're seeing.

Privacy and Limitations

Queries aren't logged. Checks run through a same-origin endpoint on this site. Your browser sends a request to that endpoint to retrieve results, and the request itself includes your current public IP. This page's scripts don't save results to local storage. Copying happens only when you select “Copy IP.”

If the endpoint is unavailable, this page shows “Temporarily unavailable” and won't switch to a third-party lookup service. Check your connection, then run the check again manually. Before sharing screenshots or troubleshooting notes, check for IP addresses, account details, and subscription information. Never share your password or subscription link. See our Privacy Policy for details.