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.

Mixed adoption — .de and others may offer web WHOIS only; tool handles per-TLD behavior.

Will WHOIS port 43 disappear?

Gradually for gTLDs per ICANN policy; expect RDAP-first tooling for new automation.

Can I convert WHOIS text parsers to RDAP?

Yes — map RDAP events to expiry/updated dates and entities to registrar/abuse roles; DN01 already normalizes both for manual use.

Does DN01 show raw RDAP JSON?

The UI emphasizes readable cards; use registry RDAP URLs directly when you need machine parsing beyond normalized fields.

Guides

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.

Open WHOIS2026-06-23

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.

Automation should prefer RDAP JSON when building internal tools; humans benefit from DN01 formatted cards either way.

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.

RDAP error responses use HTTP status codes — easier to distinguish «domain not found» from rate limiting in scripts.

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.

When RDAP returns 404 bootstrap errors, verify TLD supports RDAP or fall back to registry web WHOIS.

Parsing differences for scripts

WHOIS text varies by registry — regex parsers break when formatting changes. RDAP JSON uses stable field names for status, events, and nameservers.

Rate limits differ: port 43 may throttle by IP; RDAP may require Accept headers and return structured throttling errors.

For one-off checks, skip writing parsers — use DN01 WHOIS and copy normalized fields into tickets.

Choosing a lookup path per TLD

gTLDs (.com, .net, .org): RDAP bootstrap is standard — DN01 selects the right endpoint.

Many ccTLDs: registry web WHOIS or national RDAP server — DN01 handles per-TLD quirks.

When both protocols fail, check registry maintenance pages before assuming the domain is unregistered.

ICANN RDAP bootstrap files list HTTPS endpoints per TLD — update automation when bootstrap version changes quarterly.

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.
Will WHOIS port 43 disappear?: Gradually for gTLDs per ICANN policy; expect RDAP-first tooling for new automation.
Can I convert WHOIS text parsers to RDAP?: Yes — map RDAP events to expiry/updated dates and entities to registrar/abuse roles; DN01 already normalizes both for manual use.
Does DN01 show raw RDAP JSON?: The UI emphasizes readable cards; use registry RDAP URLs directly when you need machine parsing beyond normalized fields.