Current network egress

Public IP check

First confirm where your traffic exits the network, then review the location, ISP, and proxy detection results. This page only requests VPNYE’s own-domain API.

Network egress check

Checking

Public IP

Loading

Country / Region

Loading

Internet Service Provider (ISP)

Loading

Proxy detection

Loading

The results show where your browser traffic exits to the public internet.

Understanding the results

What this egress information means

This result card describes information exposed when requests from your current browser reach the public internet. It is not the device’s local network address.

Public IP

The public IP is the address that target websites can usually see. After switching to a VPNYE route, run the check again and compare the results. If the address and location change accordingly, your browser traffic is leaving through the new network egress.

Country and region

The location comes from an IP address database and indicates the region where the address is usually registered or routed. It is useful for checking the route direction, but it is not an exact location and may be temporarily inaccurate when an ISP changes its address ranges.

Internet service provider

The ISP field identifies the network operator associated with the egress address. If the original provider still appears after switching routes, refresh the page first, then check whether your system proxy, browser proxy extensions, and application routing rules are aligned.

Proxy detection

Proxy detection is a reference result inferred by the API from address characteristics. A detected proxy does not mean the connection is faulty; no detection alone cannot prove that all traffic uses the same path. Consider this field together with the public IP, location, and the actual connection status of each application.

Resolution path

DNS leak self-check

The GeoIP result on this page checks only the public egress of the web request; it cannot directly list the DNS resolvers used by your device. A DNS self-check requires reviewing system settings, browser settings, and changes before and after connecting.

  1. Record the pre-connection state

    Before switching routes, review the DNS configuration currently used by your system and record the ISP and public IP. This baseline helps distinguish local network settings from changes after connecting through a route.

  2. Clear the cache after connecting

    After connecting to the target route, close pages that are still loading, clear the system DNS cache, and reopen the browser. Old cached results may keep using pre-connection resolutions and distort the assessment.

  3. Check the system resolver

    On Windows, check ipconfig /all; on macOS, check scutil --dns; on Linux, check resolvectl status. Confirm that the resolver used by the active network interface still points to the original provider.

  4. Check secure DNS in the browser

    Some browsers enable secure DNS separately and bypass system resolver settings. If system results do not match browser behavior, check the browser’s secure DNS option and whether a proxy extension overrides system rules.

  5. Verify each application separately

    Web pages, command-line tools, and desktop applications may use different paths. Revisit the target service in the application you need to use; do not infer the traffic behavior of the entire device from a single browser check.

Privacy notice

This site does not log query results

IP checks are sent to VPNYE’s own-domain API. This page does not use third-party public lookup services or store the returned public IP, location, ISP, or proxy detection result in the browser. A new check runs after the page is closed or refreshed.