# Bulk WHOIS Domain Lookup – RDAP, DNS, Expiry & Availability (`chris_elder/bulk-whois-domain-lookup`) Actor

Bulk WHOIS lookup via official RDAP registries: registrar, creation and expiry dates, days to expiry, status, nameservers, DNSSEC and availability, plus DNS, SPF and DMARC. No API key, no personal data. $1.50 per 1,000 domains; failed lookups are free.

- **URL**: https://apify.com/chris_elder/bulk-whois-domain-lookup.md
- **Developed by:** [Chris Elder](https://apify.com/chris_elder) (community)
- **Categories:** Developer tools, SEO tools, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Domain Lookup – RDAP, DNS, expiry dates & availability

**Bulk WHOIS Domain Lookup** checks hundreds or thousands of domains in one run using **RDAP** – the official, structured successor to WHOIS that every gTLD registry must run. For each domain you get the **registrar**, **creation date**, **expiry date**, **days until expiry**, **domain age**, **EPP status codes**, **nameservers**, **DNSSEC**, and whether the domain is **registered or available** – plus optional live **DNS records (A, AAAA, MX, NS, TXT, CNAME, CAA, SOA)** and **email authentication (SPF, DMARC policy, MX)**.

No API key, no proxies, no scraping of WHOIS websites, and **no personal data**: registrant/admin/tech contacts are deliberately dropped – you only get registry and registrar facts.

### What can this WHOIS lookup tool do?

- 📋 **Bulk WHOIS / RDAP lookup** – paste a list of domains or URLs (`https://www.example.com/page` → `example.com`), duplicates removed
- 📅 **Expiry monitoring** – `expiresAt` and `daysUntilExpiry` for renewal reminders and expiring-domain hunting
- 🟢 **Domain availability check** – `available: true` when the registry has no record of the domain
- 🏢 **Registrar & IANA ID**, creation/update dates, **domain age in days**, EPP **status** (clientTransferProhibited, redemptionPeriod…)
- 🌐 **Nameservers & DNSSEC** from the registry, plus **live DNS** via DNS-over-HTTPS (Cloudflare, Google fallback)
- ✉️ **SPF, DMARC and MX** – audit email authentication for a whole portfolio of domains
- 🌍 Covers **1,200+ TLDs** from the IANA RDAP bootstrap (.com, .net, .org, .uk, .co.uk, .fr, .nl, .au, .ca, .app, .dev, .ai, .xyz…) plus .io, .sh, .ac and .de
- 🛡️ **Polite by default** – requests to each registry are sent one at a time with a delay, retries with back-off, `Retry-After` honoured
- 💸 **Failed lookups are free** – timeouts and TLDs without RDAP (e.g. .eu, .us, .jp) are returned with a clear message and not charged

### Who uses it?

- **Domain investors & brand managers** – track expiry dates and status of a portfolio; spot domains about to drop
- **SEO & marketing agencies** – domain age and registrar checks for link-building and competitor research
- **Security & IT teams** – audit DNSSEC, nameservers, SPF and DMARC across all company domains; detect look-alike domains
- **Sales-ops / data teams** – enrich a list of company websites with domain age, hosting/DNS provider and email set-up (no personal data)
- **AI agents (MCP)** – a cheap, deterministic "who is the registrar and when does this domain expire?" tool

### How much does a bulk WHOIS lookup cost?

**$1.50 per 1,000 domains** ($0.0015 per domain, cheaper on higher Apify plans) + $0.0005 per run. DNS, SPF and DMARC are included at no extra cost. You are **only charged for domains with a definitive registry answer** (registered or not found). Failed lookups and unsupported TLDs are free.

| Job | Price |
|---|---|
| 100 domains | ~$0.15 |
| 1,000 domains | ~$1.50 |
| 10,000 domains | ~$15 |

Set **Max cost per run** in the run options to cap spending. Apify Free plan users get $5 of monthly credit – enough for ~3,000 lookups.

### How to use it

1. Click **Try for free**.
2. Paste your domains (one per line) – URLs and `www.` are cleaned up automatically.
3. Keep **Include DNS records** and **Check email authentication** on (they are free), or switch them off for speed.
4. Click **Start** and export results as JSON, CSV, Excel, XML, or via API, or schedule a weekly run for expiry monitoring.

#### Input example

```json
{
  "domains": ["apify.com", "https://www.bbc.co.uk/news", "wikipedia.org", "my-new-startup-idea-2026.com"],
  "includeDns": true,
  "dnsRecordTypes": ["A", "MX", "NS", "TXT"],
  "checkEmailAuth": true
}
```

#### Output example

```json
{
  "domain": "apify.com",
  "tld": "com",
  "rdapStatus": "found",
  "registered": true,
  "available": false,
  "registrar": "Amazon Registrar, Inc.",
  "registrarIanaId": "468",
  "createdAt": "2009-06-02T17:14:10.000Z",
  "updatedAt": "2026-05-16T16:53:04.000Z",
  "expiresAt": "2035-06-02T17:14:10.000Z",
  "domainAgeDays": 6338,
  "daysUntilExpiry": 3157,
  "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,
  "dns": { "A": ["108.156.184.38"], "MX": [{ "priority": 1, "exchange": "aspmx.l.google.com" }], "NS": ["…"], "TXT": ["v=spf1 a mx include:_spf.google.com … -all"] },
  "resolves": true,
  "hasMx": true,
  "spf": "v=spf1 a mx include:_spf.google.com include:mailgun.org include:amazonses.com … -all",
  "dmarc": "v=DMARC1; p=reject; …",
  "dmarcPolicy": "reject",
  "charged": true,
  "checkedAt": "2026-10-09T06:40:00.000Z"
}
```

A domain the registry does not know returns `"rdapStatus": "not-found", "available": true`. A `RUN_SUMMARY` record in the key-value store lists counts and any invalid inputs.

### Input options

| Field | Default | Description |
|---|---|---|
| `domains` | – | Domains or URLs, one per line |
| `includeDns` | `true` | Live DNS records via DNS-over-HTTPS |
| `dnsRecordTypes` | A, AAAA, MX, NS, TXT | Also CNAME, CAA, SOA |
| `checkEmailAuth` | `true` | SPF, DMARC (+ policy), MX |
| `followRegistrarRdap` | `false` | Also query the registrar's RDAP server (thin registries) |
| `maxConcurrency` | 4 | Domains processed in parallel (same-registry requests are still serialised) |
| `requestDelayMs` | 250 | Delay between requests to the same registry |

### FAQ

**Is RDAP the same as WHOIS?** RDAP is the IETF-standard replacement for port-43 WHOIS (RFC 9082/9083). ICANN requires all gTLD registries and registrars to run it. It returns the same registration facts as WHOIS, but as structured JSON, so results are reliable and consistent across TLDs.

**Why is there no owner name or e-mail?** Since GDPR most registries redact contact data anyway, and this tool is designed not to collect personal data. You get registry facts only.

**"Available" – can I trust it?** `available: true` means the registry has no record of the domain. Premium, reserved or blocked names may still be unavailable to register – confirm at your registrar.

**Which TLDs are not supported?** TLDs whose registry has no public RDAP server (for example .eu, .us, .jp and some ccTLDs). They are returned with `rdapStatus: "unsupported-tld"`, DNS data where available, and are **not charged**.

**Is it legal?** RDAP is a public service operated by registries for exactly this purpose. The Actor sends polite, rate-limited queries and stores no personal data. Respect each registry's terms of use (no high-volume abuse, no spam).

**Can I integrate it?** Yes – via the Apify API, client libraries for JavaScript/Python, webhooks, Zapier, Make, n8n, Google Sheets, or as an MCP tool for AI agents.

Found a bug or need a TLD added? Open an issue on the **Issues** tab – we usually respond within a day.

### Need the data done for you?

If you'd rather not set up runs yourself, the UK company behind these tools (GPT Shop Ltd) offers a fixed-price done-for-you scrape. Tell us the website and the fields you need, and you get a clean CSV or Google Sheet within 48 hours of the confirmed brief, up to 5,000 rows, for £149 or $179. If we can't get the data, you're refunded in full. [See the done-for-you scraper service](https://sme-free-tools.pages.dev/done-for-you-scraper/?utm_source=apify\&utm_medium=readme\&utm_campaign=bulk-whois-domain-lookup)

# Actor input Schema

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

Domain names to look up, one per line. URLs and www. prefixes are cleaned automatically (https://www.example.com/page → example.com). Duplicates are removed.

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

Add live DNS records (via DNS-over-HTTPS) and a 'resolves' flag. Free – included in the per-domain price.

## `dnsRecordTypes` (type: `array`):

Which record types to return when DNS is included. Allowed: A, AAAA, MX, NS, TXT, CNAME, CAA, SOA.

## `checkEmailAuth` (type: `boolean`):

Add the SPF record, DMARC record and policy (none/quarantine/reject) and whether the domain has MX records.

## `followRegistrarRdap` (type: `boolean`):

For thin registries (.com/.net) also ask the registrar's own RDAP server for its expiry date. One extra polite request per domain; usually not needed.

## `maxConcurrency` (type: `integer`):

How many domains are processed in parallel. Requests to the same registry are always sent one at a time with the delay below.

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

Politeness delay per RDAP server. Keeps you well below registry rate limits.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "wikipedia.org",
    "bbc.co.uk"
  ],
  "includeDns": true,
  "dnsRecordTypes": [
    "A",
    "AAAA",
    "MX",
    "NS",
    "TXT"
  ],
  "checkEmailAuth": true,
  "followRegistrarRdap": false,
  "maxConcurrency": 4,
  "requestDelayMs": 250
}
```

# Actor output Schema

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("chris_elder/bulk-whois-domain-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",
        "wikipedia.org",
        "bbc.co.uk",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("chris_elder/bulk-whois-domain-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",
    "wikipedia.org",
    "bbc.co.uk"
  ]
}' |
apify call chris_elder/bulk-whois-domain-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chris_elder/bulk-whois-domain-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/19swuiaoQ3Po50eCm/builds/9OtrENXbkvHezdeVK/openapi.json