RDAP: the structured successor to whois
2 min read
What RDAP is, how it differs from whois, and whether whois is dying. What the JSON-based protocol brings, and the honest state of adoption today.
Where whois shows its age
The whois protocol dates from 1982: answers are free text, every registry formats them differently, language and charset support is weak, and there is no access control. That is why every whois tool (ours included) must write per-registry parsers — "Created on……" and "Creation Date:" are two spellings of the same fact.
What RDAP brings
RDAP (Registration Data Access Protocol) serves the same data as JSON over HTTPS with standard field names. Dates look identical across registries, privacy can be tiered (authorised parties may see more), and referrals are standardised. ICANN made RDAP mandatory for gTLDs (com/net/org…) and formally ended the whois port-43 obligation in 2025 — the direction is clearly RDAP.
The honest state today
Whois still works widely (many registries keep port 43 running voluntarily) and ccTLD adoption of RDAP is gradual. Our tool queries via whois today; RDAP support is on the roadmap (SEO-NOTLAR) — once added, the two sources will cross-check each other.
Look up your own domain
Everything in this guide, our tool shows with live data in seconds: registration and expiry dates, registrar, nameservers, age and value analysis — free, no signup.
Query with WhoisFrequently asked questions
How can I try RDAP myself?
Even a browser works: query a domain through rdap.org and you are redirected to the registry's RDAP answer as JSON. For programmatic use this is the preferred method.
Is RDAP data more accurate than whois?
The source is the same registry ledger; the content does not differ. The difference is form: RDAP is machine-readable, consistent and immune to parsing mistakes.