Lotamyst / The Bench / What Is My IP

What Is My IP

Your public IP address and the details of the connection carrying it — read from our own server's edge, with no third-party lookup service involved.

Your public IP address
Checking…
reading the connection…

What the connection reports
address family
country of the connection
nearest Cloudflare edge
HTTP version
TLS version
Cloudflare WARP
TLS hostname (SNI)
What your browser reports
time zone
UTC offset
languages
screen
user agent the server saw

Your address is read from /cdn-cgi/trace on this very site — the same server you already connected to in order to load this page. It is never posted to a third-party lookup API and never written to a cookie or to browser storage. That one request is the only network call this tool makes of its own, and it is repeated only when you press Check again.

How to read this

  1. The big address is your public IP. It is what our server saw when your browser asked for this page — the same thing every other website sees. Use Copy IP if you need to paste it into a support ticket, a firewall allowlist or a game server whitelist.
  2. IPv4 or IPv6. Dots means IPv4 (203.0.113.9), colons means IPv6 (2001:0db8:85a3::8a2e). If you have both, this shows the one your browser actually chose for this request.
  3. Country is the network's country. It comes from Cloudflare's own view of the address at the edge. It tells you where the network exits, not where you are sitting.
  4. The Cloudflare edge is a building, not you. The three-letter colo code is an IATA airport code for the datacentre that answered. Routing sends you to a nearby one, but "nearby" can mean a different city or, on some networks, a different country entirely.
  5. HTTP and TLS show how modern the path is. HTTP/3 over TLS 1.3 is today's best case. HTTP/1.1 or TLS 1.2 usually means a corporate proxy, an antivirus that inspects TLS, or an older device is sitting in the middle.
  6. The proxy check is a hint, never a verdict. It only compares your device's time zone against the connection's country. Travelling, a manually set clock and a perfectly ordinary mobile network all trip it.

Public vs private IP — the two numbers people mix up

Run ipconfig or check your phone's Wi-Fi settings and you will see something like 192.168.1.47. That is not the address the internet sees. Three ranges are reserved for private networks and are deliberately unroutable in public: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. Every home router on earth uses one of them, which is why millions of houses all have a device at 192.168.1.1 with no conflict.

Your router performs NAT (network address translation): it rewrites the source address of every outbound packet to the one public address your ISP gave it, keeps a table of which internal device asked for what, and unwraps the replies on the way back. So a website can never see 192.168.1.47, and it cannot tell whether the request came from your laptop, your TV or your doorbell. It only sees the one public address, which is the number at the top of this page.

The practical consequence: an IP identifies a household or an office, not a person. If a site bans "your IP", it bans everyone on your connection. If your work VPN is on, the address belongs to your employer.

What an IP address actually reveals

Anyone who receives a connection from you learns your IP — that is not optional, it is how packets find their way back. What they can do with it is narrower than folklore suggests.

Knowable, with reasonable accuracy: the country, the organisation that owns the address block (your ISP, your employer, a hosting company), and whether the block is residential, mobile or a datacentre range. That last one is how sites spot VPN and cloud traffic.

Knowable, but usually wrong in detail: the city. Geolocation databases are built from registry paperwork, latency measurements and self-reported ISP data. A single mobile gateway can serve an entire region, and rural addresses are routinely placed at whatever the database uses as a fallback point.

The "they can find my house" myth. IP geolocation has no concept of a street. When a database cannot place an address precisely it snaps to a coarse centroid — for years, one widely used database mapped every unplaceable US address to the geographic centre of the country, which happened to land on a farm in Kansas. The people living there spent a decade being blamed for spam, fraud and worse by strangers who thought an IP lookup was an address lookup.

The only party that can turn an IP into a name and a street is the ISP that issued it, and in most jurisdictions that requires a court order. If a stranger claims to have your address from your IP, they either guessed your city or got it from somewhere else entirely — a leaked account, a social profile, or a link you clicked. Browser geolocation is a separate thing: it uses GPS and Wi-Fi and it asks your permission first, which is exactly why it is accurate and an IP is not.

Static, dynamic, and why so many people share one address

IPv4 has 32-bit addresses — about 4.3 billion, minus large reserved chunks. The last blocks were handed out by IANA in 2011 and the regional registries ran dry over the following decade. There were never going to be enough for every phone, console, camera and fridge.

Two workarounds keep IPv4 alive. The first is dynamic assignment: your ISP leases you an address rather than giving you one, and it can change when your router reboots, when the lease expires, or when the ISP reshuffles its network. This is why a firewall rule or a DNS record that hard-codes your home address quietly breaks a month later, and why dynamic DNS services exist.

