Do not reconstruct or redistribute underlying datasets without appropriate rights. Do not share keys, evade quotas, abuse credentials, perform malicious surveillance, or use approximate IP location as a guaranteed high-impact decision signal. The operator may suspend abusive access under finalized service terms.
IP GEOLOCATION · SOURCE DATA · LOCALIZATION
IP location.
With context.
Know where a request comes from—and what the data can tell you. Look up IP locations, compare sources, and build a more local experience.
1,000 free credits / monthNo credit card required.
IP ADDRESS8.8.8.8IPv4 ↗
↗
Mountain ViewUnited States · Illustrative result
LOCATIONUS United States
NETWORKAS15169 Google LLC
PROVENANCEAlways visible Source + version + freshness
Know the source. Understand the answer.{ } REST API
EVERY ANSWER HAS A SOURCE.
07tracked data
integrations
integrations
v4+v6IPv4 and IPv6
address support
address support
Independent
source refreshes
source refreshes
One predictable
REST API
REST API
01 / EXPLORE THE INTELLIGENCE
Look up an IP. See the source.
See the estimated location, network, and the data behind each result.
ILLUSTRATIVE DATA
🇺🇸
APPROXIMATE LOCATION
↗Mountain View, United States
IP address8.8.8.8
RegionCalifornia
Country codeUS
Time zoneAmerica/Los_Angeles
NetworkAS15169 · Google LLC
IP versionIPv4
ⓘ Sample response for exploration. IP locations are approximate, not GPS coordinates.
◎ Illustrative location
This preview uses example responses and a browser-local counter. Production lookups require the PHP service, approved datasets, and server-enforced quotas.
02 / GO BEYOND THE COORDINATES
More than a pin on a map.
Build for where people are.
And understand the data that gets you there.
01 — PROVENANCESee where the
“Up to date”
Make the first
See where the
answer comes from.
Compare available source results. See disagreements. Follow each answer back to its original dataset.
DB-IPGeoLite2+5 tracked
Explore the sources ↗02 — FRESHNESS“Up to date”
needs a timestamp.
Each source moves at its own pace. Know the version, the publication date, and when it became available.
EVERY VERSION, ACCOUNTED FOR
Inspect data freshness ↗03 — LOCALIZATIONpublished_at → activated_atMake the first
interaction local.
Country, phone, and language pickers. Server-side country policies. Small building blocks, less setup.
Try the building blocks ↗BUILD WITH A CLEAR API
One request.
Useful context.
A predictable REST API, readable responses, and examples in the languages you already use.
- IPv4 and IPv6 support
- Source-level provenance and freshness
- Clear errors and predictable credit usage
Readable JSON. Documented responses. REST API v1
How accurate is IP geolocation?
IP geolocation is an estimate. Country results are generally more stable than city results. Mobile networks, VPNs, and routing changes can affect location. ORIGOOO shows provenance and uncertainty rather than a numerical accuracy guarantee.
Are all seven integrations independent?
No. Distributions may mirror upstream records. ORIGOOO tracks lineage so mirrored datasets do not count as independent votes. The registry shows each integration’s role and readiness.
How do the free allowances work?
The public website allowance is 10 lookup actions per visitor per UTC day. Registered Free accounts receive 1,000 API credits per month. Standard lookups cost one credit and all-source comparisons cost two. The preview uses sample data only.
Can I use this to block access by country?
Country policies must be enforced on your server. A frontend widget alone does not secure content. SDK policies should define trusted proxies, caching, and how unknown locations and service outages are handled.
← Back to ORIGOOO
CLEAR EXPECTATIONS
Acceptable use
Operator policy draft · Commercial launch requires completed operator details and legal review.