Bulk WHOIS & Domain Age Lookup (RDAP)

Look up thousands of domains at once and get back registrar, registration date, domain age, expiry date, nameservers and registry status — as clean tabular data, not raw WHOIS text you have to parse yourself.

Paste domains, full URLs, or even email addresses; the domain is extracted for you.

What you get per domain

Field	Meaning
registrar	Who the domain is registered through
created / age_days	Registration date and exact age in days
expires / expires_in_days	Expiry date and days remaining
recently_registered	true when the domain is under 90 days old
expiring_soon	true when under 30 days remain
nameservers	Normalised, sorted list
domain_status / flagged_status	Registry codes, with holds and pending-delete surfaced separately
is_registered	false when the name is unregistered and available

recently_registered is the field most people come for. A domain created three weeks ago is the cheapest reliable signal that a sender, vendor or lead is not what it claims. Combined with flagged_status, it catches most of what a manual WHOIS check is used for.

Built on RDAP, not port-43 WHOIS

This Actor uses RDAP (RFC 9082), the structured JSON protocol that registries now publish over HTTPS. That means parsed, consistent fields across registries instead of free-text WHOIS output that differs for every TLD.

Coverage is ~1,200 TLDs, including .com, .net, .org, .co.uk, .gov, .ai, .xyz and every gTLD.

Some country TLDs — notably .io, .ru, .de — do not publish an RDAP service at all. Those come back with status unsupported_tld and a clear note. They are not guessed at, and not silently dropped from your results: you get a row for every domain you submitted, in the order you submitted it.

Input

Any one of these:

• Paste into the text box — one per line, or comma/semicolon/space separated
• JSON array via domains, when calling from the API
• File URL via fileUrl — a public .txt or single-column .csv link

URLs (https://www.example.com/pricing) and emails (bob@example.com) are both reduced to example.com, and duplicates are removed after that reduction — so example.com, www.example.com and bob@example.com count as one lookup, not three.

Output

{
  "domain": "google.com",
  "status": "registered",
  "is_registered": true,
  "registrar": "MarkMonitor Inc.",
  "created": "1997-09-15",
  "expires": "2028-09-14",
  "age_days": 10546,
  "expires_in_days": 776,
  "recently_registered": false,
  "expiring_soon": false,
  "nameservers": ["ns1.google.com", "ns2.google.com"],
  "domain_status": ["client transfer prohibited"],
  "flagged_status": ["client transfer prohibited"],
  "note": null
}

Statuses: registered, available, unsupported_tld, rate_limited, invalid, error.

Pricing

Free. No per-domain fee and no markup — you pay only the Apify platform compute your own run uses, which is a fraction of a cent for a few thousand domains.

Speed and rate limits

Around 10 domains/second at the default concurrency. Registries throttle aggressive clients, so the default of 10 parallel lookups is deliberately conservative: pushing it higher tends to produce rate_limited rows rather than faster results. Repeated domains within a run are cached and cost nothing.

Common uses

• Lead qualification — filter out prospects whose domain was registered last month
• Fraud and spam screening — newly registered domains are the strongest cheap signal
• Portfolio monitoring — catch your own domains before they expire
• Availability checks — bulk-test whether names are still free
• M&A and competitive research — registration dates and registrar footprints

Related

Cleaning a contact list rather than a domain list? Bulk Email Verifier checks syntax, MX, disposable providers and typos on the same kind of input.