RDAP vs WHOIS
rdap vs whois · rdap domain lookup · registration data access protocol
Compare RDAP and classic WHOIS for domain registration data, JSON output, rate limits, and when DN01 uses each protocol.
By DN01 Network Team
RDAP (Registration Data Access Protocol) replaces legacy WHOIS for many gTLDs with HTTPS, JSON, and standardized error codes. Operators still say «WHOIS lookup» colloquially.
DN01 WHOIS tool abstracts the difference — you get consistent cards whether the registry answered on port 43 or RDAP.
Why registries migrate to RDAP
Structured data eases parsing and localization of status fields.
HTTPS enables authentication tiers for accredited users while keeping public redaction.
ICANN policy pushes gTLD RDAP bootstrap — WHOIS sunset timelines vary by TLD.
Operator workflow unchanged
Same questions: who is registrar, when expires, which nameservers, any locks?
Automation should consume RDAP JSON when available; human review uses DN01 formatted output.
Cross-check DNS delegation after every NS change regardless of lookup protocol.
Frequently asked questions
- Can I query RDAP manually?
Yes via HTTPS bootstrap URLs per TLD — DN01 wraps this for quick checks.
- Does RDAP show more data?
Not more personal data post-GDPR — mostly better structure and error handling.
- Do ccTLDs use RDAP?
Mixed adoption — .de and others may offer web WHOIS only; tool handles per-TLD behavior.