ICANN RDAP Bulk Domain Registration & Expiration Intelligence

Look up only domains you supply through the IANA DNS RDAP bootstrap registry. Bulk means a list of inputs, not internet-wide discovery. This Actor does not identify all domain owners. Registries may redact information or omit fields.

Input

{"domains":["example.com","iana.org","example.net"]}

Supply 1–100 domain names. Unicode names are normalized to IDNA ASCII, case-insensitive duplicates are processed once. URLs, IP addresses, wildcards and invalid labels are rejected. The default three-domain run normally completes within five minutes, subject to registry availability.

Output

One default Dataset row per unique domain, including failures. Download JSON at the default Dataset items URL or add ?format=csv for Clay and n8n. Columns: domain, handle, status_codes, registration_date, expiration_date, last_changed_date, registrar_name, nameservers, dnssec_signed, query_status, error_code, source_url. Missing or redacted values are JSON null. Apify CSV export flattens arrays into indexed columns such as nameservers/0 and status_codes/0.

Dates come exclusively from top-level RDAP domain events with exact eventAction values registration, expiration, and last changed. These are registry RDAP dates, not a live website TLS certificate expiry. handle is the top-level domain handle, not the registrar's handle. registrar_name is extracted only from an entity with the registrar role and its vCard fn. dnssec_signed reflects secureDNS.delegationSigned, indicating a DS delegation at the parent, not a live DNSSEC audit. Nameservers reflect registration data, not live DNS resolution.

A successful result has query_status=success. A missing IANA service, 404, rate limit, server error, timeout or malformed response has query_status=error, a machine-readable error_code, and null unavailable fields. An RDAP domain identity mismatch is not accepted as success.

Requests and limits

The Actor fetches IANA's https://data.iana.org/rdap/dns.json and chooses the label-wise longest matching service URL from HTTPS endpoints. It requests /domain/{domain} one at a time, waits at least one second between requests to the same host, uses a 10-second response timeout, at most three attempts and capped exponential backoff on transient errors or 429. Redirects are not followed. Responses are limited to 2 MB. Registry policies and availability vary; some TLDs have no IANA RDAP endpoint.

Pricing

Pay per event: $0.004 for each successful unique domain (equivalent to $4 per 1,000). The Actor sends the custom successful-domain event when writing a successful row. Failures, retries, and duplicates trigger no custom event. The live monetization configuration contains only this custom event; the synthetic apify-default-dataset-item and apify-actor-start events are absent, so error rows and run starts do not incur event charges. Apify's run spending limit is respected. No separate platform usage charge is intended.

Development

python3 -m unittest discover -s tests -v
docker build -t newapi33-rdap:0.1 .

For a local run with Apify SDK, set ACTOR_TEST_PAY_PER_EVENT=true and provide storage/key_value_stores/default/INPUT.json. Do not put account credentials in this repository.

Sources: IANA RDAP bootstrap registry; RFC 9224 (longest label match); RFC 9083 (domain response and event actions); Apify Pay-per-Event documentation.