Your IP address
This is what every site you open can see. The page stores nothing: everything here came out of your own request and is gone once the page is rendered.
Your address
216.73.216.228
Protocol version: IPv4
Where sites think you are
- Country
- US
- Region
- OH
- City
- Columbus
- Postal code
- 43215
- Time zone
- America/New_York
- Coordinates
- 39.96118, -82.99879
- Autonomous system (AS)
- AS16509
The city and coordinates are an estimate from an address database, not your real location. Being wrong by a region is normal.
Your browser
- Browser
- not determined
- System
- not determined
- Languages you announce
- not determined
- User-Agent string
- Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Your TLS fingerprint
- JA4
- t13d1011h2_61a7ad8aa9b6_3fcd1a44f3e3
This is a fingerprint of how your software opens a secure connection: the cipher list, the protocol version, the order of extensions. It does not depend on your IP address. Changing the address does not change it.
See for yourself
Note the address above, turn Liska on and reload. The address, the country and the operator will change. The TLS fingerprint and the browser string will not.
What an IP address is
An IP address is the return address of your connection. Without it there is nowhere to send the answer, so every site you contact sees it before the first image has loaded. There is nothing to allow or refuse: it is not stored in your browser and it has nothing to do with cookies.
The address is not issued to you but to your connection — by an internet provider, a mobile operator or whoever owns the Wi-Fi. That is why it changes when you move from home to mobile data, and why hundreds of people behind one operator can be using the same address at the same time.
What a single address gives away
The address maps to an autonomous system — the number of the network that owns it. That reveals your network operator, and along with it whether the connection is residential, mobile or a data centre. From there, address databases fill in a country, a region and a probable city.
Everything else on this page comes not from the address but from the request itself: your browser and operating system announce themselves, and the list of languages is something you send to every site with every request, usually without knowing it.
Why the city is often wrong
Nobody measures IP geography — it is taken from databases built out of operator filings and indirect signals. A range can be registered to an operator head office in a different city, and mobile addresses are often pinned to whichever node routes traffic for an entire region.
Being wrong by a region is normal, not a malfunction. A wrong city tells you something about the database, not that you were somehow missed.
Why the TLS fingerprint does not change with the address
Before it sends a single byte of data, your software negotiates a secure connection. At that moment it lists which protocol versions it supports, which cipher suites it is willing to use, and the order its extensions come in. Different software makes those choices differently, and consistently enough to be recognised by them. The digest of those parameters is the JA4 shown above.
It is computed from the contents of the handshake, not from where the handshake arrived from. Changing your address does not change it — not through a VPN, not through a proxy, not by switching networks. The value moves only when the software moves: a different browser version, a different library, a different operating system.
This page does not store or forward any of it.