# Domain WHOIS & RDAP Lookup (Bulk, Expiry, DNS, SSL) (`seonlabs/domain-whois-rdap-lookup`) Actor

Bulk domain lookup via official RDAP (modern WHOIS): registrar, creation & expiry dates, days to expiry, status, nameservers, availability. Optional DNS records and SSL certificate expiry.

- **URL**: https://apify.com/seonlabs/domain-whois-rdap-lookup.md
- **Developed by:** [선도 황](https://apify.com/seonlabs) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Domain WHOIS & RDAP Lookup (Bulk, Expiry, DNS, SSL)

Look up thousands of domains at once using **RDAP** — the official, structured successor of WHOIS run by the domain registries themselves. Get the **registrar, creation date, expiry date, days until expiry, status codes, nameservers, DNSSEC and availability** for every domain, as clean JSON or CSV.

Optionally add **DNS records** (A, AAAA, MX, NS, TXT) and the **SSL certificate** issuer and expiry.

No API key, no WHOIS text parsing, no rate-limit headaches — just paste your list.

### What people use it for

- **Domain portfolio monitoring** — see which of your domains (or clients' domains) expire in the next 30/60/90 days. Schedule it weekly.
- **Availability checks** — `registered: false` means the domain is not registered.
- **SSL expiry alerts** — catch certificates about to expire before your visitors do.
- **Lead research & sales intelligence** — domain age, registrar and mail provider (MX) for a list of company websites.
- **Security & brand protection** — check look-alike domains, their registrar, nameservers and abuse contact.

### Input

| Field | What it does | Default |
|---|---|---|
| **Domains** | One per line or pasted as a list. URLs, `www.` and capitals are cleaned up. Subdomains are looked up via their registered parent. | — |
| **Include DNS records** | A, AAAA, MX, NS, TXT via DNS-over-HTTPS. | off |
| **Include SSL certificate** | Issuer, valid from/to, days to expiry, valid or not. | off |
| **Ask the registrar too** | For .com/.net, also asks the registrar's RDAP server for the registrant organization/country (when public). | off |
| **Parallel lookups** | 1–20. | 5 |
| **Delay per lookup (ms)** | Politeness pause; the Actor also backs off automatically when a registry says "slow down". | 200 |

#### Example input

```json
{
  "domains": ["apify.com", "https://www.github.io/", "wikipedia.org", "my-new-startup-idea.com"],
  "includeDns": true,
  "includeSsl": true
}
```

### Output (one item per domain)

```json
{
  "domain": "apify.com",
  "tld": "com",
  "queriedAs": "apify.com",
  "rdapUrl": "https://rdap.verisign.com/com/v1/domain/apify.com",
  "registered": true,
  "registrar": "Amazon Registrar, Inc.",
  "registrarIanaId": "468",
  "createdAt": "2009-06-02T17:14:10Z",
  "updatedAt": "2026-05-16T16:53:04Z",
  "expiresAt": "2035-06-02T17:14:10Z",
  "daysToExpiry": 3167,
  "status": ["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": true,
  "registrantOrg": null,
  "registrantCountry": null,
  "abuseEmail": "trustandsafety@support.aws.com",
  "abusePhone": "+1.2024422253",
  "registrarRdapUrl": "https://rdap.registrar.amazon.com/rdap/domain/APIFY.COM",
  "dns": {
    "A": ["..."],
    "AAAA": [],
    "MX": ["1 aspmx.l.google.com", "5 alt1.aspmx.l.google.com", "5 alt2.aspmx.l.google.com", "10 aspmx2.googlemail.com", "10 aspmx3.googlemail.com"],
    "NS": ["..."],
    "TXT": ["..."]
  },
  "ssl": {
    "issuer": "...",
    "validFrom": "...",
    "validTo": "...",
    "daysToExpiry": 0,
    "valid": true,
    "error": null
  },
  "error": null,
  "scrapedAt": "2026-09-30T10:00:00+00:00"
}
```

- A domain that is **not registered** comes back as one item with `"registered": false`.
- If a registry could not be reached, the item has `"registered": null` and an `error` explaining why — you are still told about it.
- `registrantOrg` / `registrantCountry` are only filled when the registry or registrar publishes them (many hide them for privacy).
- A summary (registered / available / errors per TLD) is saved as `SUMMARY` in the run's key-value store.

### Pricing

- **$0.005** per run start
- **$0.0015** per domain (**$1.50 per 1,000**)

DNS, SSL and registrar options are included at no extra charge. Platform usage is included.

### Coverage & limitations

- Works for every TLD whose registry offers RDAP: all generic TLDs (.com, .net, .org, .io, .app, .dev, .shop, …) and a growing list of country TLDs. The list comes live from IANA on every run.
- Some country-code registries do not offer public RDAP yet; those domains return an `error` instead of data.
- Data comes from the registries' public RDAP services and their terms of use apply. Personal registrant data is not collected — only what registries publish, which is normally the organization and country at most.

### Support

Found a bug or need a field? Open an issue on the **Issues** tab — I answer quickly.

# Actor input Schema

## `domains` (type: `array`):

One per line, or paste a comma/space-separated list. URLs, `www.` and capitals are cleaned up automatically (`https://www.Example.com/page` → `example.com`). Subdomains are looked up via their registered parent.

## `includeDns` (type: `boolean`):

Adds A, AAAA, MX, NS and TXT records (via DNS-over-HTTPS). 5 extra lookups per domain.

## `includeSsl` (type: `boolean`):

Connects to port 443 and reports the certificate issuer, expiry date, days to expiry and whether it is valid.

## `includeRegistrarData` (type: `boolean`):

For .com/.net and other 'thin' registries, also query the registrar's RDAP server to fill in registrant organization/country when public. One extra request per domain.

## `concurrency` (type: `integer`):

How many domains to look up at the same time.

## `requestDelayMs` (type: `integer`):

Pause after each domain, per parallel slot. Registries rate-limit heavy use; the Actor also backs off automatically on HTTP 429.

## `proxyConfiguration` (type: `object`):

Usually leave off. If a registry refuses direct access, the Actor switches to Apify Proxy automatically.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "apify.com",
    "wikipedia.org"
  ],
  "includeDns": false,
  "includeSsl": false,
  "includeRegistrarData": false,
  "concurrency": 5,
  "requestDelayMs": 200,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `domains` (type: `string`):

One result per domain as JSON (default dataset).

## `domainsCsv` (type: `string`):

Same results as CSV.

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "example.com",
        "apify.com",
        "wikipedia.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seonlabs/domain-whois-rdap-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": [
        "example.com",
        "apify.com",
        "wikipedia.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("seonlabs/domain-whois-rdap-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "example.com",
    "apify.com",
    "wikipedia.org"
  ]
}' |
apify call seonlabs/domain-whois-rdap-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seonlabs/domain-whois-rdap-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/RjEtkjDgnbxEUPmR3/builds/AT4lPCDnXR0PPM2RV/openapi.json