Domain Availability Checker — Bulk RDAP Status and Registrar avatar

Domain Availability Checker — Bulk RDAP Status and Registrar

Pricing

from $0.80 / 1,000 domain checkeds

Go to Apify Store
Domain Availability Checker — Bulk RDAP Status and Registrar

Domain Availability Checker — Bulk RDAP Status and Registrar

Domain availability: Bulk registry RDAP status, registrar, dates and nameservers. $0.001 per domain checked; start extra; usage included; failed results uncharged.

Pricing

from $0.80 / 1,000 domain checkeds

Rating

0.0

(0)

Developer

Logan Parker

Logan Parker

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Domain availability checks use registry RDAP for supported top-level domains, returning registration status, registrar, dates and nameservers without personal contact data. AI agents can call and pay through Apify MCP. List event rates are $0.001 per domain checked; start is extra, usage is included and failed results are uncharged.

Example result

Example record for the minimal input under How to use it, as this Actor returned it on 2026-10-18 in a run of its production image; the record is kept unchanged with the release.

{
"domain": "apify.com",
"ok": true,
"available": false,
"status": [
"client transfer prohibited"
],
"registrar": null,
"createdAt": "2009-06-02T17:14:10Z",
"expiresAt": "2035-06-02T17:14:10Z",
"nameservers": [
"ns-1225.awsdns-25.org",
"ns-1928.awsdns-49.co.uk",
"ns-449.awsdns-56.com",
"ns-839.awsdns-40.net"
],
"rdapServer": "https://rdap.verisign.com/com/v1/",
"rdapTermsUrl": "https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml"
}

How to use it

Start a run in Apify Console, by API or from an agent with an input like this one — it is the input Apify runs every day to test this Actor:

{"domains": ["apify.com", "hermes-availability-probe-7f3k2q.com"]}

Start with the minimal JSON example above, then adjust the fields in the table below. Read the Example result and Output fields sections for the returned record, Errors for failure codes, and Events and prices for result events and the separate platform start.

FieldTypeMeaning
domainsarrayDomain names, not URLs or IP addresses; internationalized names use IDNA.

Events and prices

EventTitleCharged whenFREE / BRONZESILVERGOLD / PLATINUM / DIAMOND
domain-checkedDomain checkedOne domain answered available or registered.$0.001$0.0009$0.0008

Platform usage is not passed through. Apify's automatic actor-start event remains $0.00005 per started GB (one GB or less counts once). The synthetic dataset-item event is absent. Charge limits stop further paying work; unprocessed inputs receive uncharged errors. Completed readable pending events are settled on abort.

Worked cost example: ten successful primary events cost $0.01 at list, plus actor start. Failures are not included in that count.

Call it from an agent

Through Apify's MCP server (https://mcp.apify.com) use call-actor:

{
"actor": "hermeskd/domain-availability",
"input": {
"domains": [
"apify.com",
"hermes-availability-probe-7f3k2q.com"
]
},
"callOptions": {
"maxTotalChargeUsd": 0.05,
"timeout": 600
},
"waitSecs": 30
}

Then call get-dataset-items with the returned defaultDatasetId. Dedicated tool URL: https://mcp.apify.com?tools=hermeskd/domain-availability

Output fields

FieldMeaning
domainNormalized input domain, or original invalid input.
okTrue only when the registry answered registered or unregistered.
availableTrue only for RDAP 404; false for registered; null for unanswered failures.
statusRegistry domain status codes.
registrarExplicit registrar organization only; formatted-person-name fields are not returned.
createdAtRegistry registration timestamp, when supplied.
expiresAtRegistry expiration timestamp, when supplied.
nameserversRegistry-provided nameserver names.
rdapServerIANA-selected service base URL.
rdapTermsUrlExplicit terms-of-service link from registry notices.
errorFailure, always uncharged.

Limits and run time

1–100 domains per run and at most one request per second per registry host. Registration-check purpose only: use this to consider registrations or modify existing registrations, not high-volume data mining. An unanswered domain has available=null and is uncharged. Only an explicit RDAP 404 answer means available=true. Its body is optional under RFC 7480 section 5.3; an empty answer is accepted only at the exact IANA-selected query URL without redirects. HTML or malformed replies remain uncharged failures. Registrar is returned only from explicit organization data; formatted person names and nested contact cards are omitted.

The default run timeout is 600 seconds. Typical run time on Apify, measured by its deploy of 2026-10-21: the minimal input under How to use it took 5–7 seconds a run at the default 512 MB (three runs, peak memory 60 MiB). The same input also ran and passed the pricing floor at 256 MB and 1,024 MB (the deploy's memory probes).

Errors

CodeMeaning
invalid_domainInput is not a valid domain name.
tld_not_supportedIANA lists no RDAP service for the TLD.
rate_limitedThe registry refused the check; availability remains unknown.
http_errorThe source answered an unsuccessful HTTP status.
download_failedThe request or connection failed within its bounded deadline.
source_schema_changedA source or tool response no longer has the verified protocol shape.
robots_disallowedrobots.txt forbids fetching the URL; no request was made to it.
blocked_hostThe host is on the deny-list or resolves to a private or local address; no request was made.
too_largeA documented response, expansion or traversal cap was exceeded.
timeoutThe input did not finish within the run's time budget.
invalid_inputThe run input passed the input schema but cannot be used; the message names the field.
internal_errorUnexpected failure; the message carries the error class.
charge_limit_reachedThe run reached its maximum total charge; this input was not processed.

No failure record is charged. A run fails only when all input outcomes are Actor-side failures; caller errors and a mixture of caller/Actor failures do not fail the run.

Sources and terms

Only process content you have the right to process. URL fetches obey HermesBot robots-group selection, the shared deny-list, public-address checks on connections and redirects, honest identity, deadlines and rate limits. No caller credentials, cookies, CAPTCHA solving, residential proxies or evasion. Use only to compare domain names before registration, at most 100 names per run and one request per second per registry server. IANA bootstrap selects the registry; no endpoint is guessed. Verisign terms exclude high-volume automation except reasonable registration needs. Registrant, administrative, technical and abuse contacts are omitted. Registrar is returned only from an explicit organization property, and may be null when the registry supplies only a formatted name. HTTP source probes verify 200/404 protocol shapes; they are not production-path Actor runs.

Not affiliated

This Actor is not affiliated with Google, Apify, IANA, Verisign or other named protocol/source providers. Third-party names describe compatibility and source material.

Changelog

  • 1.0 (2026-10-26) — store listing rewritten for the people and agents searching for this job: title, description, search-engine title and description, categories, and the README in the order a searcher reads it (what it does, a real result, how to use it, prices, the agent call).
  • 1.0 (2026-10-21) — first public release on Apify Store, after the deploy's typical calls, memory probes, benchmarks and pricing floor passed on the platform.
  • 1.0 (2026-10-19) — repairs from an independent review: DNS privacy, malformed publisher URLs, empty sitemap failures, responsive assets and schema prefill, as applicable to this Actor.
  • 1.0 (2026-10-18) — the production image, smoke input, three example tasks and benchmarks passed on GitHub-hosted Linux.
  • 1.0 (2026-10-17) — first implementation.