Public IP & IP lookup
See the IP, country or region, network provider and proxy status presented to websites by your current connection. Data comes from YRVPN’s same-origin GeoIP API, with no third-party public lookup service involved.
CURRENT CONNECTION
Current lookup results
Fetching public connection details through our API…
READ THE RESULT
What this information means
An individual result describes only one part of the connection. To confirm that a route is working as expected, consider the public address, location and real-world access performance together.
Public IP
This is the address your browser presents to websites. Check it before and after connecting to an international route and compare the results; a change usually indicates that traffic has moved to another network exit point. If it stays the same, check the client connection status, routing rules and whether the site is set to connect directly.
Country or region
The location comes from a GeoIP database mapping public addresses to approximate areas. It is not precise positioning and may briefly lag behind network-provider address changes. Streaming and other region-specific services may also consider account region, exit-point attributes and past access context when determining available content.
Network provider
The ISP field identifies the network organization to which the public address is registered or announced. It can help distinguish residential broadband, data centers and other network types, but the name alone does not indicate route quality. Assess stability alongside the target site’s response, peak-hour performance and route type.
Proxy detection
Proxy detection is an auxiliary assessment based on address attributes returned by the API. It does not indicate a connection failure and cannot, on its own, prove that a service will work. If the API does not return this field, the page will show “No assessment provided by the API” rather than guessing.
DNS SELF-CHECK
DNS leak self-check
A changed public IP does not automatically mean that DNS resolution follows the same route. If DNS requests are still handled by the original network environment, the resolver location may not match the exit region, affecting regional content decisions, connection stability or privacy expectations.
-
Record your DNS settings before connecting
Check the current DNS configuration in your system network details or router administration page, and note whether it is obtained automatically or specified manually. Do not infer the DNS path from the public IP shown in your browser alone.
-
Check again after connecting
Confirm that the client shows as connected, then check whether the DNS settings in your system network details have been updated according to the client policy. In split-routing mode, also confirm that the target domain follows the same rule as its traffic.
-
Clear old caches and test again
Your system and browser may retain earlier DNS records. Clear the DNS cache, fully close related browser pages and revisit the target service to reduce interference from stale results.
-
Switch routes and DNS modes when needed
If the exit region is correct but the target service still identifies another region, first switch to a different route in the same region, then check the client’s DNS takeover or remote-resolution settings. Change one setting at a time to make the cause easier to identify.
PRIVACY NOTE
Lookup privacy
This site does not log this lookup
The page requests only the display fields needed for the current connection from YRVPN’s same-origin GeoIP API and renders the result in your browser. The copy action handles only the public IP already shown on the page. If the API is unavailable, the page keeps the “Temporarily unavailable” status and does not switch to a third-party public lookup service.