Summary

  • APNIC’s RDAP response for 1.0.0.0 gives the entity ORG-ARAD1-AP the role registrant, while separate entities carry administrative, technical and abuse roles.
  • RFC 9083 defines registrant as the registrant of the registration. That relationship is not, by itself, proof of beneficial ownership, corporate-group identity, BGP origin, transit or live network control.

A role inside a registration

The APNIC RDAP response for 1.0.0.0 is an IP-network registration object covering 1.0.0.0 through 1.0.0.255. Its embedded entity ORG-ARAD1-AP displays the name APNIC Research and Development and carries the role registrant. Other embedded entities carry administrative, technical and abuse roles.

That structure gives the field its proper scope. The role is not a free-standing description of everything the named organisation owns or operates. It states how an entity participates in the registration object that contains it. RFC 9083’s registered role definitions say that a registrant entity is the registrant of the registration and note that some registries call this a maintainer. The same registry of values separately defines technical, administrative and abuse responsibilities.

Responsibility is not an ownership deed

APNIC describes its Whois Database as an official record of organisations that hold IP addresses and AS numbers and as a service for finding who is responsible for a resource. That makes the record important evidence of registration responsibility. It does not make every label inside it a complete legal opinion about the organisation.

APNIC’s resource-registration guidance supplies a useful limiting principle: Internet addresses are shared public resources, APNIC does not sell them, and APNIC registers rights to use them under community policy. A registrant role therefore should not be paraphrased as ownership of an address in the ordinary property sense. Nor does one role establish beneficial ownership of the named company, resolve parent and subsidiary relationships, or prove that the displayed name is the only legally relevant identity.

If a legal or corporate conclusion matters, the analyst needs evidence designed for that question: corporate registries, transaction records, contracts, court records or verified statements from the parties. The RDAP entity handle and role remain part of the chain, but not its substitute.

Registration does not reveal the forwarding plane

The same boundary applies to operations. A registrant entry does not reveal which autonomous system currently originates the range, which networks provide transit, whether a route is accepted, where traffic terminates or who controls a service reachable at one address. Those claims require time-matched BGP observations, routing-policy records, measurements and operator evidence.

This is especially important when one organisation performs several functions. The response may correctly record APNIC Research and Development as registrant for this registration, yet the role alone does not collapse registry responsibility, routing operation, application hosting and corporate control into one fact. Each layer has its own evidence and clock.

Preserve the relationship, not an inflated conclusion

A defensible capture stores the parent network object, entity handle, exact role array, displayed vCard fields, response URL, retrieval time and response hash together. If the role or handle changes, the alert should say that APNIC’s registration representation changed. It should not announce a corporate acquisition, route transfer or operational handover unless another source establishes that event.

The resulting statement is both useful and narrow: APNIC’s response records ORG-ARAD1-AP as the registrant entity for this IP-network registration. Everything beyond that—legal ownership, group identity, routing authority and traffic control—remains a separate proposition requiring separate evidence.

Sources