Your browser's current public IP

VPNRJ Public IP Lookup

See the public IP used for this website request, then compare it with the result before connecting. This result applies only to this query and may not reflect the network route used by other apps.

Current lookup result

Lookup via VPNRJ

Ready to check. Enable JavaScript to retrieve a result.

Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet Service Provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

What the results mean

Public IP: the address websites see

Your public IP is the internet-facing address used when this query reaches VPNRJ—not your device's local network address. After connecting to VPNRJ, run the check again and compare the results. If the address hasn't changed, make sure your client is connected and that your browser traffic is covered by the active routing rules.

Location and ISP: network details from IP databases

The country or region comes from an IP address database and indicates the network's registered location, not your device's exact location. Database updates, ISP address allocation, or changes to the network exit can cause the displayed location to differ from the selected route's name. The ISP may refer to the exit network or hosting provider rather than your local broadband provider.

Proxy detection: an indicator, not proof of connection

Proxy detection relies on information supplied by the API. “No proxy detected” does not mean you aren't using a VPN, and “Proxy detected” alone cannot confirm whether your connection is secure. If a field isn't returned, this page will show “Temporarily unavailable” rather than treating missing data as a negative result.

DNS LeakSelf-Check

DNS translates domain names into network addresses. If web traffic uses your selected route but DNS queries still go to an unexpected resolver, investigate the DNS path. This page checks only your public IP; it does not test for DNS leaks or declare a pass based on IP location alone.

  1. Record your baseline before connecting. Check the DNS settings currently used by your client and operating system, and note the public IP shown on this page. Understanding your existing network route helps you identify what changes after connecting.
  2. Check your client after connecting. Make sure the connection mode, DNS interception settings, and routing rules match your expectations. Also check your browser's Secure DNS setting, which may use a separate resolution path.
  3. Use a diagnostic tool that shows which resolvers are in use. To investigate further, choose a trusted DNS diagnostic tool and compare the resolver details before and after connecting. External tools receive your requests, so review their privacy policies first. This page does not access them automatically.
  4. Check your configuration, not just the location. A difference between the resolver's location and your public IP's location does not necessarily indicate a leak. Check that the resolver is one you expect and that your client handles DNS queries according to your rules before changing DNS settings.

After changing settings, reconnect and repeat the checks. If you still have questions, use the support ticket system to describe your platform, connection mode, and symptoms. Redact sensitive information from screenshots before sharing them.

LookupPrivacy Notice

VPNRJ does not log queries. Requests are sent only to VPNRJ's GeoIP API to display information about this connection. If the API is unavailable, no third-party public API is used as a fallback. The copy button writes your current public IP to the clipboard only when you click it.

Your public IP is network information. Redact it from screenshots before sharing them publicly. When troubleshooting, never submit passwords or full subscription links. See the Privacy Policy for details.