1.8 KiB
1.8 KiB
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 |
IANA special-purpose | Not organizationally assigned | None | Unspecified address / “this host on this network” | No |
1.1.1.1 |
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:
- Classification — public unicast, private, loopback, documentation, multicast, reserved, or another special purpose.
- Registry chain — IANA → RIR → allocated/assigned resource holder.
- Route origin — currently announced covering prefix and origin ASN.
- Network operator — entity operating the route or service.
- Service — what the exact address does, if publicly documented.
- Infrastructure relationships — IXPs, facilities, upstreams, cables, and geography where evidence permits.
- 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. Use the IP record template for new exact-address pages; its first section must answer Who is this IP? Range-level knowledge is indexed in registry-ips/, using sortable filenames such as 001-001-001-000--24--apnic.md.