What .auDO observes
Public registration evidence and its source path
Each RDAP response is a point-in-time public source record. .auDO preserves the source used, availability and selected fields so later observations can be compared without treating the source response as an ownership judgement.
Technical fields
Why it is observed
Registration evidence needs source context
Why it matters
RDAP keeps registration-side evidence distinct from DNS evidence and explains where registrar, status and redaction observations came from.
What visible change may mean
Differences may reflect registry or registrar updates, registration or administrative activity, redaction changes, source availability, fallback handling or representation differences.
Interpretation limits
What RDAP cannot establish
RDAP is public registration evidence, not proof of ownership, control, intent, governance maturity or private registration processes. Fields may be absent, redacted or represented differently by source.
Common retained observations
Source and registration changes
Where to use this evidence
Move from source context to current findings
Use RDAP State for aggregate registration posture, Methodology for source and fallback rules, and Reports for dated evidence.
Related concept
How RDAP works
Related signals