🌐 Domain WHOIS / RDAP Lookup

Look up registration data for any domain via RDAP (the modern, structured replacement for WHOIS) — registrar, creation / expiry / last-updated dates, status codes, nameservers, DNSSEC and registry link — as clean JSON. Powered by the public RDAP bootstrap (rdap.org), which routes each domain to its authoritative registry. No API key, no browser.

Built for domain monitoring, due diligence, brand protection and lead research. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

🔎 What is the Domain WHOIS / RDAP Lookup?

Pass a list of domains and it returns each domain's registration record as a structured row — including when it was registered, when it expires, who the registrar is, and the nameservers.

What data does it extract?

• Domain and registry handle
• Registrar name
• Created, updated and expires dates
• Status codes (e.g. clientTransferProhibited)
• Nameservers
• DNSSEC signed flag
• Registry RDAP URL

⬇️ Input

Field	Type	Description
domains	array	Domains to look up, e.g. google.com. URLs are accepted too.

Example input

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

⬆️ Output

One record per domain:

{
  "domain": "GOOGLE.COM",
  "query": "google.com",
  "handle": "2138514_DOMAIN_COM-VRSN",
  "status": ["client delete prohibited", "client transfer prohibited"],
  "registrar": "MarkMonitor Inc.",
  "created": "1997-09-15T04:00:00Z",
  "updated": "2019-09-09T15:39:04Z",
  "expires": "2028-09-14T04:00:00Z",
  "nameservers": ["NS1.GOOGLE.COM", "NS2.GOOGLE.COM"],
  "dnssec_signed": false,
  "registry_url": "https://rdap.verisign.com/com/v1/domain/GOOGLE.COM"
}

💡 Use cases

• ⏰ Domain monitoring — track expiry dates and renewals across a portfolio.
• 🔍 Due diligence — check registrar, age and status before deals.
• 🛡️ Brand protection — watch lookalike domains and their registration data.
• 🤖 Automation — feed domain records into Make/Zapier/n8n workflows.

❓ FAQ

Do I need an API key or login? No — it uses the public RDAP bootstrap.

Is this WHOIS? RDAP is the modern, structured successor to WHOIS — same data, clean JSON.

Can I look up many domains at once? Yes — pass a list in domains.

Which TLDs are supported? Most gTLDs and many ccTLDs that publish RDAP.

Does it show contact details? It returns registrar and registration metadata; personal contact data is usually redacted by registries (GDPR).

How does pricing work? Pay per domain returned. No subscription.

Is it legal? It uses public RDAP registry data. Use responsibly and within registry terms.

🔗 You might also like

• Website Contact Extractor — emails & phones from websites.
• Geocoder (OpenStreetMap) — addresses ↔ coordinates.
• Google Maps Email Scraper — local business leads.

---

Keywords: domain whois, rdap lookup, whois api, domain registration data, domain expiry, registrar lookup, nameservers, dnssec, domain monitoring, brand protection, domain age, bulk whois, domain intelligence, tld data

Production workflow

This Actor is designed for security teams, domain portfolio managers, due-diligence analysts and brand-protection workflows. Run a bounded domain list on a schedule, key records by normalized domain, and alert only on meaningful changes such as registrar, expiry, nameserver, DNSSEC or status transitions. Small, repeatable runs are easier to audit than occasional unlimited exports: they expose source changes quickly, reduce duplicate processing and keep automation costs predictable. Use the input defaults as a smoke test, then widen the query only after confirming that the returned fields match the downstream workflow.

Treat each dataset row as source evidence captured at a point in time, not as a permanent fact. Preserve the canonical identifier and source URL, add the run timestamp in the receiving system, and deduplicate before writing to a CRM, spreadsheet, warehouse or alert channel. For recurring monitoring, compare the newest dataset with the previous successful run and send only additions or material changes onward. That pattern avoids repeated notifications and makes the automation more useful over time.

Data quality and interpretation

The primary output includes domain, query, handle, status, registrar, created, updated, expires, nameservers, dnssec_signed, registry_url. Availability depends on what the source publishes for a particular result. Empty values are retained as null or empty fields rather than invented. Search rank is source-specific and can change with language, geography, query wording and time. Validate critical decisions against the linked source page, especially when the data is used for outreach, compliance, pricing, routing or reporting.

Use bounded inputs and respect the source's published interface. The Actor does not bypass logins or collect private account data. Avoid placing passwords, session cookies, personal access tokens or confidential records in Actor input. If a public source changes its response shape, attach a reproducible public input and run ID to an Actor issue so the parser can be updated without exposing private data.

Automation and cost control

The default dataset can be exported as JSON, CSV, Excel, XML or RSS and can be consumed through the Apify API. In Make, Zapier or n8n, start the Actor, wait for the run to finish, then read default-dataset items. In code, store the Actor run ID and dataset ID alongside the imported rows so every record remains traceable. Apply filters after collection only when the source cannot express them directly; source-side filtering usually reduces cost and noise.

This Actor uses pay-per-event billing. A result event is charged only when a structured row is saved to the default dataset. Keep test runs small, estimate expected row volume before scheduling broad searches, and use platform spending limits for unattended workflows. Failed requests and empty searches should not create result events.

Support and feedback

If the Actor saves time in a real workflow, please leave a short Apify Store review describing the use case and the fields that were most useful. Reviews help other users evaluate the product and help prioritize maintenance. For support, open an Actor issue with the run ID, public input, expected behavior and one affected field. Do not include credentials or confidential information.