My IP History

Why keep a history at all

Most connections change more often than people realise. Residential addresses are leased and re-leased, mobile data hands you a different address on every reconnection, and a VPN client that reconnects may put you in an entirely different country without saying so. Individually each of these is invisible; over a week they explain a surprising number of odd problems — a service that suddenly wants a new login, a rate limit that appears from nowhere, a geo-restricted page that starts behaving differently.

How this stays private

The obvious way to build this feature is to store the address. This does not, because it does not need to. Comparing two connections only requires knowing whether they are the same, and a one-way hash answers that without keeping the thing it was computed from.

The hash is SHA-256 over the address with a fixed prefix, truncated to twelve hexadecimal characters, and computed by your own browser through the Web Crypto API. Forty-eight bits is far more than enough to distinguish the handful of connections you will ever record, and it is obviously not an address — nobody can glance at the stored value and read your IP out of it.

Everything else stored beside it is already public information about the network: the country, the operator, the autonomous system number and a connection type. None of it identifies you specifically, and all of it is what makes an entry readable a week later.

Nothing is recorded automatically

Opening this page records nothing. The entry is written when you press the button, and not before. That is a deliberate difference from a page that quietly logs every visit: a privacy feature that starts collecting before you ask is not a privacy feature.

Where this sits relative to the other tools

The dashboard shows what your connection looks like right now. The VPN and proxy detection explains what kind of network you are on. This page is the only one that remembers, and it remembers in the narrowest way that still answers the question.

What the history is stored in, exactly

The entries on this page live in your browser's localStorage, under this site's origin. They are written by the page you are reading and never transmitted anywhere — there is no account, no sync, and no copy on IPGet's server. Clearing site data for this domain removes them completely and permanently, and opening the page in a private window shows nothing, because that window has its own empty storage.

This also means the history is per-browser and per-device. The list on your phone and the list on your laptop are separate, even on the same connection, and neither can see the other.

What a history reveals that a single check cannot

One lookup tells you your address now. A series tells you how your connection behaves, which is a different and often more useful thing.

• How often your provider rotates you. Most residential connections lease an address for a period and may change it on renewal or on a router restart. Seeing whether that is daily, weekly, or effectively never tells you whether you can rely on the address at all.
• Whether a VPN is actually carrying your traffic. If the client says connected but the address here matches your ordinary one, the tunnel is not carrying browser traffic — which is precisely the failure worth catching, and easy to miss without a before-and-after.
• Whether you moved between networks. Home, office and mobile addresses will be registered to different operators, and the change is obvious in a list even when it is not obvious at the time.
• Whether you are behind carrier-grade NAT. An address that changes several times a day, or that never matches what your router reports, is a strong hint. The IPv4 checker explains how to confirm it.