Summary

  • Registro.br gives owner-c administrative power over organization records and associated number-resource contacts.
  • The same documentation separates routing, abuse and technical contacts, so owner-c alone is not evidence of live network operation or BGP control.

Authority inside a registration system

The important verb is “administer”. Registro.br says the administrative contact can alter organization information and contacts associated with allocated Internet number resources. It also says the current owner-c assigns the other contacts through the resource-management system. This is consequential authority: an outdated or compromised administrative account can distort the public accountability map.

But the object of that authority is the registration system. It governs records and role assignments. It does not turn the named contact into every person or organization represented by those records.

Separate roles preserve separate meanings

The same official material distinguishes routing-c, abuse-c and tech-c. The routing contact may register transit information that becomes visible in Whois. The abuse contact receives and coordinates abuse communications related to resources announced by an ASN. The technical contact has a separate IP-block administration function.

Those distinctions are evidence, not administrative ornament. If owner-c were sufficient proof of routing, abuse response and technical operation, the separate contact roles would carry no analytical value. A single individual may occupy several roles, but each role must be established from its own field and checked at the relevant time.

What owner-c does not establish

The field does not show who has router credentials, who announces a prefix, which upstream carries traffic, whether a service is reachable or whether an abuse mailbox responds. It does not prove that the account holder works for the organization today. Nor does a registration-management role, without legal records, settle beneficial or legal ownership.

Operational, responsiveness and ownership claims require independent evidence suited to each claim. LACNIC presents directory access, IRR and RPKI as separate services; an analyst should preserve that separation rather than promote one administrative contact into proof supplied by another evidence surface.

A defensible statement

Record the queried object, the exact owner-c value, the source service and the retrieval time. Then say: “At the observation time, this registration record identified this contact as the administrative authority for organization data and resource-contact assignments.”

Any stronger claim needs a second evidence plane. The discipline is simple: registration authority can explain who may change the public record, but not who is moving packets behind it.

Sources