RDDSRecord

Registration data for a taken domain, normalised across RDAP and WHOIS. source names the protocol that produced the record; RDAP records carry the full directory metadata (notices, links, conformance), while WHOIS records populate the subset they can and leave those empty. Contact fields are reproduced verbatim; a withheld field is reported through the entity's redacted flag and remarks, with redaction giving the registry's a-priori posture.

  • Resource type identifier.

  • Registrar of record with abuse contact, derived from the registrar entity.

    Properties: 6
  • Parties associated with the domain, keyed by role, nesting preserved.

    Properties: 13
  • Delegated nameservers with their own status and events.

    Properties: 4
  • DNSSEC delegation posture.

    Properties: 3
  • Every lifecycle event verbatim; the derived date fields are projections of it.

    Properties: 4
  • RDAP directory links (empty for WHOIS).

    Properties: 6
  • Response-level notices: terms of use, status glossary, inaccuracy form (RDAP only).

    Properties: 5
  • Object-level remarks explaining redaction (RDAP only).

    Properties: 5
  • WHOIS referral server advertised by an RDAP response.

  • rdapConformance / ICANN profile flags (RDAP only).

  • Registry ldhName (A-label / punycode form) of the domain.

  • Verbatim port-43 WHOIS text; present only for a WHOIS-sourced record.

  • Registration date, projected from events.

  • Last-changed date, projected from events.

  • Registry expiration date, projected from events.

  • Registrar-reported expiration date, projected from events.

  • Timestamp the registry last updated its RDAP database, projected from events.

  • Date the domain last changed sponsoring registrar, projected from events. Absent unless the registry publishes a transfer event; a WHOIS-sourced record never carries one.

  • U-label (Unicode) form when the registry supplies it.

  • Registry's opaque domain object identifier.

  • Protocol that produced this record: "rdap" or "whois".

  • Registry redaction posture: "none", "gdpr", or "registry_specific".

  • Whether the registry permits a registrar privacy/proxy service for this TLD.

  • Whether a WHOIS response could not be fully parsed; always false for RDAP.

  • Registry lock states as RFC 5731 EPP status codes, canonicalized to the same vocabulary whether the record came from RDAP or WHOIS.