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.
integrations
address support
source refreshes
REST API
Look up an IP. See the source.
See the estimated location, network, and the data behind each result.
Mountain View, United States
This preview uses example responses and a browser-local counter. Production lookups require the PHP service, approved datasets, and server-enforced quotas.
More than a pin on a map.
Build for where people are.
And understand the data that gets you there.
See where the
answer comes from.
Compare available source results. See disagreements. Follow each answer back to its original dataset.
“Up to date”
needs a timestamp.
Each source moves at its own pace. Know the version, the publication date, and when it became available.
published_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 ↗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
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.
Privacy policy
Account and request data support authentication, quotas, security, billing, and service operations. Review the deployment policy before collecting production data.