RDAP returns machine-readable JSON over HTTPS instead of the plain-text format used by legacy WHOIS, making it easier to parse and more secure.
Unlike WHOIS, RDAP natively supports internationalized domain names and contact information using standardized Unicode encoding.
ICANN requires all registries and registrars to support RDAP. It is the official replacement for WHOIS with built-in access control and authentication.
| Feature | RDAP | WHOIS |
|---|---|---|
| Protocol | HTTPS (RESTful API) | TCP port 43 (plain text) |
| Data Format | Structured JSON | Unstructured plain text |
| Authentication | Built-in support | None |
| Internationalization | Full Unicode support | ASCII only |
| Standardization | IETF RFCs 7480-7484 | Varies by registrar |
RDAP stands for Registration Data Access Protocol. It is defined by IETF RFCs 7480 through 7484 and provides a standardized way to query domain registration data over HTTPS.
Yes. ICANN has mandated that all gTLD registries and ICANN-accredited registrars must provide RDAP services. While legacy WHOIS servers still exist, RDAP is the official standard going forward and provides more reliable, structured data.
All gTLDs (.com, .net, .org, .io, .ai, .dev, .app, .xyz, etc.) are required to support RDAP. Many ccTLDs also offer RDAP services. Some restricted TLDs like .gov, .mil, and .edu do not provide public RDAP access.