Check your public IP address and see whether this connection uses IPv4 or IPv6. Learn what the result means, why it changes, and how to use it responsibly.
When someone searches “what is my IP address,” they usually need one dependable answer for the connection they are using right now. The number shown by this page is the public IP address that reaches the website, not a guess based on your device name or Wi-Fi label. That distinction matters when you are opening a support ticket, checking a firewall allowlist, confirming a remote-work connection, or comparing a home network with a mobile hotspot.
Use the value as a snapshot of your current internet path. Read the address and the IP version displayed beside it, copy it only when a trusted person or service needs it, and refresh after changing networks. An IP address is useful network information, but it is not a personal identity card and it is not a substitute for a security audit.
A public IP address is the externally visible address attached to a connection as it reaches an online service. Your router may let several phones, computers, and televisions share that one address through network address translation. This is the address a website can normally record for a request, so it is the right answer when a form asks for your external IP, internet IP, or allowlist address.
A private IP address works only inside a local network. Addresses in ranges such as 192.168.x.x, 10.x.x.x, or 172.16.x.x–172.31.x.x identify devices behind a router and are not the value this web page is designed to find. If a printer or router setup asks for a local address, open your operating system’s network settings instead. Neither result is “more correct”; they describe different sides of the same connection.
IPv4 is the familiar dotted form made of four numbers, while IPv6 uses a longer hexadecimal form separated by colons. Internet providers and workplaces may run both protocols at once. A phone on Wi-Fi can therefore show a different public address from the same phone on cellular data, and a network that supports IPv6 may present that version instead of IPv4 for some requests.
Seeing IPv6 is normal and does not mean the connection is unsafe. Likewise, not seeing IPv6 does not prove that anything is broken; many networks still expose only IPv4 to a particular service. When you record an address for technical support, include the displayed version and the time you checked it. That small detail prevents a technician from testing an IPv4 rule when your application is actually reaching them over IPv6.
The page processes the web request that your browser sends and displays the first valid public address available to the server. On a production site, a trusted reverse proxy or edge service may pass the original client address in a request header; the server can use that value before falling back to the connection address. The result is therefore the address visible to this request path, which is what most websites and support systems need.
Only two results are presented here: the address and whether it is IPv4 or IPv6. The checker does not look up an ISP, map a city, identify a person, test ports, inspect DNS, or decide whether a VPN is leaking. It also cannot reveal a private address inside your home. If you are testing a local development copy, a private or unavailable result can be expected because a local machine may not have a public route to the page.
Most residential connections use dynamic addressing. Your provider may assign a different public IP after a lease refresh, a modem restart, maintenance, or a longer period offline. Moving from home Wi-Fi to office Wi-Fi or mobile data changes the network entirely. Carrier-grade NAT can also place many customers behind one shared IPv4 address, so the number is not necessarily unique to your individual device.
A VPN, privacy relay, corporate proxy, or hosted browser can make the checker see the intermediary’s address instead of the one assigned to your home line. That is expected routing behaviour, not proof that the service has failed. To compare paths, note the result with the privacy service disconnected, connect it, refresh, and compare again. If the value does not change when you expected it to, check that the VPN is actually connected and ask its provider about IPv6 or split-tunnel settings.
An IP check is useful when a network administrator needs to allow a temporary office connection, an online game reports a connection problem, or support wants to confirm which network is reaching a service. Copy the value from the page rather than retyping it, send it through a trusted support channel, and request a narrow rule or short expiry instead of a broad permanent exception. For a quick comparison, refresh once, note the time, network type, and IP version, then repeat after switching between Wi-Fi and cellular data or enabling a VPN. A changed value confirms that the route changed; an unchanged one may simply mean that the provider or intermediary is stable.
Do not treat an IP address as a password. It can suggest a provider or broad region, but it normally cannot identify your exact street address, device files, or account credentials by itself. Avoid posting it publicly without a reason, keep your router and firewall updated, and use account-level authentication for sensitive access. If a firewall rejects the value, confirm that it expects a public address and supports the displayed protocol; for an internal device, use its private address instead. If no public value appears, try a normal production connection and remove unusual proxies or browser-routing extensions. Persistent discrepancies belong with the network administrator or provider because this checker reports what the request presents rather than diagnosing the entire network. When documenting a result, include the protocol, network, and time rather than forwarding a number without context; the same address can belong to many users behind shared NAT, and a later check may legitimately produce another value.