The second is CGNAT (carrier-grade NAT), and it is why the address above may not really be yours alone. Your ISP performs a second layer of NAT in its own network, so hundreds of subscribers share one public IPv4 address. Mobile networks have done this for years and many fibre and cable ISPs now do it too. Symptoms: port forwarding does nothing, you cannot host a game server, peer-to-peer connections fall back to slow relays, and you occasionally hit a CAPTCHA because a neighbour you have never met misbehaved.

How to tell you are behind CGNAT: log into your router and look at its WAN address. If it starts with 100.64. through 100.127. (the range reserved for exactly this) and does not match the address at the top of this page, you are sharing. A private 10.x WAN address that differs from this page is the same story.

IPv6 is the actual fix. 128-bit addresses give every device a globally routable one, no NAT required, which restores end-to-end connections. Because a permanent per-device address would be a tracking gift, operating systems generate rotating privacy addresses for outbound traffic — so your IPv6 address changing every day or so is a feature, not a fault.

VPNs, proxies and Cloudflare WARP

A VPN or proxy terminates your traffic somewhere else and re-originates it, so the address on this page becomes the exit node's. That genuinely hides your home address from the sites you visit and hides the destination from your ISP. It does not make you anonymous: your logins, cookies, browser fingerprint and behaviour identify you just as well as before, and you have moved your trust from an ISP you can complain to onto a VPN operator you probably cannot.

WARP is Cloudflare's own client (the 1.1.1.1 app). When it is active, the edge tags the request and this page reports it, and the address you see is a Cloudflare egress address rather than your ISP's. It is not a full VPN by default — it is closer to an encrypted transport that hides your traffic from the local network.

The time-zone comparison in the panel above is roughly how sites start detecting VPN users: if the browser insists it is in Tokyo while the connection arrives from Frankfurt, something is translating. Real detectors then check whether the address sits in a known datacentre block, look at HTTP header ordering and TLS fingerprints, and score the result. A single time-zone mismatch on its own means very little — which is exactly why this page labels it "worth noting" and refuses to call it proof.

Why this page does not show your ISP, ASN or city

Nearly every other "what is my IP" page shows an ISP name, an autonomous system number and a city with a map pin. None of that is in the request you make — it has to be looked up in a database. Which means those pages take your IP address and send it to a third party's API, on every page load, so that you can read a city name you already knew.

We are not doing that for a decoration. Everything above comes out of Cloudflare's answer to the request you already made to our server, so your address does not travel anywhere new. If you do want the ASN and the registry record, look it up yourself with a WHOIS or RDAP query at your regional registry — deliberately, once, knowing where it went, rather than automatically every time you open a tab.

The same restraint applies to what is kept. Beyond the page's own stylesheet and script, this tool makes one network request — the one that reads your address, repeated only when you press Check again — and it writes nothing: no cookie, no localStorage entry, no analytics ping carrying your IP. You can confirm it yourself in your browser's network tab, which is rather the point of saying it.

FAQ

What is my IP address?

Your public IP address is the number the rest of the internet uses to send data back to you. It belongs to your internet connection, not to your device — every phone, laptop and console on the same home network normally shares one public IP. This page reads it from our own server's Cloudflare edge and shows it at the top.

Is 192.168.1.1 my IP address?

No. That is a private address your router hands out inside your own network, along with anything starting 10. or 172.16 through 172.31. Those ranges are not routable on the public internet, so no website ever sees them. Your router rewrites them to your single public address on the way out, a process called NAT.

Can someone find my home address from my IP?

No. An IP address maps to a network, not to a doorstep. Commercial geolocation databases usually get the country right, guess the city, and are frequently wrong by tens or hundreds of kilometres. Only your ISP holds the link between an address and a subscriber, and it takes a court order or an equivalent legal process to get it.

Why does my IP address keep changing?

Most home connections are dynamic: the ISP leases you an address and can change it when the router reboots, when the lease expires, or when the network is re-engineered. Mobile networks change it far more often than that. A static address that never moves is normally a paid business option.

Do I have IPv6?

If the address shown above contains colons, such as 2001:0db8:85a3::8a2e, you reached this page over IPv6. If it is four numbers separated by dots, you are on IPv4. Many connections have both and use whichever the site supports, so this page reports the one actually used for this request, not everything you own.

Why doesn't this page show my ISP, ASN or city?

Because getting them means posting your IP address to somebody else's lookup API, and we are not willing to do that for a convenience field. Everything on this page comes out of our own server's answer to a request you already made, so your address never leaves the conversation you started.

Related tools