# RDAP Whois — Domain & IP Lookup (`bgfc97/rdap-whois-lookup`) Actor

Modern Whois via official RDAP. Bulk lookup of domains and IPs: registration/expiration dates, registrar, status, nameservers, DNSSEC, IP network range, org and country. No key, no proxy.

- **URL**: https://apify.com/bgfc97/rdap-whois-lookup.md
- **Developed by:** [Bruno](https://apify.com/bgfc97) (community)
- **Categories:** Developer tools, Lead generation, Business
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 domain/ip 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?

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

## RDAP Whois — Domain & IP Lookup

Modern **Whois** using the official **RDAP** protocol (the IETF replacement for legacy port-43 Whois). Give it a list of **domains and/or IP addresses** and get clean, structured JSON — no key, no proxy, no captchas.

### What you get

**For domains:**

- Registration, expiration and last-changed dates
- Registrar (name + IANA ID)
- Domain status (EPP codes: clientTransferProhibited, etc.)
- Nameservers
- DNSSEC (signed or not)
- Registrant (when the registry publishes it)

**For IPs (IPv4/IPv6):**

- Network range (start/end address, CIDR)
- Network name, type and handle
- Organization and country
- Registration / last-changed dates

### Input

```json
{
  "queries": ["google.com", "github.com", "8.8.8.8", "1.1.1.1"]
}
```

Domains and IPs can be mixed in the same run — the actor auto-detects each.

### Output (example)

```json
{
  "type": "domain",
  "domain": "google.com",
  "registration": "1997-09-15T04:00:00Z",
  "expiration": "2028-09-14T04:00:00Z",
  "registrar": "MarkMonitor Inc.",
  "status": ["clientTransferProhibited"],
  "nameservers": ["ns1.google.com", "ns2.google.com"],
  "dnssec": false
}
```

### Use cases

- Domain portfolio & expiry monitoring
- Brand protection / typosquat research
- Threat intelligence & IP attribution
- Lead enrichment (registrar / org data)

### Notes

- Data comes from authoritative registry/RIR RDAP servers via `rdap.org`.
- A few TLDs still lack RDAP; those return an `error` row instead of failing the run.
- You are billed per lookup (per domain/IP in `queries`).

# Actor input Schema

## `queries` (type: `array`):

List of domain names and/or IP addresses (IPv4/IPv6) to look up. Example: google.com, github.com, 8.8.8.8, 1.1.1.1.

## Actor input object example

```json
{
  "queries": [
    "google.com",
    "github.com",
    "8.8.8.8"
  ]
}
```

# 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 = {
    "queries": [
        "google.com",
        "github.com",
        "8.8.8.8"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bgfc97/rdap-whois-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 = { "queries": [
        "google.com",
        "github.com",
        "8.8.8.8",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("bgfc97/rdap-whois-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 '{
  "queries": [
    "google.com",
    "github.com",
    "8.8.8.8"
  ]
}' |
apify call bgfc97/rdap-whois-lookup --silent --output-dataset

```

## MCP server setup

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