Skip to content

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.

Look up my IP ↗Start building →

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

YOUR CONNECTION

My IP lookup.

See your public IP address and its approximate location.

Press “Look up my IP” to pull your response. Nothing is requested automatically.

Uses one of your public website lookups. IP location is an estimate, not a precise physical address.

EVERY ANSWER HAS A SOURCE.

07tracked data
integrations

v4+v6IPv4 and IPv6
address support

◷Independent
source refreshes

{ }One predictable
REST API

01 / EXPLORE THE INTELLIGENCE

Look up another IP.

See the estimated location, network, and the data behind each result.

Example mode

10 sample lookups left today · Resets at 00:00 UTC

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 — PROVENANCE

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 FORpublished_at → activated_at

Read about freshness ↗⌘03 — LOCALIZATION

Make 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

Read the quickstart →

Readable JSON. Documented responses. REST API v1

CLEAR LIMITS. ROOM TO GROW.

Start with 1,000 free credits a month.

Explore the API for free. Choose more capacity when you need it.

Find your plan →

BEFORE YOU BUILD

What you need to know.

More in the docs ↗

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.

DEVELOPERS

Documentation

Integrate IP lookups and country controls into your application.

Autonomous System Number (ASN) lookup

An Autonomous System is a network or group of networks managed under one routing administration. Its Autonomous System Number (ASN) identifies it in internet routing. AS15169 is an example associated with Google.

GET /v1/asn/{number}

Authentication: asn scope on a server key. Credits: 1, including completed no match.

curl --fail-with-body --max-time 10 'https://orig.ooo/v1/asn/15169' -H "Authorization: Bearer $ORIGOOO_API_KEY"

Input and output

number is a decimal integer from 1 through 4294967295, without an AS prefix. The response is a representative matching network payload from IPtoASN, with asn, as_name and available country fields, plus reset_at. It is not a list of all prefixes for that ASN. Network country must not be treated as visitor location.

Failures

404 no_match means no record; 409 source_unavailable means IPtoASN is not active or approved for exposure. Missing scope returns 403. ASN/IP calls share account and network speed buckets. For an IP’s ASN use ordinary IP lookup and read separate ASN provenance when available.

Find the ASN behind an IP

curl 'https://orig.ooo/v1/ip/8.8.8.8?fields=asn,as_name,asn_source_id' \
  -H "Authorization: Bearer $ORIGOOO_API_KEY"

This IP request needs lookup scope. The standalone /v1/asn/15169 request needs asn scope. Preserve asn_source_id and asn_dataset_version separately from geography provenance. A missing ASN is unavailable coverage, not proof that the network is suspicious.