← data exports  /  apify actor

Domain Availability Checker: Bulk RDAP

how to get the data with our Apify actor domain-availability-checker

Check if domains are available, in bulk: one row per domain with available or registered, registrar, creation and expiry dates and days to expiry, straight from the registry that runs the TLD (RDAP). Paste domains or links.

on apify
v0iddo/domain-availability-checker
category
developer tools, seo tools
build
0.1.7, built 2026-10-31
billing
Apify bills it per result; the price for your plan is on the actor's page.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

  • domain
  • available
  • status
  • registrar
  • Expires (expirationDate)
  • Days to expiry (daysToExpiry)
  • Registered (registrationDate)
  • note

What people use it for

  • Name shortlists: paste every candidate name for a brand or a product and keep the ones no one has registered.
  • Portfolio expiry watch: days to expiry and registrar of every domain you own, run on a schedule.
  • Brand protection: check one name across many extensions (.com, .net, .org, .app, .info and more) in one run.
  • List hygiene: registration date and domain age of every domain in a lead or vendor list.

Run it on Apify

  1. Open domain-availability-checker on Apify and sign in, or make an Apify account.
  2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
  3. Click Start. Rows appear on the Output tab while the run works.
  4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
  5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

  • Domains (domains, required): Domain names such as example.com or links such as https://www.example.com/page (the domain is taken from the link, www. removed). Up to 10,000 per run.
  • Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 1000.
  • Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

example inputjson
{
  "domains": [
    "google.com",
    "github.com",
    "wikipedia.org",
    "python.org",
    "mozilla.org",
    "voiddo.com",
    "bbc.co.uk",
    "example.net",
    "voiddo-availability-sample-7q3.com",
    "voiddo-availability-sample-7q3.org",
    "shop.github.com"
  ],
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

needs your own Apify tokenpython
# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "domains": [
        "google.com",
        "github.com",
        "wikipedia.org",
        # and 8 more, as in the example input above
    ],
    "maxItems": 20,
}
run = client.actor("v0iddo/domain-availability-checker").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

  • Available means not registered at the registry. A reserved or premium name can still be refused or cost more at a registrar.
  • A TLD without an RDAP service, or a registry that closes its RDAP service in robots.txt, gives status unknown with the reason. No guessing from DNS.
  • A name under a registered domain (shop.example.com) gives status subdomain: it cannot be registered on its own.
  • Answered: .com, .net, .org, .app, .dev, .page, .info, .biz, .club, .fr, .nl, .ca, .au and every other extension whose registry runs an open RDAP service. Not answered (status unknown): .io, .de, .eu, .co, .me and .us have no RDAP service listed by IANA; the registries of .xyz, .shop, .online, .site, .store, .tech and .in close theirs to automated clients.
  • Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
  • The actor reads only pages that the site's robots.txt leaves open to automated access.
  • Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
  • Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on the domain registries, cookies or an API key?

No. The actor reads only what every visitor of the domain registries can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 10,000 rows per run. Without a limit it stops at 1,000. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

every fact here is read from the actor's public data on Apify, every day; it last changed on