world-v1/network-v1
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: lead IP records with attribution answer

Browse Source
This commit is contained in:
jarvis-at-skic
2026-07-22 19:34:44 +00:00
parent 052306bafe
commit 652bd652d8
11 changed files with 111 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
address-book/ip-addresses.md
+1 -1
View File
@@ -21,4 +21,4 @@ For every address, investigate these independently:
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`.
The canonical structured records are in [`data/ip-addresses.csv`](../data/ip-addresses.csv). Use the [`IP record template`](ip/TEMPLATE.md) for new exact-address pages; its first section must answer **Who is this IP?** Range-level knowledge is indexed in [`registry-ips/`](../registry-ips/README.md), using sortable filenames such as `001-001-001-000--24--apnic.md`.
address-book/ip/0.0.0.0.md
+2 -2
View File
@@ -1,8 +1,8 @@
# 0.0.0.0
## Answer
## Who is this IP?
`0.0.0.0` is **not an ordinary public address owned by a company**. IANA records both the exact `0.0.0.0/32` address and its `0.0.0.0/8` parent as special-purpose protocol space.
**Short answer:** `0.0.0.0` belongs to no company or ordinary network operator. IANA reserves both the exact `0.0.0.0/32` address and its `0.0.0.0/8` parent as special-purpose protocol space.
| Axis | Finding |
|---|---|
address-book/ip/1.1.1.1.md
+2 -2
View File
@@ -1,8 +1,8 @@
# 1.1.1.1
## Answer
## Who is this IP?
`1.1.1.1` demonstrates why “owner” must be split into multiple relationships.
**Short answer:** The covering range is registered to APNIC Research and Development, while Cloudflare routes `1.1.1.1` through `AS13335` and operates its public recursive DNS service. This split demonstrates why “owner” must be treated as several relationships.
| Axis | Finding |
|---|---|
address-book/ip/TEMPLATE.md
+26
View File
@@ -0,0 +1,26 @@
# <IP address>
## Who is this IP?
**Short answer:** <Name the registered holder and operator first. If they differ, say so immediately. If unknown, say “Unknown — investigation pending.”>
Do not begin with technical background. First answer whose registered resource contains the address, who currently routes it, and who operates the documented service when those are different entities.
| Axis | Finding |
|---|---|
| Exact address | `<address>` |
| Registered covering prefix | `<prefix>` |
| Registry | <registry> |
| Registered resource holder | <holder or unknown> |
| Current announced prefix | <prefix or none/unknown> |
| Current route origin | <ASN or none/unknown> |
| Operator/service | <operator and service or unknown> |
| Globally routed | <yes/no/unknown> |
## Interpretation
<Explain registration, routing, operation, and service relationships without collapsing them into one “owner.”>
## Sources
- [Authoritative source](https://example.invalid/), checked <YYYY-MM-DD>