
Domain registration data as clean JSON across 1,200+ TLDs, through RDAP, the official WHOIS replacement. 7-day free trial, from $9/month.
A startup from France.
This page is designed to help you find out whether RDAP API is good and if it is the right choice for you.
RDAP API turns domain registration data into one consistent JSON format. It queries RDAP, the official replacement for WHOIS, for more than 1,200 TLDs, and falls back to the registry's WHOIS server where no RDAP server exists.
Plans start at $9 per month for 30,000 requests, with a 7-day free trial.
Listed in
PHP and Laravel, MariaDB, Redis, Vue.js with Inertia, and Stripe for billing.
It reads registration data from the registries themselves over RDAP, the protocol that ICANN made the replacement for WHOIS, and returns it in one JSON format for more than 1,200 TLDs. Where a TLD has no RDAP server, it reads the registry's WHOIS server and returns the same format, with the source stated in the response. For .com and .net, an optional follow mode also fetches the contacts held by the registrar. A public /tlds endpoint shows, for each TLD, which fields the registry actually fills.
Most WHOIS APIs sell records from their own database and price them for security teams: WhoisXML API costs $2.40 per 1,000 queries at one million per month. RDAP API answers from the registry, with at most 48 hours of caching, and costs between $0.20 and $0.30 per 1,000 requests. The response format is identical for every TLD, so there is no WHOIS text to parse and no per-registry exception to handle.
Developers who need domain registration data inside their own product: domain investors and availability checkers, brand protection and security tools, registrars, and companies that enrich lead or vendor data with domain information. Most usage is unattended automation.
ICANN ended the WHOIS obligation for gTLD registries in January 2025, and RDAP became the official source. RDAP is a better protocol, but every registry implements it slightly differently, and some TLDs still have no RDAP server at all. RDAP API was launched in March 2026 to absorb those differences, so that developers get one reliable format instead of maintaining their own parsers.
We have collected here some useful links to help you find out if RDAP API is good.
Check the traffic stats of RDAP API on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of RDAP API on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of RDAP API's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of RDAP API on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about RDAP API on Reddit. This can help you find out how popualr the product is and what people think about it.
Do you know an article comparing RDAP API to other products?
Suggest a link to a post with product alternatives.
Is RDAP API good? This is an informative page that will help you find out. Moreover, you can review and discuss RDAP API here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.