RDAPAPI pricing: domain WHOIS API
Is RDAPAPI yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
- $9 monthlyStarter$0.30 per 1,000
- $49 monthly, ProPro$0.245 per 1,000
- $199 monthly, BusinessBusiness$0.199 per 1,000
- $90 yearlyStarter$0.25 per 1,000
- $490 yearly, ProPro$0.204 per 1,000
- $1,990 yearly, BusinessBusiness$0.166 per 1,000
GET / domain/ {domain} one of RDAPAPI's 2 callsAbout this item
- A copy at most 48 hours old. You get WHOIS records from RDAPAPI's database.
- All 9 fields on our checklist. Registrant, Registrar, Created on, Updated on, Expires on, Name servers, Statuses, DNSSEC, Abuse contact.
- A monthly subscription. You pay $9 a month for 30,000 requests. Calls stop once your requests run out.
- One call. You send
domaintoGET /. You can also senddomain/ {domain} followandwhois. The call returns the domain's WHOIS record. - Who can get it: anyone with an account. Keep data: no limit. Use data: with conditions.
RDAPAPI: domain WHOIS API alternatives
RDAPAPI alternatives: other domain WHOIS API providers by price
We list other providers' plans closest to this plan in price per 1,000 domains. Each plan in the table gives live data or data at most a week old.
| This planRDAPAPI, $9 monthly | WhoisJsonAPI, $129 monthly, Premium, GET /v1/{domain} | WhoisJSON, $100 yearly | HackerTarget, $2,400 yearly | domainIQ, $149.95 monthly, Expert, GET /api, 15,000 requests a day | |
|---|---|---|---|---|---|
| $ per 1,000 domains | $0.30 | $0.258 | $0.278 | $0.329 | $0.333 |
| Completeness | 100% | 78% | 89% | 89% | 56% |
| Billing | monthly | monthly | yearly | yearly | monthly |
| Pay | $9 | $129 | $100 | $2,400 | $149.95 |
| Enough for | 30,000 calls a month | 500,000 calls a month | 30,000 calls a month | 20,000 calls a day | 15,000 results a day |
| Freshness | 48 hours | 24 hours | 3 hours | live | live |
| Who can get it | anyone with an account | anyone | anyone at least 18 years old (or of legal majority in their jurisdiction), one account per individual or entity | anyone who pays for a membership and is not in the business of creating similar documents, goods or services to provide them for a fee to users | anyone 18 or older |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-07.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Registrant
- Registrar
- Created on
- Updated on
- Expires on
- Name servers
- Statuses
- DNSSEC
- Abuse contact
| $ per 1,000 domains | $0.30 |
|---|---|
| Per | call |
| Billing | monthly |
| $ a month | $9 |
| Also pays for | from the same budget: IP Address Lookup · ASN Lookup · Nameserver Lookup · Entity Lookup |
|---|
| Units cap | hard |
|---|
| $ per 1,000 | $0.30 |
|---|
| Their pitch | Clean JSON for any domain across 1,200+ TLDs, including the ones RDAP still doesn't cover. We find the right server, manage rate limits, and pull registrar data when it lives there. |
|---|
| Freshness | 48 hours |
|---|---|
| Keep data | no limit |
| Use data | You agree not to: Use the Service for any unlawful purpose. Attempt to circumvent rate limits or usage quotas. Resell API access without prior written consent. Interfere with or disrupt the Service infrastructure. Use the Service to harvest personal data in violation of applicable privacy laws. |
| Pay | $9 |
|---|---|
| You get | 30,000 requests a month |
| Enough for | 30,000 calls a month |
| Per second | 0.5 |
|---|---|
| Batch | 1 |
| Answer | in the call |
|---|
| You send | domain. Optional: follow, whois |
|---|---|
| Method | GET |
| Path | /domain/{domain} |
| Plan | Starter |
|---|---|
| Who can get it | anyone with an account |
The 64 fields the plan's answer can hold
domain name, Unicode domain name, domain handle, domain status, registrar name, registrar IANA ID, registrar abuse email, registrar abuse phone, registrar URL, creation date, expiration date, updated date, name servers, DNSSEC, registrant handle, registrant name, registrant organization, registrant email, registrant phone, registrant address, registrant contact URL, registrant country code, administrative handle, administrative name, administrative organization, administrative email, administrative phone, administrative address, administrative contact URL, administrative country code, technical handle, technical name, technical organization, technical email, technical phone, technical address, technical contact URL, technical country code, billing handle, billing name, billing organization, billing email, billing phone, billing address, billing contact URL, billing country code, abuse handle, abuse name, abuse organization, abuse email, abuse phone, abuse address, abuse contact URL, abuse country code, redaction details, answering server, data protocol (RDAP or WHOIS), RDAP server, raw RDAP URL, served from cache, cache expiry time, registrar contacts followed, registrar RDAP server, follow error