Disclosure: I'm Lindenbyte, the small studio that built the Apify Actor used below, and this post was
drafted with AI assistance. All numbers come from real runs on 2026-11-16.
Naming a product usually goes like this: you have three name ideas, you type each one into a registrar's
search box, try .com, then .io, then .ai, and twenty tabs later you still don't have a clean overview. The
second half of the domain chore is worse: nobody remembers when the company domains expire until a renewal
email lands in someone's spam folder.
Both jobs can be done with one public data source: RDAP.
Why RDAP and not WHOIS
RDAP (Registration Data Access Protocol) is the structured successor of WHOIS. Instead of free-text output
that differs per registry, you get JSON over HTTPS with standard fields: registrar, creation and expiry
dates, EPP status codes (clientHold, redemptionPeriod, pendingDelete...) and nameservers. ICANN made
RDAP the definitive source for gTLDs and sunset the WHOIS requirement in 2025.
Which server answers for which TLD is listed in the IANA bootstrap file (data.iana.org/rdap/dns.json).
You look up the TLD, send GET <server>/domain/example.com, and a 404 means the registry does not know the
name. You can do this yourself with curl. The tedious part is everything around it: rate limits per
registry, TLDs missing from the bootstrap, ccTLDs without RDAP, and 404s that are not really "available".
That is what the Actor below handles.
1. Check a name x TLD matrix
Open the Bulk Domain Availability & Expiry Checker
(or the public example task "brand-name-domain-finder" on its page) and enter keywords plus extensions:
{ "keywords": ["lindenbyte", "northpeak", "brightlark"], "tlds": ["com", "io", "ai", "dev", "co", "app"] } 3 keywords x 6 TLDs = 18 domains. The run took under 3 seconds: 8 registered, 10 available, all
answered by registry RDAP servers.
| .com | .io | .ai | .dev | .co | .app | |
|---|---|---|---|---|---|---|
| lindenbyte | registered | free | free | free | free | free |
| northpeak | registered | registered | registered | registered | registered | registered |
| brightlark | registered | free | free | free | free | free |
The registered rows carry the details you need to decide whether a name is worth chasing:
| domain | registrar | created | expires | days left |
|---|---|---|---|---|
| northpeak.com | NameCheap, Inc. | 1998-12-03 | 2027-12-02 | 380 |
| northpeak.co | Dynadot Inc | 2025-12-08 | 2026-12-08 | 22 |
| brightlark.com | GoDaddy.com, LLC | 2013-08-02 | 2028-08-02 | 625 |
"northpeak" is taken everywhere, so drop it. "brightlark" is free on five of six TLDs, but the .com has
been registered since 2013 and is renewed until 2028, so do not count on getting it.
2. Audit a domain portfolio
Paste domains, URLs or subdomains; they are reduced to the registrable domain
(https://www.python.org/downloads/ becomes python.org, news.bbc.co.uk becomes bbc.co.uk, and
münchen.de is converted to punycode). Add an expiry window and, optionally, DNS records:
{ "domains": ["https://www.python.org/downloads/", "go.dev", "ruby-lang.org", "news.bbc.co.uk", "bund.de", "bnb.bg", "github.io", "münchen.de"], "expiringWithinDays": 120, "includeDns": true } Results for those 8 domains:
| domain | method | registrar | expires | days left | expiring soon |
|---|---|---|---|---|---|
| python.org | rdap | Gandi SAS | 2033-03-28 | 2323 | no |
| go.dev | rdap | MarkMonitor Inc. | 2027-02-13 | 89 | yes |
| github.io | rdap | MarkMonitor Inc. | 2027-03-08 | 112 | yes |
| ruby-lang.org | rdap | Japan Registry Services Co., Ltd. | 2027-09-16 | 304 | no |
| bbc.co.uk | rdap | British Broadcasting Corporation | 2034-12-13 | 2948 | no |
| bund.de | rdap | (not published by DENIC) | |||
| münchen.de (xn--mnchen-3ya.de) | rdap | (not published by DENIC) | |||
| bnb.bg | dns-heuristic |
With includeDns each registered row also gets A/AAAA, MX, NS, the SPF record and the DMARC policy, so
the same table tells you that bbc.co.uk publishes p=reject while python.org is still on p=none.
3. Turn it into a monitor
Set "mode": "monitor" and a stateKey (one per watch list). The first run outputs every domain as
new and saves a snapshot; later runs output only domains whose availability, status, expiry,
registrar, nameservers or EPP status changed, or that entered your expiry window. A renewal (from a test where I
edited the saved snapshot) looks like this:
"change": { "type": "changed", "fields": ["expiresAt"], "summary": "expiry 2027-09-14 -> 2028-09-14 (renewed)" } I ran the portfolio above twice in monitor mode: the first run output 8 baseline rows, the second checked
all 8 again and output 0 rows (nothing changed, nothing charged). Schedule it daily or weekly in Apify
and connect the dataset to email, Slack or a webhook; an empty run is the normal case. The example task
"domain-portfolio-expiry-monitor" on the Actor page is a starting point.
4. Pull it into Python or JavaScript
from apify_client import ApifyClient client = ApifyClient("<APIFY_TOKEN>") run = client.actor("lindenbyte/bulk-domain-availability-expiry-checker").call( run_input={"keywords": ["acme", "acmely"], "tlds": ["com", "io", "ai", "dev"]}) for row in client.dataset(run.default_dataset_id).iterate_items(): if row["available"]: print("FREE ", row["domain"]) else: print("taken", row["domain"], row.get("registrar"), (row.get("expiresAt") or "")[:10]) import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('lindenbyte/bulk-domain-availability-expiry-checker').call({ domains: ['example.com', 'example.org'], expiringWithinDays: 60, onlyExpiringSoon: true, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((d) => console.log(d.domain, d.expiresAt, d.daysToExpiry)); 5. Limits, honestly
- "Available" means "not registered at the registry". Premium and registry-reserved names can still be unregistrable or expensive. While testing,
india.iocame back as RDAP 404 with no DNS, yet it is a reserved country name. Confirm at a registrar before you print business cards. - ccTLDs without RDAP (.bg, .it, .es, .eu, .se, .jp and others) get a DNS heuristic: nameservers mean "likely-registered", NXDOMAIN means "likely-available". A registered domain without nameservers (on hold, suspended) will look available, and there is no expiry date or registrar for these TLDs.
- Some registries publish little. DENIC (.de) returns status and nameservers but no registrar or expiry, as bund.de above shows.
- When RDAP and DNS disagree (404 but the name is delegated), the row becomes
unknowninstead of a wrong "available", and unknown rows are free. - Registry RDAP terms forbid using the data for unsolicited marketing. Use it for registration decisions, portfolio management and security research.
Free alternatives: your registrar's bulk search box for availability, curl against the RDAP server for a
handful of domains, and your registrar's renewal emails. What the Actor adds: many TLDs and registries in
one run, rate-limit handling, change detection, JSON/CSV export and scheduling.
Pricing is pay per event: $0.001 per domain checked ($1 per 1,000), optional DNS records $0.001 per
domain, and a $0.002 start fee. Unknown rows and unchanged monitor rows are free. Feedback and feature
requests: the Issues tab on the Actor page.