The IP Geolocation Lookup estimates the country, region, city, network organization, and related metadata associated with a public IP address. Treat it as network-database inference, not GPS.
What to enter?
Use a valid public IPv4 or IPv6 address. Private addresses such as 192.168.x.x, 10.x.x.x, and 172.16–31.x.x do not have meaningful public geolocation because they are reused inside private networks.
How to interpret the result?
Country and network/ASN ownership are often more useful than city. A city can represent the ISP’s aggregation point, mobile core, VPN exit, satellite gateway, or registration address rather than the device’s physical location.
Example diagnosis
If a customer says a VPN is active, compare the visible public IP and organization before and after connecting. A change to a known VPN/cloud ASN supports the explanation that traffic exits elsewhere. It still does not prove the user’s identity or exact location.
Common reasons the estimate looks wrong
- Mobile carriers pool addresses across large regions.
- CGNAT makes many customers share provider infrastructure.
- VPN/proxy/Tor exits replace the user’s normal public path.
- IP blocks can be reassigned faster than every geolocation database updates.
Privacy and limitations
Do not use approximate IP geolocation to make claims about a person’s street address, presence, or identity. For fraud/security decisions, combine network metadata with authorized application/account evidence rather than treating a city estimate as proof.