Hakkında

What this site is

ipaddress.gg answers the question its domain asks: what address is the internet seeing you as, and what does the public record say about it. Alongside that it carries the lookups that question leads to — WHOIS and RDAP registry records, autonomous system numbers, DNS, blocklist status, and whether anything on your own address answers from outside.

Where the answers come from

Every routing, registry, location, vendor and AS-name answer on this site is read from datasets we compile ourselves and serve from our own disk. There is no commercial geolocation API behind them, no reseller, and no account that could be cancelled or repriced.

The sources are all public: the global BGP table published by APNIC's Thyme project, the delegated-extended files from the five regional internet registries, IANA's RDAP bootstrap, DB-IP's free IP-to-City database for location estimates, GeoNames for places and timezones, the Tor Project's own exit list, and the IEEE registration authority's files for hardware vendors. They are rebuilt daily into flat binary indexes, so a lookup costs one binary search — and, more to the point, costs zero outbound requests. Nobody else learns that you were here.

The map is part of that. Country outlines, lakes and administrative boundaries are vector data served from this domain, and the places on it come from our own index, so no tile server is contacted and nobody learns which address you looked at.

The live queries are the exceptions, and they are the ones you ask for explicitly: RDAP and WHOIS go to the registry that holds the record, and DNS goes to a resolver. Those are the authoritative sources, and going anywhere else for them would mean showing you a copy instead of the record.

What we will not do

We will not present an estimate as a record. City-level location is an inference — ours included — so it is always labelled as an estimate, always carries the radius it is good to, and is always shown beside the registry's country of allocation, which is a fact of record. Where an operator publishes its own location under RFC 8805, that declaration is shown instead, with the URL it came from. Where we have nothing, the page says so rather than placing a pin somewhere plausible.

We do not offer a way to scan an address you do not control. The port check runs against the address your own request arrived on and has no field to point it elsewhere.

We do not sell, and have never held, a record linking a person to an address over time. The address history feature keeps its list in your browser for exactly that reason.

Corrections

If a record here is wrong, it is usually wrong at the source, and the contact page is the fastest way to tell us which one. Registry data we can only reproduce; where we have introduced the error ourselves we would like to know.