# IP address map

The question “who owns this IP?” usually has several different answers. This directory separates registration, routing, operation, and service instead of forcing them into one unreliable `owner` field.

## Initial records

| Address | Registry classification | Registered resource holder | Current route origin | Operator/service | Globally routable |
|---|---|---|---|---|---|
| [`0.0.0.0`](ip/0.0.0.0.md) | IANA special-purpose | Not organizationally assigned | None | Unspecified address / “this host on this network” | No |
| [`1.1.1.1`](ip/1.1.1.1.md) | APNIC public resource (`1.1.1.0/24`) | APNIC Research and Development | AS13335, Cloudflare | Cloudflare 1.1.1.1 recursive DNS service; APNIC–Cloudflare project | Yes |

## Ownership model

For every address, investigate these independently:

1. **Classification** — public unicast, private, loopback, documentation, multicast, reserved, or another special purpose.
2. **Registry chain** — IANA → RIR → allocated/assigned resource holder.
3. **Route origin** — currently announced covering prefix and origin ASN.
4. **Network operator** — entity operating the route or service.
5. **Service** — what the exact address does, if publicly documented.
6. **Infrastructure relationships** — IXPs, facilities, upstreams, cables, and geography where evidence permits.
7. **Time and provenance** — registry and routing facts can change, so every claim needs a source and verification date.

The canonical structured records are in [`data/ip-addresses.csv`](../data/ip-addresses.csv). Range-level knowledge is indexed in [`registry-ips/`](../registry-ips/README.md), using numerically sortable IP-first filenames such as `001-001-001-000--24--apnic.md`.