OWNERSHIP & ROUTING
IP Geolocation Lookup
Query RIPEstat registry-country and routed-prefix data, with richer GeoLite detail available as an administrator-controlled option.
39DExternal testRuns from the toolbox server
RUN TEST
IP Geolocation Lookup
HOW IT WORKS
About the IP Geolocation Lookup
The default result uses Regional Internet Registry statistics to show the country associated with the allocation. Administrators may separately enable a GeoLite estimate after reviewing the relevant data-provider terms. Neither result is a precise device location.
How to use this result
- Run the test from this server.Use a public hostname, address, prefix or ASN in the format requested above.
- Compare with another observation point.Run a local command or use a second provider to identify location-specific behaviour.
- Correlate related evidence.Use the related tools below to compare DNS, routes, ports, TLS and application responses.
- Keep the time and context.Routing, DNS caches and reputation data change, so record when the result was collected.
Common interpretation issues
- VPNs, mobile networks, corporate gateways and anycast can make the apparent location misleading.
- City-level results are less reliable than country-level results.
- Geolocation should not be used as proof of a person’s physical location.
NEED HELP INTERPRETING THE RESULT?
39D supports business networks, cyber security and managed IT.
For ongoing support or a larger infrastructure project, speak to the 39D team.
Frequently asked questions
Is this GPS data?
No. It is database-derived information about an IP allocation or observed network location.
Why does another site show a different location?
Providers use different registry, routing and observational datasets with different update schedules.