Domain DNS & WHOIS (RDAP) Lookup: bulk records, registrar, expiry, SPF/DMARC

Look up up to 1000 domains per run and get, for each one: its DNS records (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA - pick any subset), an email-security summary (SPF, DMARC policy, MX presence) and its registration data via RDAP - the official IANA directory and the modern, protocol-based successor of WHOIS (registrar, registration, expiration and last-changed dates, status, nameservers). Ideal for domain inventory, expiry/renewal monitoring, deliverability pre-checks and lead enrichment, on demand or via Apify schedules.

What you get (one dataset item per domain)

domain, status (ok | nxdomain | invalid_input | error), records (each requested type as a list of answers), dnsErrors (per-type failures, e.g. timeouts), emailSecurity (spf record, dmarc record, parsed dmarcPolicy such as reject, hasMx), rdap (registrar, created, expires, updated, status[], nameservers[]) or null with rdapError (e.g. not found), and checkedAt (UTC).

• Domains are normalised for you: lowercased, IDNA-encoded, and if you pass URLs, reduced to the host (scheme, path, port and a leading www. removed).
• Multi-label TLDs such as co.uk are routed to the correct RDAP server automatically via the IANA bootstrap file (fetched once per run).
• A per-domain report (key-value store record REPORT) mirrors the dataset and adds per-domain processing time.

Pricing: pay per domain that answered

One event per domain with a real answer - status ok or nxdomain (a domain that does not exist in DNS is still a definite answer). Entries that fail normalisation (invalid_input) and domains that error out are reported but never charged. There is no start fee. The run checks your spending limit before each domain and stops cleanly when it is reached.

Limits

• Max 1000 domains per run (duplicates are checked once).
• DNS queries: 5 s timeout, 10 s lifetime per query, up to 10 domains in flight at once.
• RDAP: up to 2 concurrent requests per registry server, one retry after 5 s on HTTP 429.
• RDAP is public registration data; some registries answer slowly or not at all, which is reported as rdapError instead of failing the run.
• RDAP covers all generic TLDs (.com, .net, .org, .app, ...) and many country TLDs, but some registries (for example .de and .io at the time of writing) publish no RDAP service. For those, DNS and email-security results are still returned and rdapError says "no RDAP server in IANA bootstrap for this TLD".

Input example

{
  "domains": ["apify.com", "https://www.example.org/path", "münchen.de"],
  "recordTypes": ["A", "AAAA", "MX", "NS", "TXT"],
  "includeRdap": true,
  "includeEmailSecurity": true
}