# SiteVerdict — Domain & IP RDAP Lookup + Expiry Alerts (`siteverdict/siteverdict-domain-rdap-lookup`) Actor

Bulk domain and IP registration data from official RDAP (the WHOIS replacement): registrar, dates, status, nameservers, DNSSEC. Expiry and change alerts to Slack or webhook, plus lookalike-domain watch for your brand. Privacy-safe: no registrant personal data.

- **URL**: https://apify.com/siteverdict/siteverdict-domain-rdap-lookup.md
- **Developed by:** [Aman Thakran](https://apify.com/siteverdict) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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 & IP RDAP Lookup + Expiry Alerts — the official WHOIS replacement, in bulk

**Never lose a domain to a missed renewal, and spot lookalike domains before phishers use them.** SiteVerdict queries the **official RDAP services** (the IETF/ICANN successor to WHOIS) for thousands of domains and IP addresses and returns clean, structured registration data — registrar, creation and expiry dates, EPP status, nameservers and DNSSEC — with expiry alerts, change monitoring and a lookalike-domain watch.

- 📅 **Expiry alerts**: "expires in 9 days", "EXPIRED", "on hold", "pending delete" — straight to Slack or any webhook
- 🔁 **Change monitoring**: registrar, expiry, status, nameserver and DNSSEC changes since the last run (hijack and lapse early warning)
- 🎣 **Lookalike watch**: typo, TLD-swap, homoglyph and combo variants of your own domains, each checked in RDAP — no grey-market "newly registered domain" feeds
- 🌍 **IP lookups**: network name, CIDR, holder organisation, country and abuse contact from the regional internet registries (RIPE, ARIN, APNIC, LACNIC, AFRINIC)
- 🔒 **Privacy-safe by design**: we never output registrant names, emails, phones or addresses, and we report which fields the registry redacted

### Who it is for

1. **Domain portfolio owners and agencies** managing dozens to thousands of client domains — one scheduled run a week replaces calendar reminders.
2. **Security and brand-protection teams** — detect registered lookalikes and registrar/nameserver changes on your own domains.
3. **Sales and data teams** — enrich lead lists with domain age, registrar and DNSSEC (company data only).

### Example output

```json
{
  "domain": "example.com",
  "lookupStatus": "ok",
  "registered": true,
  "registrar": { "name": "RESERVED-Internet Assigned Numbers Authority", "ianaId": "376", "abuseEmail": null },
  "createdAt": "1995-08-14T04:00:00Z",
  "expiresAt": "2027-08-13T04:00:00Z",
  "daysToExpiry": 306,
  "ageDays": 11381,
  "status": ["client delete prohibited", "client transfer prohibited", "client update prohibited"],
  "flags": { "transferLocked": true, "clientHold": false, "pendingDelete": false },
  "nameservers": ["elliott.ns.cloudflare.com", "hera.ns.cloudflare.com"],
  "dnssec": true,
  "redactedFields": [],
  "alerts": [],
  "termsOfServiceUrl": "https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml",
  "sourceUrl": "https://rdap.verisign.com/com/v1/domain/example.com"
}
```

**Before:** a spreadsheet of renewal dates nobody updates. **After:** a Slack message the moment a domain is 30 days from expiry, goes on hold, or changes registrar.

### How to use

1. Paste domains (URLs are fine) and/or IP addresses.
2. Optional: add your own domains under **Lookalike watch**, set **Alert when a domain expires within** and a Slack/webhook URL.
3. Turn on **Monitor mode** and schedule the Actor (daily or weekly). Download `DOMAINS_CSV` from the key-value store for spreadsheets.

No input? It runs on fictional sample data, free.

### Pricing

| Event | Price (proposed) |
|---|---|
| Domain looked up (`domain-lookup`, includes each lookalike candidate) | $0.002 |
| IP looked up (`ip-lookup`) | $0.002 |

Examples: **100 domains ≈ $0.20**; weekly monitoring of 500 domains ≈ **$4 a month**; lookalike watch of one brand with 50 variants ≈ $0.10 per run. Not charged: invalid input, TLDs without an RDAP service, network errors, sample mode.

### Benchmark (honest summary)

Compared with WHOIS/RDAP Actors on the Apify Store by documented features (we did not run competitors):

| | SiteVerdict | Typical WHOIS/RDAP Actors |
|---|---|---|
| Official RDAP via IANA bootstrap | ✅ | Mixed (some scrape WHOIS port 43 or third-party APIs) |
| Expiry + status alerts to Slack/webhook | ✅ | Rare |
| Change monitoring between runs | ✅ | Rare |
| Lookalike/typosquat watch | ✅ | ❌ |
| IP/RIR lookups | ✅ | Usually domains only |
| Personal data | Never output; redactions reported | Often raw registrant blocks |
| Price per lookup | $0.002 | $0.001–$0.009 |

Live check on 11 Oct 2026: example.com, iana.org, bbc.co.uk and wikipedia.org returned registrar, dates and status from Verisign, PIR and Nominet RDAP; `.io` has no RDAP service in the IANA bootstrap and is reported as `no-rdap-service` (not charged).

### FAQ

**Why RDAP and not WHOIS?** ICANN gTLD registries and registrars must run RDAP; it returns structured JSON, standard status codes and explicit redaction markers. Port-43 WHOIS is being retired for gTLDs.

**Some TLDs return `no-rdap-service`.** A few ccTLD registries (e.g. .io, .de at the time of writing) do not publish an RDAP service in the IANA bootstrap registry. We do not scrape their web WHOIS.

**Can I get the owner's email?** No. Since GDPR most registries redact it, and we never output personal data. Use the registrar's abuse contact or the registrar's own relay/contact form.

**Is there a newly-registered-domains feed?** We deliberately do not use one: the feeds we could find either need ICANN CZDS approval with redistribution limits or come from sources whose terms do not allow resale. The lookalike watch covers the main use case (who registered a domain like mine?) using only official per-domain RDAP queries.

### Limits

- Max 5,000 domains and 1,000 IPs per run; up to 10 lookalike source domains with up to 300 candidates each.
- Each RDAP server gets one request at a time with at least 1 s spacing (configurable up to 10 s); HTTP 429 `Retry-After` is always honoured. Large batches on one registry (e.g. 5,000 .com names) therefore take about 1.5 hours.
- Data is as published by each registry at query time; registrar-level expiry can differ from registry expiry during auto-renew periods.

### Run time, aborts and partial results

- **Run time** is set by the per-server spacing, not by your memory setting: about 1 second per domain on the same registry (for example 100 .com names ≈ 2 minutes; 5,000 ≈ 1.5 hours). Different registries are queried in parallel. A registry that asks for a long pause (HTTP 429 with a long `Retry-After`) is skipped for the rest of the run, and those domains are reported as errors, not charged.
- **Set the run timeout above the expected time.** If the run times out or you abort it, every row already in the dataset stays there; each looked-up domain is charged at most once, right after its row is saved, and nothing is charged for domains not reached.
- **Saved only at the end:** the `DOMAINS_CSV` file, the `OUTPUT` summary and the Slack/webhook alert are written when the run finishes. An aborted or timed-out run has no CSV, no summary and sends no alert.
- **Monitor mode after an abort:** the stored state is updated domain by domain, so a change found in an aborted run is not reported as a change again on the next run. Check the aborted run's dataset (the `change` field) or re-run without aborting.
- **Partial success is normal:** one domain failing (no RDAP service, registry error, rate limit) never fails the whole run; it gets its own row with `lookupStatus` and an `error` text.

### Sources & compliance

- IANA RDAP bootstrap registry (RFC 9224): https://data.iana.org/rdap/ — public, read 11 Oct 2026 (publication 2026-09-30).
- RDAP responses from each registry/RIR's official RDAP service. Each response's terms-of-service link is returned in `termsOfServiceUrl` (e.g. Verisign RDAP terms: https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml, read 11 Oct 2026). Lookups are low-volume, one at a time per server, with an honest User-Agent (`SiteVerdict/domain-rdap-lookup`, contact https://apify.com/siteverdict/siteverdict-domain-rdap-lookup), for lawful purposes such as managing your own domains and security research — do not use the output for unsolicited marketing, as registry terms forbid it.
- **UK GDPR/PECR:** personal data is OFF and cannot be switched on. The optional "registrant organisation & country" field outputs only an organisation name and country when published unredacted. RDAP redaction markers (RFC 9537) are reported, never bypassed.
- SSRF protection on every request and redirect; secrets (webhook URLs) never logged.
- Not legal advice.

# Changelog

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

# Actor input Schema

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

Domain names (URLs are fine - we take the host). Up to 5,000 per run. Example: example.com, mybrand.co.uk

## `ips` (type: `array`):

IPv4 or IPv6 addresses (up to 1,000). Returns the network, holder organisation, country and abuse contact from the regional internet registry.

## `expiryAlertDays` (type: `integer`):

Domains expiring within this many days get an alert in the output (and in Slack/webhook if set).

## `sampleMode` (type: `boolean`):

Uses built-in fictional RDAP responses. Switched on automatically when no domains or IPs are given.

## `lookalikeOf` (type: `array`):

We generate typo, TLD-swap, homoglyph and combo variants of YOUR domains (e.g. mybrand-login.com, mybrnad.com, mybrand.co) and check each one in RDAP. Registered lookalikes are reported. Each candidate checked is one domain lookup.

## `maxLookalikesPerDomain` (type: `integer`):

Most likely variants first (TLD swaps, missing letters, swapped letters...).

## `onlyRegisteredLookalikes` (type: `boolean`):

Unregistered candidates are still checked (and charged) but not pushed to the dataset.

## `monitorMode` (type: `boolean`):

Remembers registrar, expiry, status, nameservers and DNSSEC per domain in a named key-value store and reports changes. Schedule daily or weekly.

## `monitorStateName` (type: `string`):

Separate watch lists need separate names (stored as siteverdict-rdap-<name>).

## `onlyChanges` (type: `boolean`):

In monitor mode, unchanged domains are not pushed (still checked and charged).

## `slackWebhookUrl` (type: `string`):

Optional. Sends one message per run when something needs attention (expiry, hold, change, registered lookalike). Stored encrypted, never logged.

## `webhookUrl` (type: `string`):

Optional HTTPS endpoint. Stored encrypted, never logged.

## `includeRegistrantOrg` (type: `boolean`):

OFF by default. Adds only the registrant ORGANISATION name and country when the registry publishes them unredacted. Individual names, emails, phones and addresses are never output.

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

For thin registries (.com/.net) the registry links to the sponsoring registrar RDAP for fuller registrar details. One extra request per domain (not charged extra).

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

Different RDAP servers are queried in parallel; each server gets one request at a time.

## `minIntervalMsPerServer` (type: `integer`):

Politeness spacing between requests to the same RDAP server. Retry-After on HTTP 429 is always honoured.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "iana.org"
  ],
  "expiryAlertDays": 30,
  "sampleMode": false,
  "maxLookalikesPerDomain": 50,
  "onlyRegisteredLookalikes": true,
  "monitorMode": false,
  "monitorStateName": "default",
  "onlyChanges": false,
  "includeRegistrantOrg": false,
  "followRegistrarRdap": false,
  "maxConcurrency": 4,
  "minIntervalMsPerServer": 1000
}
```

# Actor output Schema

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

No description

## `output` (type: `string`):

No description

## `files` (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": [
        "example.com",
        "iana.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("siteverdict/siteverdict-domain-rdap-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": [
        "example.com",
        "iana.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("siteverdict/siteverdict-domain-rdap-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": [
    "example.com",
    "iana.org"
  ]
}' |
apify call siteverdict/siteverdict-domain-rdap-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,siteverdict/siteverdict-domain-rdap-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/RWEGu6Cr1LvHLWkpg/builds/nJEmRyaHilPlZxhur/openapi.json