RDAP vs WHOIS: What Changed?

RDAP and WHOIS both provide domain registration information, but they use different formats and access methods. RDAP is an HTTP-based, structured protocol with JSON responses; traditional WHOIS is commonly a plain-text query and response. For generic top-level domains, RDAP is the current standard service.

How the formats differ

An RDAP domain query has a defined URL pattern, and its response can express events, entities, statuses, links, and notices in named fields. Software can interpret those fields more reliably than prose with provider-specific labels. WHOIS output often varies across servers, which makes automated extraction harder. Structured format does not make an inaccurate source automatically accurate.

The same registration can still yield different visible fields. Access policy, privacy redaction, server implementation, and the time of each request all matter. A missing contact in RDAP is not proof that WHOIS holds a public contact.

Why WHOIS still appears

Some domain endings and lookup paths continue to rely on WHOIS. A tool may try RDAP first and use WHOIS when needed or available. That fallback is a coverage decision, not a sign that WHOIS is newer or more authoritative. WhoisFind follows that pattern for supported lookups; its results should be read with their source and timing in mind.

Do not confuse either protocol with DNS. RDAP and WHOIS concern registration; DNS describes records used to reach services. A domain can have an RDAP record while its A query returns no address.

A useful comparison workflow

Look up the same exact domain at /whois, identify the data source, and focus on stable fields such as domain, registrar, status, and events. If a result affects a transfer or renewal, verify it with the responsible registrar. Treat redacted or unavailable fields as unknown. The WHOIS guide explains the older response in more detail.

Sources

• RFC 9082: RDAP query format
• RFC 9083: RDAP JSON responses