About IPGet

What IPGet is

IPGet answers one question immediately — what is my IP address — and then gives you a growing set of focused tools for the questions that usually follow. Which protocol am I actually connecting over? What does my browser reveal? How fast is this connection really?

It is built for people who need a precise answer quickly: developers debugging a deployment, network engineers checking a route, anyone verifying that a VPN is doing what they think it is.

How it is built

Every page is static HTML generated at build time. There is no client-side framework, no analytics bundle and no tracker. The only JavaScript that runs is the small amount needed to fetch your address and read your browser's own settings — a few kilobytes in total.

That is a deliberate constraint rather than an aesthetic preference. A diagnostic tool that takes several seconds to load has failed at its job, and every third-party script is another party watching you use it.

Our approach to your data

Your IP address is read from the connection, used to render the page, and discarded. It is not written to a database, not logged for analytics, and not linked to an identity — there are no accounts here to link it to.

Everything on the browser and screen pages is read inside your browser and displayed there. None of it is transmitted to us. The privacy policy sets out exactly what is processed and why.

Accuracy over guessing

When IPGet cannot determine something, it says Unavailable rather than producing a plausible-looking number. This matters most for IPv4 and IPv6 detection, where many tools report a confident wrong answer: a browser uses one address family per connection, so a single request cannot tell you about the other. IPGet tests each family separately where the deployment allows it, and clearly states when a family was not tested.

Geolocation is presented the same way. Country is dependable; city is an estimate that is frequently wrong by tens of kilometres, and we say so rather than implying precision that does not exist.

Security

Tools that reach out to a host you name — the DNS and port checkers — are treated as security-sensitive features rather than conveniences. They validate input, refuse private and reserved address ranges, pin resolved addresses to prevent DNS rebinding, apply rate limits and time out quickly.

Where those protections are not yet operational, the feature is not enabled. We would rather publish a useful reference page than a half-guarded network tool.

What is next

The DNS and port checkers are next, followed by more developer utilities. The architecture is designed so a new tool is one configuration entry and one page — which keeps the catalogue growing without the site getting slower.

See everything available today on the tools page.