# Domain WHOIS Lookup (RDAP) – Expiry, Registrar & Nameservers (`webintel/domain-whois-rdap`) Actor

Look up domain registration data using RDAP, the official WHOIS successor. Returns expiry dates, registrar, statuses, DNSSEC, nameservers and privacy-safe registrant organization/location fields.

- **URL**: https://apify.com/webintel/domain-whois-rdap.md
- **Developed by:** [Deepak Ganesh](https://apify.com/webintel) (community)
- **Categories:** Developer tools, Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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 WHOIS Lookup (RDAP) – Expiry, Registrar & Nameservers

![Domain WHOIS Lookup (RDAP) – Expiry, Registrar & Nameservers](https://api.apify.com/v2/key-value-stores/21SBwDwdNtlnapIdO/records/domain-whois-rdap.png?v=0ea86178)

Look up domain registration data with RDAP, the official JSON-over-HTTPS successor to classic WHOIS. This Actor accepts domains, URLs, and email addresses, normalizes them to the registrable domain with the public suffix list, and returns expiry dates, registrar details, statuses, nameservers, DNSSEC, and privacy-safe registrant organization/location fields.

Failed inputs, unsupported TLDs, and network failures are saved with `success=false` and are **not charged**. A `404` RDAP response means the domain appears available; that is a valid lookup result (`registered=false`) and **is charged**.

### Use cases

- **Domain portfolio expiry monitoring**: run on a Schedule and filter `expiresSoon=true`.
- **Lead enrichment**: add registrar, domain age, expiry, and nameserver context to company domains.
- **Brand protection**: check lookalike or campaign domains and detect available names.
- **Domain investors**: screen domain lists for registration status and expiry timing.

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `domains` | string list | required | Domains, URLs, or emails. Examples: `google.com`, `https://www.bbc.co.uk/news`, `admin@wikipedia.org`. |
| `includeRaw` | boolean | `false` | Include raw registry and registrar RDAP JSON responses. |
| `concurrency` | integer | `5` | Domains processed in parallel. Each RDAP host is limited to two concurrent requests. |
| `expiryWarnDays` | integer | `30` | Mark `expiresSoon=true` when expiry is within this many days. |

### Output example

```json
{
  "input": "apify.com",
  "domain": "apify.com",
  "tld": "com",
  "registered": true,
  "success": true,
  "registrar": {
    "name": "Amazon Registrar, Inc.",
    "ianaId": "468",
    "url": "http://registrar.amazon.com",
    "abuseEmail": "trustandsafety@support.aws.com",
    "abusePhone": "tel:+1.2024422253"
  },
  "createdAt": "2009-06-02T17:14:10Z",
  "updatedAt": "2026-05-16T16:53:04Z",
  "expiresAt": "2035-06-02T17:14:10Z",
  "daysToExpiry": 3162,
  "expiresSoon": false,
  "statuses": ["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": { "signed": true },
  "rdapServer": "https://rdap.verisign.com/com/v1/",
  "rdapUrl": "https://rdap.verisign.com/com/v1/domain/apify.com"
}
```

### Pricing

| Event | Price | Charged when |
| --- | ---: | --- |
| Actor start | $0.00005 | The Actor starts. |
| Domain | $0.002 | A supported RDAP lookup returns a valid result, including `registered=false` for available domains. |

Store display: **$2.00 / 1,000 Domains**.

Not charged: invalid inputs, unsupported TLDs, HTTP/network failures, and rate-limit failures.

### FAQ

#### Why RDAP instead of WHOIS port 43?

RDAP is the standards-based successor to WHOIS. It uses HTTPS, structured JSON, redirects/links between registry and registrar data, clear status codes, and better support for internationalization and access control. Port-43 WHOIS is free-form text and differs widely by registry.

#### Is an available domain charged?

Yes. RDAP `404` means the domain is not registered or not found at that registry. The Actor returns `success=true` and `registered=false`, which is a useful successful lookup and is charged.

#### How is privacy handled?

The Actor does not output personal names, personal emails, or phone numbers for registrants. It only includes registrant organization, country, and state when present and not redacted. Registrar and abuse contacts are included because they are operational public contacts.

#### Why do some TLDs fail?

Some ccTLDs do not publish an RDAP server in the IANA bootstrap. These return `success=false` with `RDAP not available for .xx` and are not charged. RDAP providers may also rate-limit; those failures are not charged.

### Changelog

#### 0.1.0

- Initial release with IANA bootstrap lookup, RDAP registry and registrar merging, expiry monitoring, DNSSEC, nameservers, statuses, privacy-safe registrant fields, tests, and pay-per-event charging.

# Changelog

This Actor's version history is a separate document: https://apify.com/webintel/domain-whois-rdap/changelog.md

# Actor input Schema

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

Domains to look up, one per line. Full URLs and email addresses are accepted and normalized to the registrable domain.

## `includeRaw` (type: `boolean`):

Include the raw registry and registrar RDAP responses in each successful dataset item.

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

Maximum number of domains processed in parallel. Requests to the same RDAP host are additionally limited to two at a time.

## `expiryWarnDays` (type: `integer`):

Mark domains as expiresSoon when the expiry date is within this many days.

## Actor input object example

```json
{
  "domains": [
    "google.com",
    "https://www.bbc.co.uk/news",
    "admin@wikipedia.org"
  ],
  "includeRaw": false,
  "concurrency": 5,
  "expiryWarnDays": 30
}
```

# Actor output Schema

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

All lookup results. Each item has domain, tld, registered, success, error, registrar, dates, statuses, nameservers, DNSSEC, privacy-safe registrant fields, RDAP URLs and optional raw JSON.

## `expiry` (type: `string`):

A focused view of expiry dates, days to expiry, expiresSoon and registrar details.

# 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",
        "https://www.bbc.co.uk/news",
        "admin@wikipedia.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("webintel/domain-whois-rdap").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",
        "https://www.bbc.co.uk/news",
        "admin@wikipedia.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("webintel/domain-whois-rdap").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",
    "https://www.bbc.co.uk/news",
    "admin@wikipedia.org"
  ]
}' |
apify call webintel/domain-whois-rdap --silent --output-dataset

```

## MCP server setup

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

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/DnGWX9xXKED98sTII/builds/pAjwCeWe3sKASQjcp/openapi.json