Read a saved domain registration record with its source
Admin ·
A registry response describes what its source reported when the record was obtained. Record that source and time before interpreting the dates.
Identify the recorded registration event
In an RDAP domain record, registration, last changed and expiration are different event actions. A registration on 2020-05-01 and a change on 2024-07-01 describe different events. Use the registration event for the creation field.
Read an unavailable value in context
A redacted array can declare fields that a registry removed or replaced. An absent field alone cannot establish why the value is missing. An RDAP errorCode of 404 is an unavailable record, while 429 records a rate-limited response.
IETF RFC 9537 — Redacted Fields in RDAP ResponsesIETF RFC 9083 — JSON Responses for RDAP
Trace two different registration dates
A registrar transfer may add a transfer or update event after the original creation event. Find the event name next to each timestamp before quoting a domain’s age. The latest change date is useful history but measures a different event.
If a WHOIS capture contains only an expiry field, report the expiry and leave the creation date unknown. Keep the provider and capture date with the export so a later reader can judge its age.
Common questions
Is the source URL opened?
The source is recorded as text. An HTTP source URL in the report retains its origin and path and omits embedded credentials, query parameters and fragments.
Which WHOIS dates are read?
Supported English creation, update and expiry labels are read when their values use an ISO calendar date or a timestamp with an explicit offset. Other formats stay unavailable.