Connection Check / Current Browser IP

IP Lookup & 出口核对

See where this browser request is coming from. After connecting to or switching routes, run the lookup again and compare the result with the exit location selected in your client.

Current IP Details

Lookup via U6VPN API
Public IP
Waiting for lookup
Country / Region
Waiting for lookup
ISP / Network
Waiting for lookup
Proxy detected
Waiting for lookup

Getting ready to retrieve your IP details via U6VPN’s API.

This result applies only to this browser request, not every app on your device. This page does not run a DNS leak test.

What These Results Mean

Public IP and Location

Your public IP is the address seen by U6VPN’s API. When you use a proxy route, it is usually the route’s exit address, not your device’s local address.

Location data comes from an IP database and may be out of date. If it doesn’t match your selected region, first check whether your browser is using the proxy, then run the lookup again. IP geolocation alone can’t tell you where a route’s physical infrastructure is located.

ISP and Network Ownership

The ISP field identifies the network provider or organization associated with the address. After you connect to a route, it may show a data center or network provider instead of your local broadband ISP.

This field is not a speed rating and can’t confirm that an AI tool or streaming platform will work. Check access directly in the service you want to use.

Limits of Proxy Detection

Proxy status comes from the API’s detection data. A proxy being detected doesn’t mean your connection has a problem; no proxy being detected doesn’t prove that all your traffic is going directly to its destination.

“Temporarily unavailable” means the API didn’t provide a result that could be interpreted; it does not mean “no proxy detected.” Check your account region, platform rules, and network exit separately.

Checking DNS and Resolution Paths

DNS Leak Self-Check

An IP lookup and a DNS leak test are not the same thing. This page shows the exit address for web requests, but it can’t tell you which servers handled domain lookups. A location that matches your expectations doesn’t mean DNS requests followed the same path.

  1. Check your client’s DNS settings. See whether the client handles domain resolution and how your current routing rules handle DNS. Setting names vary by platform; a “connected” status alone isn’t enough to verify your configuration.
  2. Check your system and browser DNS settings. Secure DNS in your browser, a custom resolver, or other network software may use a different path from your client. Note your original settings before making changes so you can identify the cause if something goes wrong.
  3. Use DNS logs to verify resolution. If your client provides DNS logs, check how requests are handled when you visit the site in question. If you use a tool that can identify DNS resolvers, interpret its results in light of your client settings; a resolver’s country alone doesn’t prove a leak.
  4. Verify the changes. Restart the relevant connection, revisit the site, and check your IP and DNS logs again. If you still have questions, describe what you did in a support ticket in the user panel. Don’t submit your password or full subscription link.

In split-tunneling mode, some requests may connect directly according to your rules. Whether that’s expected depends on the access you need and your actual routing rules; not every request has to come from the same region.

Lookup Privacy and Scope

U6VPN does not log queries. Lookups use an API on the same domain and are not forwarded to third-party public IP lookup services. If the API is unavailable, you’ll see an error; sample addresses are never shown in place of real results.

The copy button copies only the public IP retrieved for this lookup; it does not copy your account details or client configuration. Before sharing a screenshot, check that it doesn’t reveal network information you’d rather keep private. For details, see the Privacy Policy.