What the address at the top of this page is
It is the public IP address your internet connection is using right now: the address a website, a game server or a remote login system sees when your traffic arrives. Your internet provider assigns it to your connection, usually to the router rather than to the device in your hand, so every device on your home Wi-Fi normally shows the same public address here.
To find it, your browser asks ipify, a free lookup service, which reports the address the request came from. If that request fails, the page falls back to asking our own server what address it sees. Both methods answer the question from the outside, which is why the result can differ from anything your device settings show.
IPv4 or IPv6: which one you will see
An IPv4 address is four numbers from 0 to 255 separated by dots, such as 203.0.113.7. An IPv6 address is eight groups of hexadecimal digits separated by colons, such as 2001:db8::8a2e:370:7334, where a double colon stands for one run of all-zero groups. IPv6 exists because IPv4 has only 32 bits of address space; IPv6 has 128, and its notation is defined in RFC 4291.
Many connections have both. This page uses the IPv6-capable ipify endpoint, so if your connection supports IPv6 you will see an IPv6 address here even though other sites may show you an IPv4 one. Both are correct at the same time. One practical consequence: if you need your IPv4 address for an allowlist on a server that only speaks IPv4, and this page shows IPv6, the IPv4 address your connection also uses will not appear here. The system you are configuring will usually have logged the address it actually received.
Why it differs from the address in your device settings
Your laptop or phone almost certainly shows something like 192.168.1.23 in its network settings. That is a private address, valid only inside your local network. Your router translates between the private addresses on the inside and the single public address on the outside, a process called network address translation (NAT). Private ranges are reserved by RFC 1918 and are never routed on the public internet, so sending one to a hosting support team or putting it in a firewall rule achieves nothing.
A second range matters if you run anything at home that the internet must reach. Some providers do not give each customer a public IPv4 address at all; they share one among many customers with carrier-grade NAT and give the router an address from 100.64.0.0/10, the block reserved for this by RFC 6598. If your router's WAN address is in that range, or simply does not match the address shown on this page, inbound connections cannot reach you and port forwarding will not work however you configure it. The Open Port Checker confirms whether a port is reachable from the outside.
| Range |
Kind |
Where you see it |
| 10.0.0.0/8 | Private (RFC 1918) | Company networks, VPN clients, cloud virtual networks |
| 172.16.0.0/12 | Private (RFC 1918) | Office networks, Docker and other container networks |
| 192.168.0.0/16 | Private (RFC 1918) | Home and small-office routers |
| 100.64.0.0/10 | Shared (RFC 6598) | Router WAN address behind carrier-grade NAT |
| 169.254.0.0/16 | Link-local | A device that asked for an address and got no answer |
| fe80::/10 | IPv6 link-local | Every IPv6 interface, for the local link only |
When your public IP changes
Most home and mobile connections get a dynamic address: the provider leases it to you and may hand out a different one when the router reconnects, when the lease expires, after maintenance on their side, or whenever a phone moves between cells and networks. A fixed (static) address is usually a paid business option. Connecting to a VPN replaces your visible address with the VPN provider's exit address for as long as the tunnel is up.
The usual symptom of a changed address is a login that fails with the correct password. A server, control panel or cloud firewall that allows only your address still holds yesterday's entry. Check the address here, compare it with the allowlist, and update the rule rather than resetting credentials.
What this page does not tell you
It does not show your location. Finding the city, region and provider behind an address takes a geolocation database, and this page does not consult one; the IP Lookup tool does, and shows approximate results for any address you enter. The address alone does not reveal who you are or where you live: geolocation data is approximate, and only your provider can link an address to a subscriber.
It does not show your private address, your IPv4 address when IPv6 answered, or whether a VPN is leaking DNS requests. The user agent box shows the User-Agent string your browser sends with every request, which names the browser and operating system in general terms; modern browsers deliberately keep it vague. The Port box is not your connection's port number; it only records which of the two lookups answered.
As for who sees the address when you use this page: ipify receives one request from your browser, Cloudflare proxies our site, our hosting provider keeps ordinary server logs, and the site's cookieless analytics count the visit. The page code itself does not save the address anywhere.