Domain WHOIS & RDAP Lookup

What this Actor scrapes

RDAP (Registration Data Access Protocol, RFC 7482+) is the structured, machine-readable successor to legacy WHOIS text — and every gTLD registry (plus a growing set of ccTLDs) is required to expose it publicly, with no key or login. The catch: there's no single RDAP endpoint. Every TLD points at a different registry server, and you have to resolve that mapping yourself via IANA's bootstrap file before you can ask a single question. This Actor does that resolution for you, walks your domain list at a pace you control, and writes one structured row per domain — registrar, registration and expiration dates, name servers, DNSSEC status, and domain status codes — ready for a portfolio monitor, a lead list, or a brand-protection sweep.

What we handle for you

• 🌐 Correct-registry routing — resolves the right RDAP server per TLD via the IANA bootstrap file, so one input list can span domains across dozens of registries.
• 🔁 Polite pacing + retries — configurable delay between requests, exponential backoff on 429/503, Retry-After honoured.
• 🌐 Optional proxy rotation via Apify Proxy for higher-volume runs against registries that throttle by source IP.
• 🧊 Clean, typed dataset rows — Pydantic-validated registrar, dates, name servers, and status codes, ready for CSV/JSON export.
• 💰 Pay-Per-Event pricing — you only pay for domains that resolve. No data, no charge beyond the warm-up fee.

Use cases

• Domain portfolio monitoring — schedule daily runs across your portfolio and catch expiration dates before they lapse.
• Prospecting / lead gen — bulk-check registrar and creation date to spot newly registered domains in a niche.
• Brand protection — batch-check lookalike domain registrations for enforcement leads.
• Due diligence — verify domain ownership, age, and registration history for a target company's web assets.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "domains": [
    "stripe.com",
    "example.com"
  ],
  "maxDomains": 5,
  "requestDelaySeconds": 1.0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

domainstatusregistrarcreated_dateexpiration_datelast_changed_datenameserversepp_status_codesdnssec_enabledregistrant_countryrdap_serverscraped_at

{
  "domain": "stripe.com",
  "status": "registered",
  "registrar": "SafeNames Ltd.",
  "created_date": "1995-09-12T04:00:00Z",
  "expiration_date": "2027-09-11T04:00:00Z",
  "last_changed_date": "2025-10-01T01:39:51Z",
  "nameservers": [
    "NS-1087.AWSDNS-07.ORG",
    "NS-1882.AWSDNS-43.CO.UK",
    "NS-423.AWSDNS-52.COM",
    "NS-705.AWSDNS-24.NET"
  ],
  "epp_status_codes": [
    "client delete prohibited",
    "client transfer prohibited",
    "client update prohibited",
    "server delete prohibited",
    "server transfer prohibited",
    "server update prohibited"
  ],
  "dnssec_enabled": false,
  "registrant_country": null,
  "registrant_org": null,
  "rdap_server": "rdap.verisign.com",
  "scraped_at": "2026-09-01T09:31:19+00:00"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• RDAP coverage depends on the registry — most gTLDs (.com, .net, .org, etc.) support it; some ccTLDs still only offer legacy WHOIS, which this Actor does not fall back to.
• Registrant contact fields (name, email, phone) are frequently redacted by the registrar under GDPR/privacy-proxy policy — this is a registry-side restriction, not a limitation of the lookup.
• We query only the public RDAP surface each registry exposes — no bulk-zone-file access, no historical/expired WHOIS records.