WHOIS & RDAP basics

WHOIS vs RDAP — what changed and why

RDAP is the modern successor to WHOIS. Here's what's different and why it matters.

WHOIS has been around since the early 1980s. It worked, but it was built in a different era — single-byte text, no formal data model, no authentication, no way to internationalize names or addresses, no encryption in transit. As the internet grew and privacy laws caught up, the cracks started to show. RDAP, the Registration Data Access Protocol, is the modern replacement, designed by the IETF in cooperation with ICANN and the regional internet registries.

RDAP was finalized as a set of RFCs in 2015 and gradually rolled out across gTLD registries between 2018 and 2024. As of today, every ICANN-accredited registrar and gTLD registry is required to operate an RDAP service alongside (or instead of) classic WHOIS.

What RDAP changes

  • It returns structured JSON instead of free-form text, so tools can parse the data reliably instead of guessing at formats.
  • It runs over HTTPS, so queries and responses are encrypted in transit and authenticated by certificate.
  • It supports internationalized domain names and Unicode contact details out of the box, including non-Latin scripts.
  • It defines a standard set of object types (domain, entity, nameserver, autnum, ip) so the same lookup works the same way across different registries.
  • It supports rate limits, redirects, conditional access, and signed responses in a documented way, instead of every server inventing its own behavior.
  • It has a bootstrap registry maintained by IANA, so a client can discover the right RDAP server for any TLD automatically.

Why the switch happened

Two big forces pushed the move. First, the technical community had been frustrated for years with WHOIS's lack of structure: every registrar formatted their text response slightly differently, which made automated tools brittle, fragile, and a maintenance burden. Parsing an unfamiliar registrar's WHOIS output often meant writing a new regex from scratch. Second, the introduction of GDPR in May 2018 forced a rethink of how registration data is published. RDAP was already designed with access controls in mind — it can return different fields to authenticated clients than to anonymous ones — which made it the natural place to land.

There was also a security argument. Classic WHOIS runs in the clear, so a network observer can see both the query and the response. For sensitive lookups (e.g. an investigator researching a malicious domain), that exposure is not great. RDAP over HTTPS makes the conversation private.

What you'll notice as a user

For most lookups, the experience is the same: you type a domain, you get back facts about it. Behind the scenes, a tool that uses RDAP can show you cleaner data, handle international domains correctly, present consistent status codes, and reflect the registry's current privacy policies more accurately. Whoray uses RDAP wherever it is available and only falls back to classic WHOIS when a TLD has not yet adopted it.

Related guides