35 lines
1.7 KiB
Markdown
35 lines
1.7 KiB
Markdown
# 1.1.1.1
|
||
|
||
## Answer
|
||
|
||
`1.1.1.1` demonstrates why “owner” must be split into multiple relationships.
|
||
|
||
| Axis | Finding |
|
||
|---|---|
|
||
| Exact address | `1.1.1.1` |
|
||
| Registered covering prefix | `1.1.1.0/24` |
|
||
| Registry | APNIC |
|
||
| RDAP network name/type | `APNIC-LABS` / `ASSIGNED PORTABLE` |
|
||
| RDAP registrant | APNIC Research and Development |
|
||
| Current announced prefix | `1.1.1.0/24` |
|
||
| Current route origin | `AS13335` |
|
||
| Origin holder | Cloudflare, Inc. (`CLOUDFLARENET`) |
|
||
| Operator/service | Cloudflare 1.1.1.1 public recursive DNS resolver |
|
||
| Project relationship | APNIC–Cloudflare DNS Resolver project |
|
||
| Globally routed | Yes |
|
||
|
||
## Interpretation
|
||
|
||
- **Registration:** APNIC RDAP identifies the resource as `APNIC-LABS` and the registrant as APNIC Research and Development.
|
||
- **Routing:** RIPEstat reports `1.1.1.0/24` announced by `AS13335`, Cloudflare.
|
||
- **Operation/service:** Cloudflare publicly documents `1.1.1.1` as its consumer recursive DNS service.
|
||
- **Relationship:** APNIC RDAP explicitly describes an APNIC and Cloudflare DNS Resolver project and says the research prefix is routed globally by AS13335/Cloudflare.
|
||
|
||
Therefore, saying only “Cloudflare owns 1.1.1.1” loses important registry context. A more accurate statement is: **the covering prefix is registered through APNIC to APNIC Research and Development, while Cloudflare originates the route and operates the public resolver service as part of the documented collaboration.**
|
||
|
||
## Sources
|
||
|
||
- [APNIC RDAP record](https://rdap.apnic.net/ip/1.1.1.1), checked 2026-07-20
|
||
- [RIPEstat prefix overview](https://stat.ripe.net/data/prefix-overview/data.json?resource=1.1.1.1), checked 2026-07-20
|
||
- [Cloudflare launch announcement](https://blog.cloudflare.com/announcing-1111/)
|