We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Accurately look up the street-level location and ISP details of an IP address. Supports both IPv4 and IPv6 parsing.
- Supports custom area (multi/single) and coordsys (WGS84/BD09).
- Supports both IPv4 and IPv6 addresses.
- When multiple areas are returned, all area details are displayed.
- Results are for reference only.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
An IP geolocation lookup associates an IPv4 or IPv6 address with network and location records. Depending on what is available for that address, this lookup can return country, continent, time zone, ISP, owner, data source, an AS number, country code, postal code, and one or more area entries. An area entry may include province or region, city, district, address text, radius, and longitude and latitude. Missing values are shown as a dash, and area details may be empty.
These are records associated with an IP address or network range, not a reading from the device’s GPS. Internet standards describe geolocation feeds with fields such as country, region, city, and postal code; those fields are optional and depend on the published data. See RFC 8805 for the feed format and RFC 9632 for how geofeed data is found and used.
A result can contain an address-like string or coordinates, but that wording does not establish that the IP belongs to a device at that street, building, or household. Network routing, shared public addresses, mobile gateways, VPNs, proxies, and hosting providers can all make the returned location differ from a person’s location. The English-language lookup results I reviewed for this US-focused query likewise emphasize approximate network location and distinguish it from a precise address. MaxMind’s published guidance says its IP geolocation data is not precise enough to locate a specific individual, household, or street address. This is a general limitation of IP geolocation, not a guarantee about any particular record.
Choose multi or single for the requested area mode, and choose WGS84 or BD09 for the coordinate representation. Multi mode can show multiple returned area entries; single mode asks for the single-area form. WGS84 and BD09 change how available coordinates are represented. Neither option adds location evidence or makes an IP-based estimate more precise. The service does not publish a US-only coverage statement here, so results and detail can vary by address and by the underlying location data.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter the IP address itself in IPv4 or IPv6 notation. A domain name, URL, or street address is not the input for this lookup.
Select single-area or multi-area output. Select WGS84 or BD09 if you need coordinates in a particular representation; the default is WGS84.
Start the query and complete any sign-in or usage prompt shown by the page. Review the summary fields, then inspect Area Details for any returned region, city, district, address, radius, or coordinates. Use Copy Result if you need to keep the displayed response.
If the input is rejected, remove surrounding spaces and punctuation and check that you copied the complete IP address. A syntactically plausible address can still have no location record. In that case the result may be unavailable rather than evidence that the address is invalid.
Use cases
See how the tool fits into real work and everyday tasks.
An administrator reviewing a sign-in or server log can use the country, ISP, owner, and AS number as leads about the network involved, then compare them with device, account, and access records before deciding what happened.
A network operator can look up a public address used by an organization and compare the returned location and provider fields with routing or registration records. A mismatch is a reason to investigate the records, not to infer a user’s whereabouts.
A support team can use the approximate region as one clue when investigating why a service selected a regional setting or challenged a login. Ask the user about VPN or mobile-network use and check other evidence before changing an account decision.
Q&A
Find concise answers to common questions and confusing cases.
No. It returns network-associated location data and does not establish a person’s identity or residence. Even when an address field appears, do not treat it as a verified street address; MaxMind’s public accuracy guidance also cautions that IP geolocation cannot locate a specific person, household, or street address.
The IP may be associated with an ISP gateway, a shared mobile-network exit, a VPN or proxy endpoint, or a hosting facility. The displayed place can describe that network infrastructure or its location record rather than the device using it.
The result can include these fields, but no definition or unit is provided with the lookup. Read them as raw returned values only; do not interpret them as a percentage, confidence score, or distance unless the data provider documents that meaning.
Location fields depend on available data and can be omitted. If the address has a valid format but the data source has no area entry, the lookup may still return summary fields or no detailed location. The geofeed standard itself makes locality fields optional.
Notes
Review scope, result limitations, and important precautions before use.
Use an IP address only when you have a legitimate reason to process it. An IP address can be sensitive in context, and the returned location is an estimate tied to network data. Do not use this output alone to identify, accuse, track, or locate a person, to prove someone’s physical presence, or as legal or forensic evidence. For account security or access decisions, combine it with other reliable signals and follow your organization’s privacy and retention rules. The lookup does not state a geographic coverage guarantee or explain its accuracy, consistency, or correctness fields; those omissions are intentional here rather than assumptions about the data.
Related
Discover related tools, collections, and available API capabilities.