Your public IP address is the address an internet service sees when your connection reaches it. On a typical home network, several phones, computers, televisions, and smart devices can share one public IPv4 address through the router. If your ISP supplies IPv6, a device may also have one or more public IPv6 addresses.

What this result tells you

The address shown above is observed by this website. It can be useful when you are checking a VPN, troubleshooting a remote-access setup, comparing IPv4 and IPv6 connectivity, or confirming which connection is currently active. It is not the same thing as your router’s local admin address.

Public IP vs. router IP

Router admin pages normally use private addresses such as 192.168.1.1, 192.168.0.1, or 10.0.0.1. Those addresses work only inside the local network. Your public IP is assigned or routed by your ISP and is visible to services on the internet.

Why the address can change

Many residential connections use dynamic addressing, so the public IP can change after a modem reconnect, an ISP maintenance event, or a lease change. A VPN or corporate proxy can also make the visible address belong to that service rather than to your home ISP. Mobile networks may place many customers behind carrier-grade NAT, which means the address shown here is shared at the provider level.

Privacy and limitations

An IP address can usually suggest an ISP and a broad region, but it does not reliably reveal a street address. Treat IP-geolocation results as approximate. If you are trying to reach your router, use the router IP guide instead of entering this public address into your browser.

How to use this tool as evidence, not as a score

This tool is designed for public-address verification, VPN checks and IPv4/IPv6 troubleshooting. Run the check, record the exact input/result and compare it with the configuration you expected. A single result is most useful when it answers a specific troubleshooting question.

How to interpret the result

Compare the displayed address before and after changing networks or VPN state. A change can confirm that traffic is exiting through another provider, but it does not identify a person or exact location.

Important limitation

Carrier-grade NAT, privacy relays, enterprise gateways and VPNs can make many users share or appear behind the same public address.

A practical troubleshooting workflow

  1. State the symptom and expected result before testing.
  2. Run the tool once without changing configuration.
  3. Change only one relevant variable—such as VPN state, DNS record, router rule or URL.
  4. Run the same test again and compare.
  5. Confirm the finding with the system/provider/vendor tool closest to the source of truth.

This avoids “tool hopping,” where several unrelated checkers produce numbers but none actually isolates the problem.

Privacy and responsible use

Use network/domain tools on systems and data you are authorized to test. Public registration/DNS information can be inspected, but results should not be used to claim a person’s identity or precise location. Do not submit passwords, API keys or other secrets into diagnostic fields unless the page explicitly requires them and you trust the system.

What a useful result looks like

A useful public-address verification, VPN checks and IPv4/IPv6 troubleshooting result changes a decision. It should tell you whether the observed value matches the expected configuration, which layer to inspect next, or whether a previous change actually fixed the symptom. Save the timestamp, target and result when comparing before/after states.

False certainty to avoid

One tool sees only one part of a system. A successful network request does not prove an application is healthy; a DNS record does not prove mail or a website is configured correctly; an open port does not prove the service behind it is secure; and a geolocation database result does not prove a person’s exact location. Interpret the output within the tool’s stated scope.

Repeatability matters

Transient packet loss, DNS caching, CDN routing, firewall state and server load can change from one run to the next. Repeat measurements when timing or availability matters, and compare from the same vantage point before concluding that a configuration change caused the difference.

Corroborate at the source of truth

When the result affects a production decision, confirm it with the system that owns the data: authoritative DNS/provider console for DNS, router/firewall configuration for local networking, certificate issuer/server configuration for TLS, mail-provider logs for authentication, or the web server/CDN for HTTP behavior. Third-party checks are evidence, not authority over your configuration.

Troubleshooting notes worth recording

  • Exact input/target and whether it is IPv4, IPv6, hostname, URL or domain.
  • Network context: home/office, VPN on/off, Wi-Fi/Ethernet, and ISP if relevant.
  • Status/result before the change and after the change.
  • Any cache, TTL, timeout or rate-limit condition that can delay the expected result.
  • The authoritative configuration you compared against.

Privacy and authorization

Test systems you own or are authorized to administer. Network metadata can be sensitive even when it is technically public. Do not use lookup results to make unsupported claims about a person’s identity, physical address or intent, and never paste passwords or secret tokens into general diagnostic inputs.

Network-context checks that prevent bad conclusions

Compare the result from both sides of the router boundary when relevant. A client’s private address and default gateway describe the LAN, while a public-IP/port result describes the upstream internet-facing path. VPNs, CGNAT, IPv6, dual-stack and second routers can make those perspectives different without either tool being “wrong.”

Use a control test

Repeat the check on Ethernet versus Wi-Fi, VPN on versus off, or another authorized device on the same LAN. A controlled comparison is much more informative than changing several router settings and testing again.