Bulk Domain WHOIS/RDAP Lookup: Age, Registrar, Expiry avatar

Bulk Domain WHOIS/RDAP Lookup: Age, Registrar, Expiry

Pricing

$2.00 / 1,000 domains

Go to Apify Store
Bulk Domain WHOIS/RDAP Lookup: Age, Registrar, Expiry

Bulk Domain WHOIS/RDAP Lookup: Age, Registrar, Expiry

Bulk WHOIS replacement using the official RDAP protocol: registrar, creation/expiry dates, domain age, days to expiry, status, nameservers, DNSSEC, registrant org/country (when public) and registrar abuse email. Works for .com, .net, .org, .io and hundreds of TLDs.

Pricing

$2.00 / 1,000 domains

Rating

0.0

(0)

Developer

Rakesh Pai

Rakesh Pai

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Security

Limited permissions

Share

Bulk WHOIS replacement using the official RDAP protocol: registrar, creation/expiry dates, domain age, days to expiry, status, nameservers, DNSSEC, registrant org/country (when public) and registrar abuse email. Works for .com, .net, .org, .io and hundreds of TLDs.

Data source: the official RDAP servers of each domain registry, discovered through IANA's RDAP bootstrap file (data.iana.org/rdap/dns.json), with a follow-up to the registrar RDAP server when available. It needs no login, proxy or browser. Results are returned as clean, flat JSON that is ready for spreadsheets, databases, BI tools and AI agents.

What can you use it for?

  • Score lead or vendor domains by age (fraud and spam checks)
  • Track domain expiry dates for portfolios and brand protection
  • Find registrar and nameserver patterns across competitors
  • Bulk WHOIS replacement now that port-43 WHOIS is being retired
  • Use it as a tool from AI agents through the Apify MCP server, or schedule it and send new results to Slack, Google Sheets or a webhook

Input

FieldNameDescription
domainsDomainsDomains or URLs, e.g. stripe.com
followRegistrarFollow registrar RDAPAlso query the registrar RDAP server for registrant details
concurrencyConcurrencyDomains in parallel

Example input

{
"domains": [
"stripe.com",
"apify.com",
"openai.com",
"bbc.co.uk",
"notion.so"
]
}

Output

Each result is one dataset item with these fields: domain, tld, registered, ldhName, registrar, registrarIanaId, createdAt, updatedAt, expiresAt, domainAgeDays, daysUntilExpiry, status, nameservers, dnssec, registrantOrg, registrantName, registrantCountry, registrarAbuseEmail, rdapServer, checkedAt.

Example output (real result, long fields shortened)

{
"domain": "openai.com",
"tld": "com",
"registered": true,
"ldhName": "openai.com",
"registrar": "Markmonitor Inc.",
"registrarIanaId": "292",
"createdAt": "2007-01-19T19:28:24Z",
"updatedAt": "2024-10-17T22:20:04Z",
"expiresAt": "2029-01-19T19:28:24Z",
"domainAgeDays": 7224,
"daysUntilExpiry": 811,
"status": [
"client delete prohibited",
"client transfer prohibited",
"client update prohibited",
"server delete prohibited",
"server transfer prohibited",
"server update prohibited"
],
"nameservers": [
"ns1-02.azure-dns.com",
"ns2-02.azure-dns.net",
"ns3-02.azure-dns.org",
"ns4-02.azure-dns.info"
],
"dnssec": false,
"registrantOrg": "REDACTED FOR PRIVACY",
"registrantName": null,
"registrantCountry": "US",
"registrarAbuseEmail": null,
"rdapServer": "https://rdap.verisign.com/com/v1/",
"checkedAt": "2026-10-31T16:13:27.772Z"
}

Download the results as JSON, CSV, Excel or XML, or read them through the Apify API.

Pricing

This Actor uses pay-per-event pricing. You pay $0.002 per domain returned, plus standard Apify platform usage, which is small because the Actor uses lightweight HTTP requests (no browser). You are never charged for results that are not returned. To cap spending, set a maximum cost per run in the run options.

Tips

  • Start with a small max-results value to check your filters, then scale up.
  • Schedule the Actor (for example daily) to monitor changes over time.
  • The data comes straight from the source, so its freshness and completeness depend on that publisher.

Disclaimer

This Actor is not affiliated with or endorsed by any website, platform or data publisher named here. Use it in line with the target sites' terms and applicable privacy laws (e.g. GDPR/CAN-SPAM for contact data). Verify critical decisions against the official source.