Public IP address
An IP address is what external websites see as the source of the current connection. If you are using RqVPN, run a lookup before and after connecting to confirm that the egress has switched to your selected route.
Real-time lookup via a same-origin API
Check your current public IP
See the IP address, location, ISP, and proxy status currently presented by your browser’s connection to the public internet. The lookup uses this site’s same-origin API and will not be routed to another data service if it fails.
This site does not log lookups
Copy results with one click
CURRENT CONNECTION
Waiting for lookup
Current lookup results
- IP address
- Temporarily unavailable
- Location
- Temporarily unavailable
- Internet service provider (ISP)
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Understanding the results
What this information means
The results describe the network egress your browser presents when its request reaches the public internet. This is not the address your device uses on a local network. The result may change when you switch networks, routes, or connection methods.
Location
Location data comes from an IP geolocation database and indicates the approximate region of the egress. Databases can take time to update, so use this result as a connection check rather than proof of an exact location.
Internet service provider
The ISP field usually identifies the network operator, hosting provider, or autonomous system associated with the address. Different databases may display different organization names, but the current egress address remains unchanged.
Proxy detection
Proxy detection is an assessment based on address type and network characteristics. A detected or undetected result reflects only the current database classification; it does not by itself measure connection quality, privacy, or route stability.
Connection check
DNS leak check
DNS resolves website names into connectable addresses. A changed public IP does not automatically mean every DNS request follows the same path. If DNS queries are still handled by the original network environment, the connection source and DNS route may not match.
A complete DNS check requires a dedicated test domain and server-side records. This page reads GeoIP data only; it does not present a standard IP lookup as a DNS test or call a third-party public API to fill in missing results.
Recommended self-check steps
- Keep the same route Stay on the same network and use the same egress location during the check to avoid mixing results through frequent switching.
- Compare DNS locations When using a trusted DNS testing tool, check whether the DNS servers’ locations clearly conflict with the expected connection path.
- Compare after disconnecting Record the differences between connected and disconnected states. If the DNS provider and location never change, review your system DNS, browser secure DNS, and client settings.
- Reconnect and check again Reconnect after adjusting your settings, then compare the public IP and DNS path again to confirm the change took effect.