
DomainTools
WhoisAPI
zonefiles.io
WhoisFreaks
JsonWhois.io
Dymo
ILSERBY.net
Domain, IP, and DNS data provider

WhoisFreaks
DomainIndex.com WHOIS Database Download
ICANN WHOIS
WhoisJson
WhoisAPI
WhoisThisDomain
JsonWhois.io
Domain registration data as clean JSON across 1,200+ TLDs, through RDAP, the official WHOIS replacement. 7-day free trial, from $9/month.

Which is more popular?
Website, pricing, platforms and company facts side by side.
|
|
|
|
|---|---|---|
| Website | whoisxmlapi.com | rdapapi.io |
| Pricing | — | |
| Company | — | Startup from France · 1 - 9 employees · 2026 |
| Listed in |
In their own words, as submitted to SaaSHub.


No description of WhoisXML API yet.
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. Domain lookups: registrar, creation and expiry dates, nameservers,...
What each product offers, as listed by its team.


Possible disadvantages
No features have been listed yet.
How often each product is chosen within a category, 0–100% relative to the other.


As answered by people managing WhoisXML API and RDAP API.
RDAP API's answer:
PHP and Laravel, MariaDB, Redis, Vue.js with Inertia, and Stripe for billing.
RDAP API's answer:
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.
RDAP API's answer:
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.
RDAP API's answer:
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.
RDAP API's answer:
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.
Share your experience with using WhoisXML API and RDAP API. For example, how are they different and which one is better?
When comparing WhoisXML API and RDAP API, you can also consider the following products.

Domain name research, including comprehensive Whois Lookup, Reverse Whois Lookup and Whois History.
Compare DomainTools to WhoisXML API or RDAP API:

Domain & IP Intelligence API with Live and Historical WHOIS Data
Compare WhoisFreaks to WhoisXML API or RDAP API:

WhoisAPI is the premier provider of freshly parsed whois data for domain names and IP addresses...
Compare WhoisAPI to WhoisXML API or RDAP API:

Get domain price, keywords, searches, ngrams | Domainindex.com
Compare DomainIndex.com WHOIS Database Download to WhoisXML API or RDAP API:

List of registered domain names updated daily
Compare zonefiles.io to WhoisXML API or RDAP API:

The official ICANN WHOIS search for domain lookups.
Compare ICANN WHOIS to WhoisXML API or RDAP API: