Direct answer
The registry operates the domain namespace, the registrar provides the registration service to customers, and the registrant is the person or organisation that holds the domain licence or registration.
Plain-language explanation
A domain name is not just a website address. It sits inside a registration system with defined roles.
The registry is responsible for operating the namespace at a wholesale level. It maintains the authoritative registration layer for domains within that namespace.
The registrar is the provider that a registrant usually deals with to register, renew, transfer and administer the domain. The registrar relationship is often where billing, support, delegation changes and account access are handled.
The registrant is the domain holder. In an organisational context, this should map to clear internal ownership, even when a supplier or agency helps manage the domain day to day.
Why it matters
These distinctions matter because governance questions often get blurred. A domain may be used by communications, administered by technology, billed through finance, managed by a supplier and registered through a registrar.
When the visible registrar changes, it may reflect supplier consolidation, portfolio cleanup, account transfer, renewal management or routine administration. The public signal is useful, but it does not explain the internal reason by itself.
What .auDO observes
- registrar values visible through public RDAP observations
- domain status signals where available
- registration date metadata where available
- DNSSEC-related delegation signals where visible through registration data
- changes in registrar visibility between repeated observations
- aggregate registrar patterns across the fixed .auDO panel
What it can tell us
- which registrar was visible for an observed domain at collection time
- whether the visible registrar changed between observations
- whether registrar movement appears isolated or repeated across the panel
- whether a domain may be worth reviewing alongside DNS provider and nameserver context
- whether registration-layer signals align with expected domain administration records
What it cannot prove
- who internally owns the domain
- why a registrar changed
- whether a transfer was planned or unexpected
- whether the listed provider is responsible for DNS hosting, email or web hosting
- whether supplier arrangements changed beyond the public registration signal
- whether domain governance is effective on the basis of registrar data alone
Practical governance questions
- Who is the internal owner for each important domain?
- Who has access to the registrar account?
- Are registrar, DNS provider and hosting provider responsibilities documented separately?
- Are domain transfers reviewed before and after they occur?
- Do communications and technology teams share the same source of truth for domain ownership?
For a practical ownership check, use the Domain Governance Baseline to ask who owns, controls and remains accountable for each domain.