IP Geolocation

It's network-level, not street-level. We map the IP to the country its network block is registered in, along with the operator (ASN) and the announced route. For most sites that's the hosting country, which is what matters for compliance, latency and CDN questions. It is not GPS positioning and won't pinpoint a city or a person — a registered country can also differ from the physical server location when a global provider registers ranges centrally.

Because of how this whole toolkit is built. Precise geo-IP means sending the IP to a third-party database or API, almost always hosted in the US. That would contradict the promise behind every Uptimeify tool: lookups run on our own EU servers, off US infrastructure and clear of US Cloud Act exposure. We chose the honest, privacy-clean answer — network and country from registry data we resolve ourselves — over a more precise figure that would leak the query.

Both. A domain is first resolved to its public IP address, then that address is located. Private and reserved addresses are rejected, since they don't belong to any public network. The result shows the country, the operator and AS number, the announced BGP prefix, the registry and a reverse-DNS hostname where one exists.