Bulk RDAP Domain Lookup – Expiry, Registrar, Status, Nameservers & DNSSEC

Look up hundreds of domains in a single run and get one normalized record per domain: registration and expiry dates, days until expiry, registrar, EPP status codes (locks, hold, redemption), nameservers, DNSSEC and availability.

Data comes straight from the official RDAP registries (the successor of WHOIS), discovered through the IANA RDAP bootstrap. No scraping, no third-party API, no login, no personal data: registrant, admin and technical contacts are deliberately never read or returned.

Why use it

• ✅ Structured and consistent: the same fields for .com, .org, .dev, .co.uk and every other TLD with an RDAP server, instead of free-text WHOIS output that differs by registry.
• ✅ Built for lists: paste 10 or 10,000 domains or URLs. Duplicates are removed and invalid entries are skipped and never billed.
• ✅ Alerts included: expiring soon, expired, on hold, in redemption, pending delete, no transfer lock, no DNSSEC.
• ✅ Privacy by design: no personal data. Only the registrar (a company) and technical data are returned.
• ✅ Polite: at most 2 requests per second to any given RDAP server.
• ✅ Pay only for answers: one charge per conclusive lookup. Errors and TLDs without RDAP are free.

Use cases

1. Domain portfolio monitoring: schedule a weekly run on the domains you own and get alerted before one expires or is put on hold.
2. Brand protection and due diligence: check the age, registrar and nameservers of look-alike domains or of a supplier's domains.
3. Availability screening: test a list of candidate names and keep the ones the registry reports as not registered.
4. Security and IT inventories: verify transfer locks and DNSSEC across all your domains, and spot changes in nameservers between runs.
5. Lead and market analysis: measure domain age and registrar market share for a list of companies (no contact data involved).

How to use it

1. Click Try for free and paste your domains (or full URLs) into Domains.
2. Optionally set the expiry warning threshold (30 days by default).
3. Click Start. When the run finishes, export the results as JSON, CSV, Excel or HTML, or fetch them through the Apify API.

Tip: create a Schedule to re-run the lookup weekly and trigger a webhook or an integration when alerts is not empty.

What is returned

Field	Details
outcome	registered, not_registered, unsupported_tld or error
registered	true / false, null if inconclusive
registrar, registrarIanaId	Registrar name and IANA identifier
createdAt, updatedAt, expiresAt	ISO 8601 dates
daysUntilExpiry, domainAgeDays	Computed at run time (negative when expired)
eppStatuses	For example client transfer prohibited, redemption period, client hold
nameservers	Lowercase, sorted
dnssecSigned	Whether the delegation is signed
alerts	Human-readable warnings
rdapServer	The registry server that answered

Input

{
  "items": ["example.com", "https://www.github.com/", "wikipedia.org", "this-domain-is-surely-free-4821.com"],
  "expiryWarningDays": 30,
  "timeoutSecs": 15
}

Field	Description	Default
items	Domains or URLs (only the domain name is used, a leading www. is removed, internationalized names are converted to punycode)	required
expiryWarningDays	Add an alert when a domain expires within this many days	30
timeoutSecs	Network timeout per RDAP request	15

Enter registered domain names (example.com, bbc.co.uk), not subdomains other than www.

Output

One dataset item per domain. A registered domain:

{
  "target": "https://www.example.com/",
  "domain": "example.com",
  "tld": "com",
  "checkedAt": "2026-09-18T16:40:51.974Z",
  "outcome": "registered",
  "registered": true,
  "registrar": "RESERVED-Internet Assigned Numbers Authority",
  "registrarIanaId": "376",
  "createdAt": "1995-08-14T04:00:00.000Z",
  "updatedAt": "2026-08-14T08:01:43.000Z",
  "expiresAt": "2027-08-13T04:00:00.000Z",
  "daysUntilExpiry": 328,
  "domainAgeDays": 11358,
  "eppStatuses": ["client delete prohibited", "client transfer prohibited", "client update prohibited"],
  "nameservers": ["elliott.ns.cloudflare.com", "hera.ns.cloudflare.com"],
  "dnssecSigned": true,
  "alerts": [],
  "rdapServer": "https://rdap.verisign.com/com/v1/",
  "error": null
}

A domain the registry does not know:

{
  "target": "this-domain-is-surely-free-4821.com",
  "domain": "this-domain-is-surely-free-4821.com",
  "tld": "com",
  "checkedAt": "2026-09-18T16:40:51.975Z",
  "outcome": "not_registered",
  "registered": false,
  "registrar": null,
  "expiresAt": null,
  "eppStatuses": [],
  "nameservers": [],
  "alerts": [],
  "rdapServer": "https://rdap.verisign.com/com/v1/",
  "error": null
}

Pricing

Pay per event: $0.003 per domain looked up, which is $3 per 1,000 domains. Lookups with outcome error or unsupported_tld, as well as invalid and duplicate entries, are not charged. You can cap your spending with the maximum charge setting of each run.

Integrations

• API: start runs and download results from any language with the Apify API or clients.
• Schedules and webhooks: monitor expiry dates periodically and trigger a webhook when it finishes.
• Make, Zapier, n8n: send alerts to Slack, email or Google Sheets.
• AI agents: callable as a tool through the Apify MCP server.

FAQ

Is this WHOIS? It is RDAP, the JSON protocol that replaces WHOIS. It is served by the registries themselves, so the data is authoritative and consistently structured.

Why is there no owner name, email or phone? The Actor never reads registrant, admin or technical contacts. Those are personal data and are often redacted by the registries anyway.

What does not_registered mean exactly? The authoritative registry answered "not found". In most cases the name is available, but a registry can also reserve or block names, so confirm with a registrar before buying.

Why is my TLD unsupported_tld? Some registries do not publish an RDAP server in the IANA bootstrap (for example .de and .io at the time of writing). Those lookups are free.

Some fields are null. Registries decide what they publish. A missing field is null instead of being guessed.

How fast is it? Requests to a same RDAP server are spaced by 500 ms, so a list of 1,000 .com domains takes roughly 8 to 10 minutes.

Limitations

• Only TLDs listed in the IANA RDAP bootstrap are supported.
• Subdomains are not resolved to their registered domain: pass the registered name (example.co.uk, not blog.example.co.uk).
• Registries apply their own rate limits; the Actor retries a few times on HTTP 429 or 503, then reports error (not billed).
• Dates and statuses are the registry's own; some registries omit the creation date, expiry date or DNSSEC data.