What Is My IP Address

This page shows what the network sees when you connect, and separately what your browser hands over to every website you visit. Both are worth knowing, and they are not the same thing.

What an IP address actually reveals

Your IP address is a routing label. It tells the internet where to send packets back to, which is why every site you visit necessarily learns it — there is no way to load a page without it. What it reveals about you is narrower than most people fear and broader than most people assume.

It identifies your internet provider reliably, and the network block they assigned you, shown here as the ASN and organisation name. Location is a different matter: geolocation databases map address blocks to places using registration records and observed routing, so country is usually right, region is often right, and city is frequently wrong — particularly on mobile networks, where traffic can surface hundreds of kilometres from where you are standing, and on business connections registered to a head office. Treat the city as a hint, not a fact. What an IP does not contain is your name, your street address or your identity; linking it to a person requires records held by your provider.

Why this page separates server-side from browser-side

The first group of facts can only come from a server. No browser API can tell a page its own public IP address, the autonomous system it is routed through, or which edge data centre answered the request — those are properties of the connection as observed from the other end. That is why this page asks one small endpoint of ours for them.

The second group needs no server at all. Your timezone, language preferences, screen dimensions, platform and user agent string are read directly out of your own browser, in your own tab. We show them in a separate column because that distinction is the point: every website you visit can read those values silently, without asking, and combined they form a large part of what is called a browser fingerprint. Seeing them listed is a more accurate picture of what you are actually exposing than an IP address alone.

The timezone mismatch check, and why it is done by offset

If your browser thinks it is in one time band while your network exit is in another, something is rerouting your traffic — usually a VPN, a proxy, or corporate egress in another country. That is genuinely useful to know: it confirms a VPN is actually carrying your traffic, and it also explains why some sites suddenly demand extra verification or serve you the wrong language.

The comparison here is made on UTC offset, not on timezone name, and that detail is the whole difference between a useful signal and a false alarm. Asia/Taipei and Asia/Shanghai are different names for the same UTC+8 offset; a name comparison would flag somebody in Taipei on a Shanghai-registered network as suspicious when nothing unusual is happening. A differing offset is the real signal. When the names differ but the offsets agree, this page says so plainly and does not raise an alarm.

IPv4, IPv6, and why you see only one

The address shown is the one your device actually used to reach this page. If it contains colons it is IPv6; if it contains dots it is IPv4. Most connections today are dual stack, meaning your device holds both kinds of address and picks per destination, generally preferring IPv6 when the other end supports it.

That is why the address here can differ from what another site reports, and why it may change between visits without anything being wrong. This page deliberately does not attempt simultaneous dual-stack detection. Doing it properly requires separate IPv4-only and IPv6-only hostnames and loosening the strict connection policy that makes the rest of this site verifiable, and we are not willing to weaken that for one extra row of information.

What we do with this data: nothing

The endpoint that returns your connection details performs no writes. There is no log file, no database, no analytics pipeline and no third-party script anywhere on this page — no ad network, no tag manager, no session recorder. Your IP is read from the request headers, put straight into a response addressed to you, and then it is gone.

You do not have to take that on trust for the part that can be checked. Every page on this site is served with a Content Security Policy that permits connections only to this origin. A browser enforces that rule itself, which means this page is technically incapable of sending anything to a third party — if we added a tracker tomorrow, your browser would refuse to load it. Open DevTools, watch the Network tab and reload: you will see a request for the page, a request for our own endpoint, and nothing else. This is also one of only two tools on Breezo that involve a server at all; the other is the speed test, and it says the same thing on its own page.