# Domain Availability Checker (`ozito/domain-availability-checker`) Actor

Fast, reliable domain availability checker using RDAP with automatic WHOIS fallback. Check one domain across up to 10 TLDs in a single request. Supports .com, .net, .org, .io, .ai, .dev, .app + custom RDAP endpoints. Structured JSON output with status, source & response time.

- **URL**: https://apify.com/ozito/domain-availability-checker.md
- **Developed by:** [Kal](https://apify.com/ozito) (community)
- **Categories:** Automation, AI, Agents
- **Features:** Limited permissions
- **Stats:** 11 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 domain checks

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 Availability Checker

Fast, reliable domain availability checker using **RDAP** with automatic **WHOIS** fallback. Check one domain name across up to **10 TLDs** in a single request and get structured JSON results.

### Features

- ⚡ **RDAP-first** — Uses the modern RDAP protocol for fast, structured lookups
- 🔄 **WHOIS fallback** — Automatically retries with WHOIS if RDAP is unavailable or inconclusive
- 🌐 **Multi-TLD** — Check up to 10 TLDs per run (`.com`, `.net`, `.org`, `.io`, `.ai`, `.dev`, `.app`, …)
- 🎯 **Custom RDAP endpoints** — Override or add RDAP endpoints for any TLD
- 🔁 **Built-in retries** — Automatic retry with backoff on rate limits (429) and server errors (503)
- 💰 **Pay-per-event pricing** — First 5 domain checks free, then $0.005 per check

### Input

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `domain` | `string` | ✅ | Base domain name **without** TLD (e.g. `myproject`) |
| `tlds` | `string[]` | ❌ | TLDs to check, max 10. Defaults to `["com", "net", "org"]` |
| `rdapEndpoints` | `object` | ❌ | Custom RDAP endpoint URLs keyed by TLD |

#### Example input

```json
{
    "domain": "myproject",
    "tlds": ["com", "net", "org", "io", "ai"],
    "rdapEndpoints": {
        "xyz": "https://rdap.nic.xyz/domain/"
    }
}
```

### Output

Results are stored in the default **dataset**. Each row contains:

| Field | Type | Description |
|-------|------|-------------|
| `domain` | `string` | Full domain checked (e.g. `myproject.com`) |
| `status` | `string` | `AVAILABLE`, `REGISTERED`, or `UNKNOWN` |
| `source` | `string` | Protocol used (`RDAP` or `WHOIS`) |
| `tld` | `string` | TLD that was checked |
| `response_time` | `number` | Lookup time in seconds |
| `checked_at` | `string` | ISO 8601 timestamp |

#### Example output

```json
[
    {
        "domain": "myproject.com",
        "status": "REGISTERED",
        "source": "RDAP",
        "tld": "com",
        "response_time": 0.32,
        "checked_at": "2026-02-14T19:30:00.000Z"
    },
    {
        "domain": "myproject.io",
        "status": "AVAILABLE",
        "source": "RDAP",
        "tld": "io",
        "response_time": 0.45,
        "checked_at": "2026-02-14T19:30:01.000Z"
    }
]
```

### Pricing

This Actor uses **pay-per-event** pricing:

| Tier | Domain checks | Cost |
|------|--------------|------|
| 🆓 Free | First 5 per run | $0.00 |
| 💳 Paid | 6th check onwards | $0.005 per check |

The Actor automatically stops if the user's spending limit is reached.

### Built-in RDAP endpoints

The following TLDs have pre-configured RDAP endpoints:

| TLD | Endpoint |
|-----|----------|
| `.com` | `rdap.verisign.com` |
| `.net` | `rdap.verisign.com` |
| `.org` | `rdap.publicinterestregistry.net` |
| `.io` | `rdap.nic.io` |
| `.ai` | `rdap.nic.ai` |
| `.dev` | `rdap.dev` |
| `.app` | `rdap.nic.google` |

For other TLDs without a pre-configured endpoint, the Actor will use WHOIS directly. You can add your own endpoints via the `rdapEndpoints` input field.

# Actor input Schema

## `domain` (type: `string`):

Base domain name without TLD (e.g., 'myproject')

## `tlds` (type: `array`):

List of top-level domains to check (max 10)

## `rdapEndpoints` (type: `object`):

Custom RDAP endpoint URLs by TLD (optional). Key is TLD, value is endpoint URL.

## Actor input object example

```json
{
  "domain": "myproject",
  "tlds": [
    "com",
    "net",
    "org"
  ],
  "rdapEndpoints": {
    "xyz": "https://rdap.nic.xyz/domain/"
  }
}
```

# Actor output Schema

## `overview` (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 = {
    "domain": "testdomain",
    "tlds": [
        "com",
        "net"
    ],
    "rdapEndpoints": {}
};

// Run the Actor and wait for it to finish
const run = await client.actor("ozito/domain-availability-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 = {
    "domain": "testdomain",
    "tlds": [
        "com",
        "net",
    ],
    "rdapEndpoints": {},
}

# Run the Actor and wait for it to finish
run = client.actor("ozito/domain-availability-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 '{
  "domain": "testdomain",
  "tlds": [
    "com",
    "net"
  ],
  "rdapEndpoints": {}
}' |
apify call ozito/domain-availability-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ozito/domain-availability-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/57H04nd7mgpTpynkQ/builds/PUoGvWpTWigqyRBoh/openapi.json