RDAP · domain registration
RDAP Domain Lookup — registrar, dates, nameservers, and DNSSEC for many domains
RDAP Domain Lookup looks up registration data for many domains in one run through RDAP, the ICANN-standard successor to port-43 WHOIS, and returns registrar, dates, status codes, nameservers, and DNSSEC for each domain. Store id taroyamada/rdap-domain-lookup. Registrant, admin, and tech contact entities are ignored.
See the Apify Store page for current pricing.
Open RDAP Domain Lookup on Apify Open Input
Current RDAP records, not DNS propagation or a change monitor
Use this page for a bulk lookup of the current registration record. The Actor reads the official IANA RDAP bootstrap file (data.iana.org/rdap/dns.json) to find the registry server for each TLD, then queries that server. Use RDAP Domain Expiry & Whois Scraper when you need expiry warnings and registration changes between runs. Use DNS Propagation Checker for public DNS across resolvers. Use DMARC & Email Security Checker for SPF, DMARC, and MX. Use SSL/TLS Certificate Scraper for certificate expiry and fingerprints.
| This Actor | RDAP Domain Expiry & Whois Scraper | DNS Propagation Checker | |
|---|---|---|---|
| Job | Current RDAP registration facts for a domain list | Expiry warnings and registration changes between runs | Public DNS records across resolvers |
| Primary input | domains, concurrency, delayMs |
domains plus snapshot and expiry-warning fields |
domains and record types |
| Contacts | Registrant, admin, and tech contacts are ignored | Registration-change monitoring | No RDAP contact records |
| Primary output | Registrar, dates, EPP status, nameservers, DNSSEC, answering RDAP server | Expiry, registrar, nameservers, change history, warnings | Resolved values, TTL, resolver identity |
No personal data is collected. Only registrar-level and domain-level fields are written. This Actor is not affiliated with ICANN, IANA, or any registry.
Use cases
- Expiry monitoring for a domain portfolio, from the dates the registry publishes.
- Checking registrar and name-server setup across client domains.
- Enriching a lead or vendor list with domain age from the registration date.
How to start a run
- Open the Actor and start with the prefilled sample domains to see the output shape.
- Replace the list with your own domains. URLs are accepted.
www.is stripped. The schema uses the hostname’s registrable part as typed. - Export the dataset as JSON, CSV, or Excel, or call the Actor through the API.
Run RDAP Domain Lookup on Apify
Input
| Field | Default | Notes |
|---|---|---|
domains |
["google.com", "wikipedia.org", "apify.com"] |
Domain names to look up. URLs are accepted; www. is stripped |
concurrency |
3 |
Parallel lookups. Minimum 1, maximum 10. Kept low to respect registry RDAP rate limits |
delayMs |
500 |
Pause between batches, in milliseconds. Minimum 0, maximum 10000 |
Input example (schema prefill):
{
"domains": ["google.com", "wikipedia.org", "apify.com"],
"concurrency": 3,
"delayMs": 500
}
Output fields
One dataset row per domain that the registry answers. Registrant, admin, and tech contact entities are not included.
| Field | Meaning |
|---|---|
registrar, registrarIanaId |
Sponsoring registrar name and IANA ID |
createdAt, updatedAt, expiresAt |
Registration, last-changed, and expiration dates, as published by the registry |
domainStatus |
EPP status codes (for example client transfer prohibited) |
nameservers |
Delegated name servers |
dnssecSigned |
Whether the delegation is DNSSEC-signed |
rdapServer |
The registry RDAP server that answered |
Limitations
- Some ccTLDs do not publish an RDAP server in the IANA bootstrap. Those domains are reported as
no_rdap_server. - Field coverage depends on each registry. Thin registries (for example
.com) return registrar-level data only. - Lookups are rate-limited: low default concurrency, a delay between batches, and retry with backoff on HTTP 429, to respect registry limits.
- Domains that fail (invalid, not registered, TLD without RDAP, or a registry error) are not written to the dataset. They are saved to the key-value store record
FAILED_DOMAINSwith the reason. - Data comes from public RDAP services operated by domain registries, located via the IANA bootstrap registry. Use the output in line with each registry’s RDAP terms of use.
See the Apify Store page for current pricing.
Related actors
- RDAP Domain Expiry & Whois Scraper — expiry warnings and changes between runs
- DNS Propagation Checker — public DNS across resolvers, not registration records
- DMARC & Email Security Checker — SPF, DMARC, and MX grades
- SSL/TLS Certificate Scraper — certificate expiry and fingerprints
- Domain Trust Reputation Scraper — TLS, DMARC, and header checks together
Related pages
- Company Domain Tech, DNS & Security Audit — website, DNS, RDAP, and TLS in one audit
- Bulk Email DNS Audit Scraper — SPF, DKIM, DMARC, and BIMI across a portfolio
- Security Headers Checker — HTTP response headers, not RDAP
- Tools
- Home