# RDAP Domain Intelligence - Bulk Lookups + Expiry Monitor (`gratifying_graph/rdap-domain-intel`) Actor

Bulk domain lookups over RDAP (the modern WHOIS replacement): status, registrar, registration/expiry dates, nameservers, DNSSEC. Optional expiry monitoring flags domains nearing renewal or changed since last run. No personal contact data - registry records only.

- **URL**: https://apify.com/gratifying\_graph/rdap-domain-intel.md
- **Developed by:** [Jimmy A](https://apify.com/gratifying_graph) (community)
- **Categories:** Developer tools, Automation
- **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 lookups

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## RDAP Domain Intelligence - Bulk Domain Lookups + Expiry Monitoring

Bulk domain lookups over **RDAP**, the standardized JSON protocol that is replacing WHOIS, plus built-in **expiry monitoring**. Pass a list of domains and get clean, normalized records: status codes, registrar, registration and expiry dates, nameservers, and DNSSEC - straight from the authoritative registry via the official IANA bootstrap.

No proxies, no scraping, no API key. RDAP is the registries' own structured-data endpoint, so this actor is fast, stable, and accurate across hundreds of TLDs.

### Privacy by design

This actor returns **registry data only**. Registrant, admin, and technical contact records are never read or output - only the registrar organization and the non-personal domain record. That keeps your runs clean of personal data and free of the consent headaches that come with raw WHOIS contact dumps.

### What you get

One record per domain:

```json
{
  "domain": "apify.com",
  "tld": "com",
  "found": true,
  "ldhName": "apify.com",
  "status": ["client transfer prohibited"],
  "registrar": { "name": "Amazon Registrar, Inc.", "handle": "468", "ianaId": "468" },
  "createdDate": "2015-06-02T17:14:10Z",
  "updatedDate": "2024-05-01T09:12:00Z",
  "expirationDate": "2035-06-02T17:14:10Z",
  "daysUntilExpiry": 3278,
  "transferDate": null,
  "nameservers": ["ns-1225.awsdns-25.org", "ns-1928.awsdns-49.co.uk"],
  "dnssec": true,
  "rdapServer": "https://rdap.verisign.com/com/v1/",
  "source": "IANA RDAP (registry data via official bootstrap)",
  "fetchedAt": "2026-06-11T02:14:30.000Z"
}
```

Domains that are unregistered, not found, or on a TLD with no RDAP server come back with `found: false` and an `error` reason, so a batch never fails on a single bad domain.

### Expiry monitoring

Set **expiringWithinDays** and any domain inside that window gets an `expiryAlert`. Turn on **monitor** and each run is compared against the last one: when a domain's expiry date moves (a renewal or transfer), it is flagged. Run on a schedule to watch a whole portfolio and only pay for the alerts that fire.

```json
"expiryAlert": {
  "domain": "example.com",
  "expirationDate": "2026-07-01T00:00:00Z",
  "daysUntilExpiry": 20,
  "previousExpirationDate": "2025-07-01T00:00:00Z",
  "reasons": ["expires in 20 day(s)", "expiration changed 2025-07-01... -> 2026-07-01..."]
}
```

### Inputs

- **domains** (required): list of domain names to look up.
- **expiringWithinDays**: flag domains expiring within N days. Empty = no threshold alerts.
- **monitor**: compare against the previous run and flag renewals/transfers.
- **snapshotGroup**: namespace for monitoring state, so separate portfolios track independently.

### Use cases

- **Portfolio expiry watch**: never lose a domain to a missed renewal - daily run, alert on the window you choose
- **Brand and threat monitoring**: track nameserver, registrar, and DNSSEC changes on domains you care about
- **Sales and enrichment**: append clean registrar/age/status fields to a domain list
- **AI agents**: ask "when does example.com expire and who is the registrar" through the standby API endpoint

### API / Standby mode for AI agents

Call the actor as a synchronous HTTP endpoint:

```
GET /?domain=example.com&expiringWithinDays=30
```

Returns the normalized record immediately. Works as a tool for agent frameworks that support Apify actors.

### Pricing

Pay per event:

| Event | Price |
|---|---|
| Actor start | $0.0001 |
| Per domain lookup | $0.001 |
| Per expiry alert | $0.005 |
| API call (standby) | $0.02 |

Monitoring 500 domains daily is about $15/month plus a few cents per alert - cheaper than losing one domain.

### FAQ

**RDAP vs WHOIS - what's the difference?**
RDAP is the IETF-standard successor to WHOIS: structured JSON instead of free-text, consistent fields across registries, and the official protocol registries are mandated to run. It is more reliable to parse and less likely to break.

**Which TLDs are supported?**
Every TLD listed in the IANA RDAP bootstrap registry (hundreds of gTLDs and many ccTLDs, including multi-label ones like co.uk). The actor refreshes the TLD-to-server map automatically. TLDs without an RDAP server return `found: false`.

**Do you return registrant names or emails?**
No. By design the actor reads only the registrar organization and the non-personal domain record. Contact entities are ignored.

**How fresh is the data?**
It is the registry's live RDAP response at request time - the authoritative source.

**CSV export?**
Every Apify dataset exports as CSV, JSON, Excel, or via API.

# Actor input Schema

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

Domain names to look up (e.g. example.com, mysite.org). One RDAP query per domain.

## `expiringWithinDays` (type: `integer`):

Flag domains that expire within this many days with an expiry alert. Leave empty to disable.

## `monitor` (type: `boolean`):

Compare expiry dates against the previous run and flag renewals/transfers (expiry date moved). Enables expiry alerts even without a day threshold.

## `snapshotGroup` (type: `string`):

Namespace for monitoring state. Use different names to track separate domain portfolios independently.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "apify.com"
  ],
  "monitor": false,
  "snapshotGroup": "default"
}
```

# 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"
    ]
};

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

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

```

## MCP server setup

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

```

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/e5IAYNIO89fs7MWwN/builds/08FHPtr6J1VK2RZVe/openapi.json