# Domain Availability Checker: Bulk DNS + RDAP (`lineagersiui/domain-availability-checker`) Actor

Check which domain names are registered or available: bulk DNS delegation check for up to 1,000 domains, with RDAP confirmation of shortlisted available names. Name x TLD combinations. Free demo.

- **URL**: https://apify.com/lineagersiui/domain-availability-checker.md
- **Developed by:** [Lineage RSIUI](https://apify.com/lineagersiui) (community)
- **Categories:** Developer tools, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 domain checkeds

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: Bulk DNS + RDAP

**Find out which domain names are taken and which look available.** Give it up to 1,000 domains, or a list of names and TLDs (acme × com, io, ai…). Only registrable names are accepted, such as `acme.com` or `acme.co.uk`. Subdomains and bare suffixes are rejected. For each domain it reports:

- `registered`: the domain is delegated in DNS, or the registry's RDAP record shows it is registered;
- `available`: not in DNS, and the registry's RDAP service has no registration record (only when RDAP confirmation is on);
- `likely_available`: not in DNS, and not confirmed by RDAP. This is a strong hint, not a guarantee: names registered without nameservers also look like this;
- `unknown`: DNS did not answer (timeout or server failure). Not billed;
- `invalid_tld`, `not_registrable` or `invalid_input`: not a valid registrable domain. Not billed.

### Try it free first

Run it with empty input. A **free demo** checks 4 domains, which isn't billed, so you can see the output format.

### How it works

1. **DNS delegation check** for every domain (and once for each TLD, so a made-up TLD is never reported as available).
2. **Optional RDAP confirmation**, off by default. When it's on, up to 10 "looks available" names per run are checked with the registry, so that names registered but not in DNS (for example parked without nameservers, or on hold) aren't reported as available. It sends at most one request every 2 seconds to each registry. All RDAP lookups stop for the run if any registry refuses or rate-limits them. The Google Registry RDAP service (.dev, .app and others) is never queried, because its terms have no exception for checks before registration.

### What it can't tell you

- **Availability is not a guarantee.** Only a registrar can confirm a name at checkout. Premium, reserved and blocked names, and names released during the run, can differ.
- **No price or owner data.** It doesn't show registration prices or WHOIS contact details.
- **Some TLDs have no public RDAP service** (for example many country-code TLDs such as .io and .co). For those, results are DNS-only and are reported as `likely_available`.

### Fair use of registry services

Registries offer RDAP to help people look up registrations, including before registering a name. Their terms prohibit high-volume automated querying. This Actor therefore uses DNS for bulk checks and keeps RDAP to a small, paced, opt-in number of confirmations per run. Please use it to check names you're considering registering. It isn't for harvesting registration data.

### Acceptable use

Don't use this Actor to find look-alike or typo domains of other people's brands for typosquatting, phishing or impersonation. It has no typo or permutation generator, and none will be added.

### Output

One dataset item per domain, with `domain`, `tld`, `status`, `method` (`dns` or `dns+rdap`), `rdap` and `checkedAt`. A `SUMMARY` record holds the counts.

### Pricing

- **Pay per event:** each domain that gets a status (`registered`, `available` or `likely_available`) is one `domain-checked` event.
- **Not billed:** `unknown`, `invalid_tld`, `not_registrable`, `invalid_input`, and the demo.
- The price is shown on the Pricing tab. You can cap the maximum charge per run in Apify's run options.

### Support

Open an issue on this Actor's **Issues** tab.

### About

- **Independent:** made by an independent developer. Unofficial; not affiliated with or endorsed by Apify or any domain registry.
- **Built with AI:** built and maintained with the help of AI tools, under the developer's direction.

# Actor input Schema

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

Full domain names, e.g. acme.com or münchen.de. URLs are accepted; the host is used. Up to 1,000 per run (with the combinations below).

## `names` (type: `array`):

Base names (e.g. acme). Each is combined with every TLD below.

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

TLDs to combine with the names above, e.g. com, io, ai.

## `confirmWithRdap` (type: `boolean`):

Asks the registry's RDAP service about names that look available in DNS, so registered-but-unused names are not reported as available. Off by default. At most 10 names per run, paced, and stopped if a registry asks us to slow down, to respect registry terms. Not all TLDs offer RDAP (e.g. .io, .co).

## `maxRdapConfirmations` (type: `integer`):

RDAP lookups per run (0 to 10). DNS checks are not limited by this.

## Actor input object example

```json
{
  "tlds": [
    "com",
    "io",
    "ai",
    "co",
    "net",
    "org"
  ],
  "confirmWithRdap": false,
  "maxRdapConfirmations": 10
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "tlds": [
        "com",
        "io",
        "ai",
        "co",
        "net",
        "org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lineagersiui/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 = { "tlds": [
        "com",
        "io",
        "ai",
        "co",
        "net",
        "org",
    ] }

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

```

## MCP server setup

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