Domain WHOIS Lookup (RDAP) – Expiry, Registrar & Nameservers

Look up domain registration data with RDAP, the official JSON-over-HTTPS successor to classic WHOIS. This Actor accepts domains, URLs, and email addresses, normalizes them to the registrable domain with the public suffix list, and returns expiry dates, registrar details, statuses, nameservers, DNSSEC, and privacy-safe registrant organization/location fields.

Failed inputs, unsupported TLDs, and network failures are saved with success=false and are not charged. A 404 RDAP response means the domain appears available; that is a valid lookup result (registered=false) and is charged.

Use cases

• Domain portfolio expiry monitoring: run on a Schedule and filter expiresSoon=true.
• Lead enrichment: add registrar, domain age, expiry, and nameserver context to company domains.
• Brand protection: check lookalike or campaign domains and detect available names.
• Domain investors: screen domain lists for registration status and expiry timing.

Input

Field	Type	Default	Description
domains	string list	required	Domains, URLs, or emails. Examples: google.com, https://www.bbc.co.uk/news, admin@wikipedia.org.
includeRaw	boolean	false	Include raw registry and registrar RDAP JSON responses.
concurrency	integer	5	Domains processed in parallel. Each RDAP host is limited to two concurrent requests.
expiryWarnDays	integer	30	Mark expiresSoon=true when expiry is within this many days.

Output example

{
  "input": "apify.com",
  "domain": "apify.com",
  "tld": "com",
  "registered": true,
  "success": true,
  "registrar": {
    "name": "Amazon Registrar, Inc.",
    "ianaId": "468",
    "url": "http://registrar.amazon.com",
    "abuseEmail": "trustandsafety@support.aws.com",
    "abusePhone": "tel:+1.2024422253"
  },
  "createdAt": "2009-06-02T17:14:10Z",
  "updatedAt": "2026-05-16T16:53:04Z",
  "expiresAt": "2035-06-02T17:14:10Z",
  "daysToExpiry": 3162,
  "expiresSoon": false,
  "statuses": ["client transfer prohibited"],
  "nameservers": [
    "ns-1225.awsdns-25.org",
    "ns-1928.awsdns-49.co.uk",
    "ns-449.awsdns-56.com",
    "ns-839.awsdns-40.net"
  ],
  "dnssec": { "signed": true },
  "rdapServer": "https://rdap.verisign.com/com/v1/",
  "rdapUrl": "https://rdap.verisign.com/com/v1/domain/apify.com"
}

Pricing

Event	Price	Charged when
Actor start	$0.00005	The Actor starts.
Domain	$0.002	A supported RDAP lookup returns a valid result, including registered=false for available domains.

Store display: $2.00 / 1,000 Domains.

Not charged: invalid inputs, unsupported TLDs, HTTP/network failures, and rate-limit failures.

FAQ

Why RDAP instead of WHOIS port 43?

RDAP is the standards-based successor to WHOIS. It uses HTTPS, structured JSON, redirects/links between registry and registrar data, clear status codes, and better support for internationalization and access control. Port-43 WHOIS is free-form text and differs widely by registry.

Is an available domain charged?

Yes. RDAP 404 means the domain is not registered or not found at that registry. The Actor returns success=true and registered=false, which is a useful successful lookup and is charged.

How is privacy handled?

The Actor does not output personal names, personal emails, or phone numbers for registrants. It only includes registrant organization, country, and state when present and not redacted. Registrar and abuse contacts are included because they are operational public contacts.

Why do some TLDs fail?

Some ccTLDs do not publish an RDAP server in the IANA bootstrap. These return success=false with RDAP not available for .xx and are not charged. RDAP providers may also rate-limit; those failures are not charged.

Changelog

0.1.0

• Initial release with IANA bootstrap lookup, RDAP registry and registrar merging, expiry monitoring, DNSSEC, nameservers, statuses, privacy-safe registrant fields, tests, and pay-per-event charging.