Is WHOIS Dead? Why RDAP Is Replacing It
When people look up domain registration information, they still call it "a WHOIS lookup" — but most modern lookup tools aren't actually speaking WHOIS at all anymore. They're using an entirely different protocol called RDAP. The name stuck around, but the internals have already changed generations. This guide explains why that transition happened, and what this tool is actually calling under the hood.
1. The limits of classic WHOIS: text with no standard
WHOIS is a very simple protocol, dating back to the 1980s and formalized in RFC 3912. You connect over TCP port 43, send a domain name, and get back human-readable plain text. The problem is that this plain text has no standardized format. Field names and line-break conventions differ from registrar to registrar and from registry to registry, which meant that any program trying to parse it automatically had to maintain a separate set of parsing rules for every registrar. Whenever a new registry appeared, or an existing one tweaked its format slightly, parsers would routinely break without warning.
2. RDAP: redesigned around structured responses
RDAP (Registration Data Access Protocol) is the standard that fixed this problem by rethinking it from the ground up. The IETF defined it across several RFCs, and it became widely established around 2021 once ICANN made support mandatory for gTLD (generic top-level domain) registries and registrars. There are three key differences.
| Aspect | Classic WHOIS | RDAP |
|---|---|---|
| Transport | TCP port 43, plain text | HTTPS (encrypted) |
| Response format | Text that varies by registry | Standardized JSON |
| Internationalization / access control | Effectively none | Unicode support, differentiated responses by requester |
RDAP looks up domain information via a RESTful HTTPS request, and no matter which registry the response comes from, it follows the same JSON schema — which means any program consuming it no longer needs registry-specific exception handling.
3. What this tool actually uses
Despite its name, this WHOIS lookup tool doesn't use the legacy WHOIS protocol at all. Looking at the source code, it sends an HTTPS request in the form fetch('https://rdap.org/domain/' + domain) to the RDAP broker service (rdap.org), parses the returned JSON, and displays the registrar, registration date, expiration date, and nameserver information on screen. If you open the "Raw WHOIS / RDAP data" toggle, what you see is the raw JSON — that's the actual RDAP response, not a legacy WHOIS text blob.
4. Why RDAP made GDPR compliance easier
Another reason RDAP gained traction is that its rise coincided with the GDPR (EU General Data Protection Regulation) era. Classic WHOIS worked on an all-or-nothing basis — either everything was public or everything was hidden. RDAP, by contrast, was built at the protocol level to return different content depending on the requester's authorization, which makes it much more natural to selectively mask registrant personal information depending on the situation. That's also why registrant personal-information fields in this tool's results are often empty or replaced with proxy information.
5. Why the name "WHOIS" still sticks around
From a user's perspective, the act of "looking up domain registration information" has long been called "a WHOIS lookup," so services tend to keep the WHOIS name out of sheer inertia. It's also worth noting that not every domain has fully moved to RDAP — ICANN's mandate applies to gTLD (.com, .net, .org, etc.) registries and registrars, while country-code domains (ccTLDs, e.g. .kr, .jp) vary by registry in whether they support RDAP at all. Some ccTLDs still only support classic WHOIS, so it isn't accurate to say "every domain is looked up via RDAP."
Frequently Asked Questions
Q. Does this tool actually use the real WHOIS protocol (port 43)?
A. No. Per the source code, it only uses RDAP — an HTTPS request to https://rdap.org/domain/{domain}. There is no legacy WHOIS logic connecting over TCP port 43.
Q. Which is more accurate, RDAP or WHOIS?
A. Accuracy is identical, since both pull from the same registration data. The difference is how reliably it can be parsed — RDAP's standardized JSON carries a much lower risk of parsing errors.
Q. Is every domain looked up via RDAP?
A. Most gTLDs (.com/.net/.org, etc.) support RDAP thanks to the ICANN mandate. Some country-code domains (ccTLDs) don't support RDAP yet and are only reachable via legacy WHOIS.
Q. Why is registrant personal information missing from RDAP responses?
A. Since regulations like GDPR took effect, most registrars redact or proxy the registrant's real name, email, and phone number by default. The RDAP protocol itself was designed to support this kind of differentiated disclosure.