.png&w=3840&q=75)
Domain Name Search3 min
Navigating RDAP Structured Data After the WHOIS Transition
NS
NameSilo Staff10/8/2026
Share
The transition from WHOIS to the Registration Data Access Protocol (RDAP) replaces messy, plain-text domain lookups with highly structured, machine-readable JSON data. To read RDAP data, developers must query an HTTPS bootstrap server. The returned JSON object cleanly separates domain statuses, registrar details, and redacted contact entities, making programmatic parsing and threat intelligence automation significantly easier.
What Is the Registration Data Access Protocol?
RDAP is the IETF and ICANN-standardized replacement for WHOIS, defined across RFC 7480 through 7484, with RFC 9083 specifically governing the JSON response format. ICANN formally sunset legacy WHOIS for gTLDs on January 28, 2025. Where a WHOIS query returned unpredictable plain text that varied by registrar, RDAP returns a consistent JSON schema over standard HTTPS, with defined fields, defined types, and a defined place in the response every time.
Why It Matters: The End of Regex Soup
Scraping legacy WHOIS at scale meant writing separate parsing logic for every registrar's own output formatting, port 43 sockets, inconsistent field labels, and no standardized structure to rely on. RDAP eliminates that entirely. One consistent JSON schema now applies across the ecosystem, meaning a single parser handles domains from any registry without registrar-specific regex.
Deconstructing the JSON Tree
Two arrays carry almost everything a developer actually needs.
The events array holds lifecycle timestamps, each entry pairing an eventAction with an eventDate in ISO 8601 format:
"events": [ {"eventAction": "registration", "eventDate": "1997-09-15T00:00:00Z"}, {"eventAction": "expiration", "eventDate": "2028-09-14T00:00:00Z"}, {"eventAction": "last changed", "eventDate": "2024-08-14T00:00:00Z"}]To find an expiration date programmatically, filter this array for the entry where eventAction equals "expiration", then read its eventDate. That single field replaces the fragile string-matching most legacy WHOIS scrapers relied on.
The entities array holds registrar and contact information, each entity tagged with a roles field (registrar, registrant, administrative, technical) identifying exactly what it represents.
Handling GDPR Redactions
Registrant name and contact fields are redacted across nearly every domain today, in RDAP just as they were in WHOIS. The difference is consistency. Rather than dozens of registrar-specific placeholder phrases, RDAP standardizes redacted entities into a predictable structure your parser can detect reliably, rather than guessing at whatever text string a particular registrar happened to use.
Common Mistakes
Querying the wrong TLD-specific RDAP server: Every TLD routes to its own registry RDAP server, and hitting the wrong one returns a plain 404 rather than useful data. A bootstrap lookup service like rdap.org solves this by automatically redirecting your request to the correct registry endpoint for whatever domain you're querying, removing the need to hardcode a TLD-to-server mapping yourself.
What This Means for You
NameSilo's own WHOIS lookup already runs on RDAP behind the scenes, even though the page itself is still labeled WHOIS for familiarity. For direct programmatic access, NameSilo also exposes an open RDAP endpoint at rdap.namesilo.com/domain/<domain>. Note that reasonable rate limits apply to this public endpoint, so build retry logic accordingly for bulk lookups. Review the API Reference for additional automated domain management options.
Frequently Asked Questions
What is the difference between WHOIS and RDAP?
RDAP returns structured JSON with a standard schema, WHOIS returned unpredictable plain text.
Is WHOIS being phased out?
Yes, ICANN formally sunset legacy gTLD WHOIS on January 28, 2025.
How do I read RDAP JSON data?
Parse the events array for dates and the entities array for contacts.
What is an RDAP bootstrap server?
A routing service directing your query to the correct TLD-specific RDAP server.
Does RDAP show private domain owner info?
No, registrant contact data remains redacted for privacy, same as WHOIS.
How do I query an RDAP server?
Send an HTTPS GET request to the correct registry endpoint for that TLD.
Why is my WHOIS script failing?
Legacy WHOIS access for gTLDs has been sunset in favor of RDAP.
Does NameSilo support RDAP lookups?
Yes, both through the WHOIS page and a dedicated public RDAP endpoint.
.png&w=2048&q=75)
NameSilo StaffThe NameSilo staff of writers worked together on this post. It was a combination of efforts from our passionate writers that produce content to educate and provide insights for all our readers.
More articleswritten by NameSilo
.png&w=3840&q=75)
.png&w=3840&q=75)