Direct answer
RDAP is a public registration data protocol that can show visible information about a domain's registration, registrar, status and related metadata.
Plain-language explanation
RDAP stands for Registration Data Access Protocol. It is one way public registration information about a domain can be requested and returned in a structured format.
For .auDO, RDAP is useful because it can expose visible registration context such as registrar names, domain status values, registration dates and redaction patterns where those fields are publicly available.
Not every field is always present. Some information may be absent, redacted or unavailable depending on registry policy, data handling, privacy settings and the type of domain record being observed.
Why it matters
Registration context helps explain how a domain appears in public records at a point in time.
For governance readers, RDAP can help answer basic but important questions: which registrar appears responsible, what public status values are visible, which dates are available, and whether registration metadata appears stable or changing over time.
Repeated observations are valuable because they can show whether public registration metadata remains consistent, becomes unavailable, is redacted, or changes across the observed panel.
What .auDO observes
- whether RDAP data was available during collection
- visible registrar names where present
- visible domain status values where present
- visible domain dates where present
- absent, redacted or unavailable optional registration fields
- changes in public registration metadata across repeated observations
What a change may suggest
- registrar movement
- routine registration administration
- domain lifecycle activity
- a change in publicly visible status values
- a change in redaction or field availability
- a data availability difference at collection time
What it cannot prove
- who made an operational decision
- why a registration value changed
- whether internal records are complete
- whether a domain is well governed
- whether a supplier, registrar or operator acted correctly
- whether a missing field is abnormal without registry and operator context
Practical governance questions
- Do we know which registrar is responsible for important domains?
- Are registration dates and status values reviewed as part of domain administration?
- Are public registration records monitored for unexpected visible change?
- Do governance owners understand which RDAP fields may be redacted or absent?
- Are registrar, DNS and mail ownership records aligned internally?