What RDAP can tell you
Registration Data Access Protocol, or RDAP, provides structured registration information for many domain names. A domain record may identify the sponsoring registrar, list important events and show status codes applied to the domain. It is useful when you need to check a domain you manage or understand the registration state of one you are considering.
RDAP is a view of registration data, not a complete account history. The information returned depends on the domain’s registry and the data available to the service you use. Contact details may be hidden or redacted for privacy, so an absent name or email address does not necessarily mean the record is incomplete.
Find and read the right record
Enter the full domain name into an RDAP lookup service that directs queries to the appropriate registry, or use an RDAP service provided by the relevant registry or registrar. Check that the result names the domain you intended: a similar spelling or a different top-level domain can lead to a convincing but irrelevant record. Internationalized domain names may appear in their encoded form, beginning with “xn--”.
Look for the registrar, nameservers, status codes and an events list. RDAP typically labels events rather than presenting an unlabeled row of dates, which makes it easier to distinguish registration from later changes. If a lookup returns no record, confirm the spelling and try a suitable service before concluding anything about the domain. A failed query or unavailable service is not proof that a name can be registered.
Understand registration and expiration dates
An event labeled “registration” generally indicates when the domain was first registered in the current registry record. An “expiration” event indicates the end of the registration term currently reported. A “last changed” event means the record was updated, but it does not, by itself, explain what changed. Other events may appear, and not every record includes the same set.
Read the timestamp as well as the event label. RDAP dates commonly include a time and a time-zone offset, so a date may look different when displayed in your local time zone. If you are comparing results from two tools, account for that difference before treating them as inconsistent.
Most importantly, an expiration date is not an availability date. A domain may be renewed, held in a post-expiration stage or subject to other registry and registrar processes. If the domain is yours, check its renewal settings and account notices with your registrar rather than relying on RDAP alone to plan a last-minute renewal.
Interpret status codes in context
Status codes describe restrictions or conditions recorded for a domain. For example, a transfer-prohibited status generally indicates that a transfer is blocked, while a hold status may prevent the domain from resolving in DNS. Some restrictions are set by a registrar; others are set at the registry level. The precise effect depends on the code, so read its description rather than guessing from a shortened label.
A status code does not always signal a problem. Transfer restrictions, for instance, can be part of routine domain protection. Likewise, a domain can have an active registration record while its website is unreachable because of DNS settings, hosting problems or another connectivity issue. If a status looks unexpected on a domain you control, check your registrar account and ask the registrar what triggered it before changing settings.
Use RDAP as one part of a domain check
For a domain you manage, compare the RDAP result with your registrar dashboard. Confirm that the domain spelling, registrar, expiration date and nameservers match what you expect. If a recent renewal or nameserver change is not reflected, allow for the possibility that the view you are using has not updated yet, then verify directly with the registrar.
For a domain you do not manage, treat RDAP as a source of clues, not permission to use the name or a promise that it will become available. Avoid sharing unredacted registration details when asking others for help, and never include account passwords, recovery codes or payment information in a lookup or support screenshot. A careful reading of the record can answer basic registration questions while keeping more consequential decisions tied to the registrar that manages the domain.



