My IP and Network Egress

What This Information Means

Your public IP is the address websites see

This is the public IP address identified by our service when it received this browser request. It isn't your device's address on your local network. When you use an acceleration route, websites may see the route's exit IP. With split tunneling, this lookup and other websites may also use different routes. This result reflects only the connection used for this request, not how every app connects.

Geolocation and ISP data don't pinpoint your location

Country and region are usually determined using IP address databases. The ISP identifies the network provider associated with the address. Database updates, address transfers, and network configurations can all affect the results. These details don't confirm your device's actual location, and the provider name alone can't tell you a route's speed, reliability, or access availability.

Proxy detection needs to be considered alongside your connection

We show “Proxy detected” or “No proxy detected” only when our service explicitly provides a proxy assessment. If that information isn't available, you'll see “Temporarily unavailable.” No proxy detected doesn't mean your traffic isn't using an acceleration service. A proxy detection doesn't indicate a connection problem, and it can't determine whether you can access a particular streaming or AI platform.

How to Check for DNS Leaks

DNS translates domain names into network addresses. A change in your public IP doesn't necessarily mean DNS requests are following the expected route. This page only looks up your public IP details; it doesn't run a DNS leak test or treat a successful IP lookup as proof that DNS is working as expected.

1. Confirm the expected route. Check the client's DNS and split-tunneling settings to see whether domain lookups should use your system, local network, or the route's DNS service. Different rules may send domains in mainland China and international domains over different routes.
2. Check your browser settings. Secure DNS or encrypted DNS in your browser may use a different provider than your system. If the browser specifies a DNS provider, check that it matches your connection setup instead of changing only the system settings.
3. Check which DNS provider is actually used. For a more detailed check, use a trusted DNS testing tool and read its privacy policy first. Compare the DNS providers it reports with the settings expected for your client. A DNS server's country alone isn't enough to confirm a leak.
4. Verify again after making changes. Connect to your chosen route, close the old page, and run a new test. If the results still don't match your expectations, note your client mode and relevant settings, then report the issue through the user dashboard ticket system. Don't include subscription links or account passwords.

System and browser caches, as well as app-specific DNS settings, can all affect what you see. When troubleshooting, change one setting at a time and test the same destination again to identify what caused the change.