IP Geolocation Lookup
Find the approximate city, region, country, timezone, coordinates, and network provider associated with a public IP address.
Approximate IP-based location. This is not a precise device or residential address.
๐ Location & Network Details
โน๏ธ Interpretation
๐งพ Raw API Result
Server-Side Lookup, Never a Browser API Key
This tool's .NET backend validates the IP address you enter, rejects private, loopback, link-local and reserved addresses, and then queries a trusted third-party geolocation provider entirely server-side - any provider credentials stay on the server and are never sent to your browser. Results are normalized into a consistent format and cached by IP for a while to reduce repeated provider calls. IP geolocation is inherently approximate: it typically reflects where an ISP or network registers an IP block, not a person's exact address, and fields the provider doesn't know (postal code, coordinates, accuracy radius) are always reported as genuinely missing rather than guessed. "Use My IP" only trusts proxy-supplied headers like X-Forwarded-For when your request actually arrives through an operator-configured trusted proxy - otherwise it uses the IP address your connection is actually coming from, so it can't be spoofed by a header a client sets itself.
What else can you check?
These tools all work on the same connection and address data — pick whichever question you actually have.
IP Geolocation Lookup FAQ
How accurate is IP geolocation?
It's an approximation based on how the IP address range is registered and routed - usually accurate at the country or region level, often accurate at the city level, and rarely precise enough to identify a specific address or device.
Why are some fields missing for certain IPs?
Not every IP address has full registration data, and our provider doesn't classify every address for VPN, proxy, hosting or mobile-network use - when a field is genuinely unknown, it's returned as missing rather than guessed.
Can I look up a private or internal IP address?
No. Addresses in private, loopback, link-local or reserved ranges are rejected before any lookup happens, since public geolocation data doesn't apply to them.
Does "Use My IP" trust any header my browser sends?
No. It only reads proxy-forwarded address headers when your connection is confirmed to be coming through an operator-configured trusted proxy; otherwise it uses the address your connection is actually arriving from.
Why does a repeated lookup return instantly?
Results are cached by IP address for a period of time to reduce load on the upstream provider - looking up the same IP again shortly after will return the cached result rather than making a new provider call.
What powers the map?
A real, interactive map built with Leaflet and OpenStreetMap tiles - free, open data, no API key. It's centered on the coordinates the geolocation provider actually returned; if a lookup doesn't include coordinates, the map area says so plainly instead of showing a fake location.