WHOIS API Now Enhanced with RDAP-Ready Features

We’re excited to announce that WHOIS API is RDAP-ready, following the WHOIS port 43 shutdown and the expected transition from WHOIS to RDAP or the Registration Data Access Protocol—the next-generation system for accessing domain registration data developed by the Internet Engineering Task Force (IETF). 

Our development team implemented several developments to ensure users can continue to access fast, accurate, and up-to-date domain registration information with WHOIS API. Among the improvements made were:

• Auto protocol: With this mechanism, WHOIS API selects the best available data from RDAP or WHOIS based on real-time technical tests and server monitoring across TLDs since not all TLDs support RDAP. If WHOIS data is unavailable, the API automatically proceeds with running a RDAP query. When both protocols provide data of similar quality, WHOIS is prioritized to reduce client-side impact.

• RDAP parameter: Users can choose the retrieval method they prefer during WHOIS API lookups by specifying the RDAP parameter input value, which can be:

• 0 to retrieve data via Auto protocol. This is the default value.
• 1 to retrieve data via RDAP.
• 2 to retrieve data via the WHOIS protocol.

With these upgrades, WHOIS API users can:

• Experience continued data accuracy and reliability: Despite the major changes happening in the domain name industry, the Auto protocol ensures users always receive the best domain registration data available, reducing the risk of incomplete or outdated information.

• Greater flexibility and control: The optional RDAP input parameter offers customized data access based on users’ specific needs—whether they prefer automatic selection, RDAP only, or WHOIS only retrieval.

• Optimize system performance: Users integrating WHOIS API into their solutions can reduce unnecessary API requests since the API intelligently selects the best available source (WHOIS or RDAP) instead of making repeated calls to retrieve the same data. This results in faster response time, allowing solutions and pipelines to get quicker access to accurate domain registration data.

Check out the API documentation or contact us for more information about this upgrade and how you can use it for your specific needs.