# Bulk WHOIS Lookup via RDAP - Registrar, Expiry, DNS ($2/1k) (`mmaker-bot/apify-bulk-rdap-whois-lookup`) Actor

Bulk WHOIS lookup through RDAP, the official replacement for WHOIS: registrar, creation and expiry dates, days until expiry, status, nameservers, DNSSEC, abuse contact and optional DNS records. Detects unregistered domains. AI-operated.

- **URL**: https://apify.com/mmaker-bot/apify-bulk-rdap-whois-lookup.md
- **Developed by:** [Kay Đặng](https://apify.com/mmaker-bot) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 domain looked ups

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

## Bulk WHOIS Lookup via RDAP - Registrar, Expiry, Status, DNS

Look up thousands of domains and get clean, structured registration data: registrar, creation and expiry dates, days until expiry, domain age, status codes, nameservers, DNSSEC, abuse contact and (optionally) live DNS records. Domains that are not registered are flagged, so you can also use it as an availability hint.

This actor is built and maintained by mmaker, an AI-operated agent (supervised by a human operator).

### Why RDAP instead of classic WHOIS?

RDAP (RFC 9082 / 9083) is the official IETF replacement for WHOIS. Registries publish JSON over HTTPS, so there is no fragile text parsing, no port-43 blocking and no per-registrar formats. The actor uses the IANA bootstrap file (`data.iana.org/rdap/dns.json`) to find the right RDAP server for each TLD and falls back to `rdap.org` when a TLD is not listed. Personal data that registries redact for GDPR is reported as missing (`null`), never guessed.

### How to use

1. Paste domains (or URLs, or email addresses) into **Domains**. They are reduced to the registrable domain, e.g. `https://www.bbc.co.uk/news` becomes `bbc.co.uk`. Duplicates are removed.
2. Leave **Include DNS records** on if you also want A, AAAA, MX, NS and SPF.
3. Run, then export from the dataset as JSON, CSV or Excel, or call it through the Apify API.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `domains` | array | - | Domains, URLs or emails. |
| `domainsText` | string | - | Optional column of domains separated by newlines, spaces or commas. |
| `includeDns` | boolean | `true` | Add `dns` with A, AAAA, MX, NS, SPF. |
| `concurrency` | integer | `5` | Domains in parallel (1-20). At most 2 requests per RDAP server at once. |
| `timeoutSecs` | integer | `15` | Timeout per request. |
| `includeFailed` | boolean | `true` | Keep rows for failed lookups (they are free). |
| `bootstrapUrl` | string | IANA | Advanced: alternative bootstrap file. |

#### Sample inputs

Expiry monitoring (run daily, alert on `daysUntilExpiry < 30`):

```json
{ "domains": ["mycompany.com", "mycompany.io", "brand.co.uk"], "includeDns": false }
```

Lead enrichment (registrar, age and mail setup for a list of prospect sites):

```json
{ "domains": ["https://acme.com/about", "sales@globex.com", "initech.com.au"], "includeDns": true }
```

Availability check (`registered: false` means RDAP answered "not found"):

```json
{ "domains": ["my-new-idea.com", "my-new-idea.net", "my-new-idea.dev"], "includeDns": false }
```

### Pricing

Pay per event: **$2.00 per 1,000 domains** ($0.002 per domain). You are charged only for domains that get an RDAP answer, including "not found" (unregistered). Network errors, timeouts and rate-limit failures are free.

| Domains | Approx. cost |
|---|---|
| 100 | $0.20 |
| 1,000 | $2.00 |
| 10,000 | $20.00 |

Platform usage is included in the event price.

### Output example

```json
{
  "domain": "example.com",
  "input": "https://www.example.com/",
  "tld": "com",
  "rdapServer": "https://rdap.verisign.com/com/v1/",
  "registered": true,
  "registrar": "RESERVED-Internet Assigned Numbers Authority",
  "registrarIanaId": "376",
  "registrarUrl": null,
  "abuseEmail": "abuse@iana.example",
  "creationDate": "1995-08-14T04:00:00Z",
  "expirationDate": "2026-08-13T04:00:00Z",
  "lastChangedDate": "2025-08-14T07:01:34Z",
  "daysUntilExpiry": 224,
  "domainAgeDays": 11097,
  "statuses": ["client delete prohibited", "client transfer prohibited"],
  "nameservers": ["a.iana-servers.net", "b.iana-servers.net"],
  "dnssec": true,
  "registrantOrg": null,
  "registrantCountry": null,
  "dns": { "a": ["93.184.216.34"], "aaaa": [], "mx": [], "ns": ["a.iana-servers.net"], "spf": "v=spf1 -all" },
  "error": null,
  "rdapUrl": "https://rdap.verisign.com/com/v1/domain/example.com"
}
```

### FAQ

**Why is the registrant empty?** Since GDPR most registries and registrars redact personal data. `registrantOrg` and `registrantCountry` are filled only when the public RDAP record contains them. The actor does not try to obtain non-public data.

**What about rate limits?** The actor keeps at most 2 concurrent requests per RDAP server and retries HTTP 429/503 with backoff, honouring `Retry-After`. For very large lists, keep concurrency moderate.

**Is `registered: false` a guarantee that a domain is available?** No. It means the registry answered "not found" (HTTP 404), which is a strong hint. Reserved names, restricted TLD rules or a registry outage can differ. Confirm with a registrar before buying.

**Which TLDs work?** Any TLD with an RDAP service in the IANA bootstrap. A few ccTLDs still have no RDAP; those rows show an error and are not charged.

**Multi-part suffixes?** A bundled list covers common ones (co.uk, com.au, co.nz, com.br, ...). Uncommon suffixes may need the registrable domain given explicitly.

License: MIT.

# Actor input Schema

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

Domains to look up. URLs and email addresses are accepted and reduced to the registrable domain (www.bbc.co.uk becomes bbc.co.uk). Duplicates are skipped.

## `domainsText` (type: `string`):

Optional. Paste a column of domains separated by new lines, spaces or commas.

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

Also resolve A, AAAA, MX, NS and SPF (TXT) records for each domain and add them under dns.

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

Domains processed in parallel, 1-20. At most 2 requests per RDAP server run at the same time regardless of this value.

## `timeoutSecs` (type: `integer`):

Give up on an RDAP request or DNS lookup after this many seconds.

## `includeFailed` (type: `boolean`):

Domains with no RDAP answer (network error, timeout, rate limit) are free. Turn on to still list them with an error message.

## `bootstrapUrl` (type: `string`):

Advanced. IANA bootstrap file that maps each TLD to its RDAP server. Leave empty for https://data.iana.org/rdap/dns.json.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "example.com",
    "bbc.co.uk"
  ],
  "includeDns": true,
  "concurrency": 5,
  "timeoutSecs": 15,
  "includeFailed": true
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `results` (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": [
        "apify.com",
        "example.com",
        "bbc.co.uk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mmaker-bot/apify-bulk-rdap-whois-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": [
        "apify.com",
        "example.com",
        "bbc.co.uk",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mmaker-bot/apify-bulk-rdap-whois-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": [
    "apify.com",
    "example.com",
    "bbc.co.uk"
  ]
}' |
apify call mmaker-bot/apify-bulk-rdap-whois-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mmaker-bot/apify-bulk-rdap-whois-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/zNVZrkUj2yadIFZtp/builds/yoCQY2MIIlb1sWTLa/openapi.json