Network identity

IP Lookup and Public IP Detection

Reads the IP, location, and ISP information currently visible to the internet, helping confirm whether a route switch took effect and supporting proxy and DNS configuration checks.

Public IP Country or region ISP Proxy detection

Current request

Current public IP details

Results are returned by this site’s same-origin GeoIP API. No third-party public lookup API is used to supplement the data.

GEOIP RESPONSE Public IP snapshot

Looking up

IP address: Loading…
Country or region: Loading…
ISP: Loading…
Proxy detected: Loading…

Field reference

What these details mean

Each field describes how the current public IP is identified in network databases. Database updates and changes in network routing may cause the displayed details to vary.

Public IP

Online services commonly identify a request source by its public IP. After switching to a WrVPN route, run the lookup again. If the public IP details change with the route, the request was sent through the new network path.

Country or region

The location comes from how IP databases register and infer an address range; it does not represent the device’s precise location. Update schedules vary between databases, and border regions or newly assigned ranges may be identified differently.

ISP

The ISP field usually shows the network operator, data center, or autonomous system organization associated with the address range. It can help confirm the public IP’s source, but cannot determine route quality on its own.

Proxy detection

This result only reflects how the GeoIP API classifies the current public IP. A network database may classify a data center address as a proxy or may not yet include a newly assigned range, so consider it alongside the actual connection status.

DNS review

DNS Leak Check Guide

An IP lookup confirms the public network exit, while a DNS check focuses on who handles domain resolution requests. These are separate steps: a route change alone does not confirm that DNS requests are following the expected path.

Record the current public IP

First, save the country or region and ISP shown on this page. Use them as reference points when comparing DNS resolution paths later.

Review client diagnostics

In the system or client you are using, review the DNS configuration and connection diagnostics. Confirm that resolution requests are handled by the DNS settings of the enabled route.

Compare DNS resolvers

If diagnostics continue to show DNS servers belonging to your previous ISP while the current public IP belongs to another route, check whether the system DNS, browser Secure DNS, and client routing rules are consistent.

Rule out cached results

After changing the configuration, reconnect and refresh the lookup and diagnostic results. Browsers, operating systems, and local network devices may all retain earlier DNS cache entries.

Privacy note

Lookup privacy

WrVPN does not record this page’s lookup results or write the returned IP, location, or ISP information to browser storage. Lookups use only this site’s same-origin API; when the API is unavailable, the page directly shows a failure state.