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.
See the estimated location, network, and the data behind each result.
This preview uses example responses and a browser-local counter. Production lookups require the PHP service, approved datasets, and server-enforced quotas.
Build for where people are.
And understand the data that gets you there.
Compare available source results. See disagreements. Follow each answer back to its original dataset.
Each source moves at its own pace. Know the version, the publication date, and when it became available.
published_at → activated_atCountry, phone, and language pickers. Server-side country policies. Small building blocks, less setup.
Try the building blocks ↗A predictable REST API, readable responses, and examples in the languages you already use.
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.
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.
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.
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.
Use one API for IPv4 and IPv6, with exact range validation and explicit reserved-address errors.
The importer normalizes 128-bit range boundaries without float conversion. Documentation, private, multicast and reserved addresses are rejected.
An adapter may have different coverage across address families. Import the appropriate official data files and inspect source readiness rather than assuming every dataset is complete.
GET /v1/ip/2001:4860:4860::8888