# Bulk Domain RDAP & DNS Lookup – Registrar, Expiry, Age (`chain_link/bulk-domain-rdap-dns-lookup`) Actor

Look up domains in bulk via official RDAP registries and DNS-over-HTTPS. Returns registrar, creation and expiry dates, domain age, status codes, nameservers, DNSSEC, DNS records, and SPF/DMARC presence. Registrant contact details are never collected.

- **URL**: https://apify.com/chain_link/bulk-domain-rdap-dns-lookup.md
- **Developed by:** [James White](https://apify.com/chain_link) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$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 Domain RDAP & DNS Lookup – Registrar, Expiry, Age, MX/SPF/DMARC

Paste in a list of domains (or full website addresses) and get one clean row per domain with its registration details, DNS records and basic email-security checks.

The tool asks the **official domain registries** directly using RDAP, the modern, structured replacement for WHOIS. The right registry server for each domain ending (.com, .org, .uk and so on) is picked from the official IANA directory. DNS records come from a public DNS-over-HTTPS resolver.

**Registrant names, addresses, phone numbers and email addresses are never collected.**

### What you get for each domain

- Whether the domain is registered (or likely available)
- Registrar name and registrar IANA ID
- Creation, last-updated and expiry dates
- Domain age in days and days left until expiry, already calculated for you
- Registry status codes, such as "client transfer prohibited"
- Nameservers and whether DNSSEC is enabled
- DNS records of the types you choose: A, AAAA, MX, NS, TXT, CNAME, SOA, CAA
- Whether the domain has an SPF record and a DMARC record
- The registry server that answered, and an error note if something went wrong

### Typical uses

- Track when your own domains, or your clients' domains, are due to expire
- Check how old a domain is when assessing leads, vendors or suspicious websites
- Audit email security (MX, SPF, DMARC) across many domains at once
- Find out which registrar and DNS provider a list of companies uses
- Check whether names on a shortlist are still unregistered

### Price

**$0.002 per domain looked up.** For example, 1,000 domains cost $2.00. You pay only for the rows you receive, and the run never returns more rows than your **Max results** setting.

### Input

| Field | What it does |
|---|---|
| **Domains** (required) | A list of domains or URLs, for example example.com or https://www.example.org/page. Each URL is reduced to its registrable domain, so www.bbc.co.uk/news becomes bbc.co.uk. Duplicates are removed. |
| **Include DNS records** | Turn DNS record lookups on or off. Default: on. |
| **DNS record types** | The record types to fetch: A, AAAA, MX, NS, TXT, CNAME, SOA, CAA. Default: A, AAAA, MX, NS, TXT. |
| **Check SPF / DMARC** | Checks for an SPF record and looks up the \_dmarc record. Default: on. |
| **Max results** | The maximum number of domains to process. The input form pre-fills 1,000. If the field is left out entirely, the limit is 50. |

#### Example input

```json
{
  "domains": ["google.com", "example.org", "https://www.bbc.co.uk/news"],
  "includeDns": true,
  "recordTypes": ["A", "MX", "NS", "TXT"],
  "includeEmailSecurity": true,
  "maxItems": 100
}
```

### Output

| Field | Meaning |
|---|---|
| domain | Normalised domain name |
| registered | true if the registry has a record. false if it was not found, which usually means the domain is available. |
| registrar | Sponsoring registrar name |
| registrarIanaId | Registrar IANA ID, if provided |
| createdDate | Registration date (ISO 8601, UTC) |
| updatedDate | Date the registry record last changed |
| expiresDate | Expiry date |
| domainAgeDays | Days since registration |
| daysUntilExpiry | Days until expiry |
| statuses | Registry status codes |
| nameservers | Nameservers listed at the registry |
| dnssec | true if the domain's delegation is DNSSEC-signed |
| dnsRecords | Record type mapped to a list of values |
| hasSpf | true if a TXT record starts with v=spf1 |
| hasDmarc | true if a \_dmarc record starting with v=DMARC1 exists |
| rdapServer | The registry RDAP address that answered |
| error | Empty if all went well, otherwise a short explanation |
| checkedAt | Time of the lookup (ISO 8601, UTC) |

#### How some values are formatted (please read)

- **IPv4 addresses use underscores instead of dots.** For example, 93.184.215.14 appears as 93_184_215_14. This applies to A records and to IP addresses inside TXT records such as SPF. Without it, automated personal-data filters can mistake an IP address for a phone number. To get the usual form, replace each \_ with a dot.
- In TXT and CAA records, email addresses are replaced with \[email redacted], and any run of 7 or more digits is replaced with \[masked]. The hasSpf and hasDmarc checks use the original, unmasked records, so they are not affected.
- For SOA, only the primary nameserver is returned.

#### Example output row

```json
{
  "domain": "example.org",
  "registered": true,
  "registrar": "ICANN",
  "registrarIanaId": "376",
  "createdDate": "1995-08-31T04:00:00Z",
  "updatedDate": "2026-08-30T04:00:10Z",
  "expiresDate": "2027-08-30T04:00:00Z",
  "domainAgeDays": 11355,
  "daysUntilExpiry": 331,
  "statuses": ["server delete prohibited", "server transfer prohibited", "server update prohibited", "auto renew period"],
  "nameservers": ["katelyn.ns.cloudflare.com", "mitch.ns.cloudflare.com"],
  "dnssec": true,
  "dnsRecords": {
    "A": ["104_20_26_136", "172_66_157_237"],
    "MX": ["0 ."],
    "NS": ["katelyn.ns.cloudflare.com", "mitch.ns.cloudflare.com"],
    "TXT": ["v=spf1 -all"]
  },
  "hasSpf": true,
  "hasDmarc": true,
  "rdapServer": "https://rdap.publicinterestregistry.org/rdap/",
  "error": "",
  "checkedAt": "2026-10-02T07:20:44Z"
}
```

### Limits and good to know

- **Some domain endings have no RDAP service.** A few country-code endings do not publish one. For these domains, the row says so in the error field, and registration status is inferred from DNS where possible.
- **Registries limit request rates.** The tool sends one request at a time to each registry, with a short pause between requests, and retries temporary errors with increasing waits. If a registry or the DNS resolver refuses access outright (for example HTTP 403 or 429 after retries), the run stops and logs the reason clearly. Results collected up to that point are kept.
- **"Not registered" is not a guarantee.** A false value in registered means the registry had no record at the moment of the lookup. It does not guarantee that you can buy the domain, because names can be reserved or premium.
- **Results are a snapshot.** Dates, records and statuses can change after the lookup.
- **One bad domain never ends the run.** Problems are noted in that row's error field and the run continues.

### Terms and privacy

This tool uses public, documented protocols: RDAP from the official domain registries and DNS-over-HTTPS. Contact details of registrants, administrators and abuse desks are deliberately ignored and never stored. Registries publish their own terms of use, which generally allow lookups for lawful purposes and prohibit using the data for spam or unsolicited marketing. You are responsible for using the results in line with those terms and with applicable law.

# Actor input Schema

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

List of domains or URLs to look up (e.g. example.com, https://www.example.org/page). URLs are normalised to the registrable domain and duplicates are removed.

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

Resolve DNS records via DNS-over-HTTPS.

## `recordTypes` (type: `array`):

Record types to resolve when DNS is enabled (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA).

## `includeEmailSecurity` (type: `boolean`):

Check for SPF in the TXT records and look up the \_dmarc TXT record.

## `maxItems` (type: `integer`):

Maximum number of domains to process.

## Actor input object example

```json
{
  "domains": [
    "google.com",
    "example.org"
  ],
  "includeDns": true,
  "recordTypes": [
    "A",
    "AAAA",
    "MX",
    "NS",
    "TXT"
  ],
  "includeEmailSecurity": true,
  "maxItems": 1000
}
```

# Actor output Schema

## `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": [
        "google.com",
        "example.org"
    ],
    "includeDns": true,
    "recordTypes": [
        "A",
        "AAAA",
        "MX",
        "NS",
        "TXT"
    ],
    "includeEmailSecurity": true,
    "maxItems": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("chain_link/bulk-domain-rdap-dns-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": [
        "google.com",
        "example.org",
    ],
    "includeDns": True,
    "recordTypes": [
        "A",
        "AAAA",
        "MX",
        "NS",
        "TXT",
    ],
    "includeEmailSecurity": True,
    "maxItems": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("chain_link/bulk-domain-rdap-dns-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": [
    "google.com",
    "example.org"
  ],
  "includeDns": true,
  "recordTypes": [
    "A",
    "AAAA",
    "MX",
    "NS",
    "TXT"
  ],
  "includeEmailSecurity": true,
  "maxItems": 1000
}' |
apify call chain_link/bulk-domain-rdap-dns-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chain_link/bulk-domain-rdap-dns-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/1Ygb8sjkQGv6PtoOc/builds/U3rlbgdabz0x7lGbM/openapi.json