What RDAP is and what happened to WHOIS
Learn how modern RDAP registration data differs from familiar WHOIS lookups—and why neither should decide whether a domain can be purchased.
WHOIS is the name many people know for looking up public information about a registered domain. RDAP—the Registration Data Access Protocol—is the newer, structured way for clients to request much of that information. The important practical point is simple: registration data and purchase availability are related, but they are not the same question.
What a registration-data lookup can show
Depending on the registry, registrar, and privacy rules, an RDAP result may include the domain name, registrar, important dates, nameservers, status codes, and DNSSEC state. Modern results are machine-readable, which makes labels and error handling more consistent than the plain-text WHOIS protocol.
Some fields may be redacted. Privacy laws, registry policies, proxy services, and the type of registrant all affect what is public. A short result does not imply that the registration is suspicious or incomplete.
Why WHOIS did not simply disappear
People still use “WHOIS lookup” as a familiar description, and some WHOIS services remain available. RDAP improves transport security, internationalization, structured responses, and referral behavior. It is better suited to modern software, but the public vocabulary changes more slowly than the protocol.
That is why Doory uses the public label WHOIS / RDAP Lookup when such a tool is available, while a custom implementation would use RDAP internally.
Availability is a separate authority
An RDAP “not found” response does not prove that you can register a domain. A registry can reserve a name, withhold it, classify it as premium, impose eligibility rules, or return incomplete registration data. Conversely, a domain may appear registered even while it is in an expiration or redemption process that prevents a normal new registration.
Doory’s domain availability search relies on the client portal and its connected registrar for ordering decisions. That system confirms supported endings, current pricing, premium status, eligibility, and the checkout path. RDAP is educational registration data, not a shopping authority.
How to read a result responsibly
Pay attention to the source, lookup timestamp, status codes, and redaction notices. Dates can have different meanings: a registry event date is not always the date a website began operating, and an expiration date does not guarantee immediate public availability afterward.
If you are investigating an important business domain, save assumptions for the registrar. Use registration data to understand the record, then use the availability and account system for purchasing or renewal actions.
The useful conclusion
Think of RDAP as the organized public record and the registrar as the transaction desk. Each answers a different question. Keeping those roles separate prevents a missing lookup from becoming an expensive domain decision.
Related service:Search and manage domains.