Treat coordinates as a centroid
Coordinates describe a database location for an IP range, not a measured device position. No accuracy radius is available, so extra decimal places do not mean street-level precision.
IP Geolocation Lookup
Estimate where an IPv4 or IPv6 address is used, then compare that database estimate with routing and registration evidence. Results clearly separate an approximate IP location from an exact device, person, or street location.
- IPv4 and IPv6
- Country, region, city and centroid
- Coarse reference map
- Route and ASN context
- Country-evidence comparison
- Source age and attribution
Run an IP geolocation lookup
Location data: IP Geolocation by DB-IP, used under CC BY 4.0. DB-IP City Lite reports approximate database centroids and supplies no accuracy radius, postal code, or timezone.
Location estimate
Approximate database location
Not reported
How precise is this?
The point is a database centroid associated with an IP range. It is not GPS, does not locate a person or device, and can be far from the user—especially for mobile carriers, VPNs, cloud services, satellite networks, and anycast addresses.
Approximate reference map
This schematic map is intentionally coarse. A marker shows only the database centroid and has no supplied accuracy radius.
Country evidence compared
Location, routing, and registration countries come from different datasets and answer different questions.
Why can the country fields disagree?
The geolocation country estimates where an address is used. Route country is context attached to an ASN route snapshot. Registration country comes from the RIR network object. VPN exits, anycast, mobile gateways, cloud networks, transferred blocks, and registry practices can make these differ without proving that any source is wrong.
Address and network context
Classification and network evidence help explain the location estimate; they do not prove ownership, ISP identity, or reachability.
Source freshness and provenance
Each source has its own observation or retrieval time. “Fresh” means within Octetify’s update policy, not real-time location.
Interpretation and limits
These boundaries should stay with screenshots, exports, and operational decisions.
Raw evidence
The complete normalized response used to produce this report.
Show raw JSON
How to use IP geolocation responsibly
Expect network effects
VPNs, corporate gateways, mobile carriers, CDNs, satellite links, and anycast can make an address appear in a different city or country from the user.
Do not infer a person
An address can be shared, reassigned, translated, or operated by an intermediary. This tool cannot identify a person, subscriber, household, device, or street address.
Compare independent evidence
A location estimate, route origin, and RIR registration describe different layers. Agreement is useful context; disagreement is a prompt to investigate, not proof of fraud.
Check data age
IP allocations and routing change. Use the source ledger to see when local datasets were retrieved and whether the report is partial or stale.
Know what is not tested
- No current reachability test.
- No VPN, proxy, Tor, abuse, or reputation verdict.
- No assertion that the AS description is the end user’s ISP.
- No postal code, timezone, or accuracy-radius estimate.
Primary references: DB-IP City Lite, IANA IPv4 Special-Purpose Registry, IANA IPv6 Special-Purpose Registry, and RFC 9224 RDAP bootstrap.