NETWORKRequest routed through your browser

YGVPN IP Lookup

Check your public IP and its location, then confirm whether your connection is working as expected. This test reflects only the current request from your browser, not the network route used by every app on your device.

Current connection details

Waiting for lookup
Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Preparing to query our API.

What this information means

Public IP and location

Your public IP is the address our API sees as the source of your request, not your device’s local network address. Run the test again after connecting to a route to check whether your public IP has changed. Location is based on an IP geolocation database, which may not be up to date. It does not pinpoint your device or determine how a destination service classifies your region.

ISP and proxy detection

ISP usually refers to the network provider or organization associated with an IP address; the result may show a data center. Proxy detection relies on database labels: a proxy result doesn’t mean your connection is malfunctioning, and no result doesn’t prove that you aren’t using a proxy. If the API doesn’t provide this field, the page will say it’s temporarily unavailable.

DNS Leak Check

A public IP lookup and a DNS test are not the same thing. Our GeoIP API can’t list the DNS servers that actually handled your requests, so this page won’t automatically label the result as a pass or a leak.

From client settings to DNS results

  1. Note your connection mode. Check whether you’re using system proxy or tunnel mode, and review your client’s DNS settings and routing rules. If only your browser is using a proxy, other apps may still resolve domain names over your usual network.
  2. Check your browser’s DNS settings. Secure DNS and custom DNS services in your browser may differ from your system settings. Confirm they match your client’s instructions. A changed public IP alone doesn’t mean your DNS traffic is taking a different route.
  3. Check which resolvers are in use. To investigate further, choose a DNS test tool you trust and run the same test before and after connecting. Note the resolver names and associated networks. Read an external tool’s privacy policy before using it; this page does not automatically send requests to third-party testing services.
  4. Consider the resolver’s network. A resolver’s reported location may reflect nearby routing and database labeling, so it doesn’t have to match your public IP’s location. If you still see a resolver associated with your local network and that doesn’t match your configuration, check your DNS routing and client settings.

After changing settings, reconnect and repeat the same test. If the results don’t match, submit a ticket through the user dashboard with your client platform, connection mode, and a description of the issue. Don’t include your password or subscription link.