IP geolocation lookup
Enter a public IPv4/IPv6 address or hostname. Hostnames are resolved locally first, and only the selected public IP is sent to the GeoIP provider.
IP geolocation is approximate
GeoIP associates an IP address with information inferred from network allocation, routing and geolocation databases. Country-level information is often useful, but city, postal code and coordinates must not be interpreted as the exact physical position of a device or person.
ASN, ISP and organization are related, but not identical
An Autonomous System Number identifies an autonomous routing domain in BGP. The organization associated with that ASN may be a carrier, cloud provider, CDN, enterprise or other network operator. The ISP field is provider metadata and should not automatically be interpreted as the end user’s contracted access provider.
A hostname can resolve to multiple locations
When a hostname is entered, this tool resolves its A and AAAA records locally before GeoIP lookup. A hostname can return multiple addresses because of load balancing, CDN, anycast, geographic DNS or infrastructure design. The page therefore shows which public addresses were found and which one was actually queried.
The visible IP may represent network infrastructure, not the user
VPNs and proxies can make traffic appear to originate from their exit infrastructure. CGNAT can place many subscribers behind shared public addresses. Mobile operators can route traffic through gateways far from the subscriber. These are normal reasons for a GeoIP result to differ from a person’s physical location.
Infrastructure IPs are especially easy to misinterpret
CDNs and anycast networks can advertise or serve the same service from many locations. A database may associate an anycast address with an operational or registration location that is not the physical server handling a specific packet. GeoIP is therefore context, not proof of packet path.
Private and special-purpose addresses are not sent to GeoIP
IANA maintains IPv4 and IPv6 special-purpose address registries. Addresses used for private networks, loopback, link-local, documentation and other reserved purposes do not represent ordinary globally reachable Internet endpoints. The integration rejects private/reserved inputs before contacting the external provider.
Hostnames are resolved before the external request
The external GeoIP integration receives the selected public IP, not the hostname typed into this page. Results are normalized by the portal integration layer and cached locally for a limited period. This reduces external requests, provider coupling and unnecessary disclosure of the searched hostname.
Different GeoIP databases can disagree
IP blocks move between operators, routing changes and geolocation providers use different data sources and correction processes. Two services can therefore return different cities or organizations for the same IP. For operational or legal decisions, verify the relevant information with routing and registration sources such as the appropriate Regional Internet Registry.