# Domain Checker: RDAP, DNS, MX, SPF, DMARC, Age (`opendatadesk/domain-checker`) Actor

Look up a domain's RDAP registration, DNS, mail servers, SPF, DMARC and age in one compact JSON record. Individual registrant details are left out. Built for AI agents, security and n8n.

- **URL**: https://apify.com/opendatadesk/domain-checker.md
- **Developed by:** [Open Data Desk](https://apify.com/opendatadesk) (community)
- **Categories:** Developer tools, Automation, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 domains

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 Checker for Agents: RDAP, DNS, MX, SPF, DMARC and Age

Give the Actor a list of domains and get one compact JSON record for each: RDAP registration, DNS, mail servers, SPF, DMARC and the age of the domain. Individual registrant details are left out. Every domain is written back.

This is meant to be an easy block for AI agents, security reviews and automations in n8n, Make or Zapier.

### What data do you get?

| Field | What it is |
| --- | --- |
| `domain` | The normalised domain |
| `rdap` | Whether the domain was found, registrar, organisation registrant (if it is an organisation), dates, age in days, status and nameservers |
| `dns` | A, AAAA, NS, MX, SOA and TXT records |
| `spf`, `dmarc` | The record and a short policy (`fail`, `softfail`, `reject`, `none`, and so on) |
| `ageDays` | Days since the RDAP registration date, when the registry publishes one |
| `issues`, `status` | A short list of problems, and a status such as `ok`, `not_found`, `invalid_domain` or `skipped_limit` |

#### Example output

One domain from a test run on example.com.

```json
{
    "input": "example.com",
    "domain": "example.com",
    "rdap": {
        "found": true,
        "ldhName": "EXAMPLE.COM",
        "status": [
            "client delete prohibited",
            "client transfer prohibited",
            "client update prohibited"
        ],
        "registrar": "RESERVED-Internet Assigned Numbers Authority",
        "registrant": null,
        "registered": "1995-08-14T04:00:00Z",
        "expires": "2027-08-13T04:00:00Z",
        "updated": "2026-08-14T08:01:43Z",
        "ageDays": 11417,
        "nameservers": [
            "ELLIOTT.NS.CLOUDFLARE.COM",
            "HERA.NS.CLOUDFLARE.COM"
        ],
        "rdapUrl": "https://rdap.verisign.com/com/v1/domain/example.com",
        "error": null
    },
    "dns": {
        "a": [
            "172.66.147.243",
            "104.20.23.154"
        ],
        "aaaa": [
            "2606:4700:10::ac42:93f3",
            "2606:4700:10::6814:179a"
        ],
        "ns": [
            "elliott.ns.cloudflare.com",
            "hera.ns.cloudflare.com"
        ],
        "mx": [
            {
                "host": "",
                "priority": 0
            }
        ],
        "soa": {
            "nsname": "elliott.ns.cloudflare.com",
            "hostmaster": "dns.cloudflare.com",
            "serial": 2420077714,
            "refresh": 10000,
            "retry": 2400,
            "expire": 604800,
            "minttl": 1800
        },
        "txt": [
            "_k2n1y4vw3qtb4skdx9e7dxt97qrmmq9",
            "v=spf1 -all"
        ],
        "errors": {
            "a": null,
            "aaaa": null,
            "ns": null,
            "mx": null,
            "txt": null,
            "soa": null,
            "dmarc": null
        }
    },
    "spf": {
        "found": true,
        "record": "v=spf1 -all",
        "policy": "fail"
    },
    "dmarc": {
        "found": true,
        "record": "v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s",
        "policy": "reject",
        "rua": null
    },
    "ageDays": 11417,
    "issues": [],
    "status": "ok",
    "checkedAt": "2026-11-16T14:55:04.445Z"
}
```

### What is left out on purpose

If the registry describes the registrant as an individual, the name, e-mail and phone are not returned. Only `registrant.type = individual` is kept, so you know a person is listed without getting their details. Organisation names from RDAP are kept.

### Nothing is silently dropped

Invalid domains, domains with no RDAP record and lookup failures stay in the results with a status. If you set `Max domains to check` lower than the size of your list, the remaining domains are still written with status `skipped_limit`.

### How to use it

1. Paste domains or URLs in `Domains`.
2. Set `Max domains to check` and click Start.
3. Download the result as JSON, CSV or Excel, or read it with the API.

### Limits

- RDAP servers are chosen from the official IANA DNS bootstrap (https://data.iana.org/rdap/dns.json). A few TLDs do not publish RDAP. In that case `rdap.error` is `no_rdap_server` and DNS is still checked.
- DNS lookups use the Actor's resolvers. They can differ from what you see on your own network.
- Age comes from the registry's registration event, not from a WHOIS text dump. Some registries hide the date.

### How much does it cost?

You pay for each domain that is written, including failed and skipped ones. The price per 1,000 domains is shown at the top of this page, and you can set a maximum cost per run.

### Data source and legal

RDAP is an open IETF protocol. Registration data is read from the official registry or registrar RDAP server for that TLD. DNS records are public. This Actor is not a substitute for a legal WHOIS policy review if you use the data in a regulated setting. Do not use it to harvest a whole registry.

### Issues and requests

If a TLD looks wrong or a field is missing, please open an issue on the Issues tab with the domain.

# Actor input Schema

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

One domain or URL per line. Every item is written back, including invalid and missing ones.

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

Checks stop after this many domains. Any remaining domains are still written, with status skipped_limit.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "apify.com"
  ],
  "maxItems": 25
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset of domain checks. Each input domain is written back, including failed lookups.

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

A short JSON summary of the run, including counts.

# 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"
    ],
    "maxItems": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("opendatadesk/domain-checker").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",
    ],
    "maxItems": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("opendatadesk/domain-checker").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"
  ],
  "maxItems": 25
}' |
apify call opendatadesk/domain-checker --silent --output-dataset

```

## MCP server setup

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

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/pYHfOevBdAYehlCaY/builds/XyC42UFa3XUaz6bOg/openapi.json
