DEV Community

Cover image for RDAP vs WHOIS: How Domain Availability Is Actually Checked
Waseem Riaz
Waseem Riaz

Posted on

RDAP vs WHOIS: How Domain Availability Is Actually Checked

RDAP vs WHOIS: How Domain Availability Is Actually Checked

When you type a domain name into a search box and get an answer in seconds, something has to ask the internet who owns that name. For thirty years that something was WHOIS. Today, the modern answer is RDAP. They sound similar, but they work very differently, and the difference matters if you are picking a business name and want to know whether the domain is really free.

What WHOIS is

WHOIS is one of the oldest lookup protocols on the internet. It dates back to the early 1980s, when the network was small and everyone more or less trusted each other. You send a plain-text query to a WHOIS server, usually on port 43, and you get back a block of plain text: the registrar, the registration dates, the nameservers, and historically the registrant's contact details.

That simplicity became its problem. Every registry formatted its answers differently, so a tool had to parse dozens of layouts, and a small change in one registry's format could break the parsing. WHOIS has no standard way to say "this name does not exist" versus "the server is busy," and it has no built-in support for internationalised domain names. After privacy regulations changed what registries are allowed to publish, many WHOIS answers became heavily redacted, which made them less useful but no more consistent.

WHOIS still exists and is still used, but it is a legacy protocol. The internet's standards body has a clear successor, and most registries have already moved to it.

What RDAP is

RDAP stands for Registration Data Access Protocol. It is defined by a set of internet standards (RFC 7480 to 7485) and works over ordinary HTTPS, the same protocol your browser uses. Instead of free-form text, an RDAP server returns structured JSON data: the same fields every time, in the same shape, with explicit status codes.

That structure is the whole point. A 200 response means the domain exists. A 404 response means it does not. There is no parsing of free text and no guessing about what a particular registry meant. RDAP also has a built-in bootstrap service: a public list, maintained by IANA, that tells any client which RDAP server is authoritative for each top-level domain, from .com to .pk. A lookup can therefore go straight to the source of truth for that extension instead of through a middleman.

RDAP also handles privacy better. It supports authenticated tiers, so a registry can show more detail to accredited users and less to anonymous ones, without breaking the format. And because it runs over HTTPS, queries are encrypted in transit, unlike classic WHOIS.

Why this matters when you check a domain

If you are naming a business, you will usually check the same name across many extensions at once: .com, .ai, .io, .co, and the country code for your market. With WHOIS-based tools, each of those checks depends on a different text format, and a parsing failure can look like an error, or worse, like a wrong answer. With RDAP, each check is a structured query to the authoritative server for that extension, and the answer is unambiguous.

There is one important caveat that applies to every checker, RDAP or not. "Available" in a checker means that, at the moment of the check, the domain had no registration record and no DNS nameservers answering for it. Registries update constantly, and a name can be registered by someone else between your check and your purchase. That is why the last step should always be confirming at the registrar before you pay. A good checker gets you a shortlist in seconds; the registrar gives you the final word.

How CheckMyDomain checks

CheckMyDomain uses RDAP-based checking, backed by DNS lookups. For each name and extension, it first checks DNS records, then queries the authoritative RDAP server for that extension directly, using the IANA bootstrap list to find it. A domain is shown as available only when DNS finds no record and the authoritative RDAP server returns not-found. If either source says the name exists, it is shown as taken. That direct-to-authoritative approach also avoids the rate limits and blocks that come from routing every lookup through a single shared proxy service.

You can try it free, with no signup: describe your business, generate brandable name ideas, and check domain availability for each one in the same flow at https://www.checkmydomain.me/tool.

The short version

WHOIS was the internet's phone book: plain text, inconsistent, and built for a smaller internet. RDAP is its structured, HTTPS-based successor: consistent JSON, clear status codes, and one authoritative server per extension. If a domain tool still relies on WHOIS alone, its answers are only as good as its text parsing. If it uses RDAP, its answers come straight from the registry that owns the record. When you are choosing a name you might build a business on, that difference is worth knowing.

Top comments (0)