RDAP (Registration Data Access Protocol) is the ICANN-mandated replacement for the 1980s WHOIS protocol. It returns the same registration data (registrar, dates, name servers, contacts) as structured JSON over HTTPS, with standardized fields and proper redirects between registries. As of 2025 all gTLD registrars are required to run RDAP; WHOIS remains only for legacy compatibility. Try both side by side with Zro7 WHOIS/RDAP.
WHOIS vs RDAP at a glance
- Transport: WHOIS = plaintext TCP/43 · RDAP = HTTPS.
- Format: WHOIS = free-form text (every registry different) · RDAP = JSON with a fixed schema.
- Internationalization: WHOIS = ASCII-only · RDAP = full Unicode.
- Access control: WHOIS = anonymous · RDAP = supports authentication (tiered access for law enforcement).
- Redirects: WHOIS = manual referrals · RDAP = HTTP 302 to the authoritative server.
Why the switch happened
- GDPR made publishing personal contact data risky — RDAP allows structured redaction ('privacy' fields).
- Parsers kept breaking because every registry formatted WHOIS text differently.
- TLS was overdue — WHOIS-over-port-43 is fully plaintext.
- IDN domains needed a protocol that supports non-ASCII correctly.
What an RDAP response looks like
ldhName: the domain in LDH form (e.g. example.com).status: array of EPP statuses (clientTransferProhibited, etc.).events: registration, last changed, expiration timestamps.entities: registrar and contacts with vCard-format details.nameservers: authoritative NS list.
Is WHOIS dead?
Not yet. Many ccTLDs (country-code TLDs like .de, .uk, .jp) still run WHOIS only. RDAP is mandatory for gTLDs (.com, .net, .org, .app, etc.). Best practice: try RDAP first, fall back to WHOIS.
How to look up a domain
- Open Zro7 WHOIS/RDAP.
- Type any domain.
- Read the standardized JSON view — no format guessing.
- Cross-check DNS with DNS Lookup.
Updated December 29, 2026 · Zro7 editorial team.
Zro7