Back to blog
June 8, 2026domainradararchitecture

100,000 domains in one request, billed for the answer

Most domain APIs cap a call at a few hundred domains and bill a flat rate. DomainRadar checks 100,000 at once and charges for the step that answered.

Jan Švábík

What checking 100,000 domains usually looks like

You have a list. Maybe it’s 50,000 brand variants you want to monitor, the long tail of an AI-generated naming run or a competitor research dump. The shape is the same: a CSV with tens of thousands of rows and one question. Which of these are available?

Open any of the usual suspects (GoDaddy, Namecheap, WhoisXML, Domainr) and the answer comes with strings attached:

  • The call cap. Most APIs top out at a few hundred domains per request; the most generous I know of, Namecheap, accepts around 5,000. Even at that cap, a 100k list is 20 separate requests you have to orchestrate, retry and reconcile, and most of the field is much smaller.
  • The orchestration tax. Now you’re writing retry logic, backoff, a queue and idempotency keys. That code doesn’t solve the actual problem.
  • The flat bill. Whether a domain was answered by a quick DNS lookup or needed a full WHOIS round trip, you pay the same per-check rate. The cheap checks subsidize the expensive ones, and you pay for both.

Each of those is a workaround for a constraint that doesn’t have to exist.

What we built instead

A bulk check that takes up to 100,000 domains at once, streams results back as they resolve and runs each domain through a pipeline of increasingly thorough steps:

Bloom filter  →  DNS  →  RDAP  →  WHOIS
   cheapest                          most thorough

Each step either answers or hands the domain to the next one, and the check stops at the first definitive answer. You’re billed at the rate of the step that answered. The steps after it never ran, so they cost nothing.

What that means in plain terms:

  • In Bloom mode, a domain the Bloom filter knows is registered is answered as taken at the Bloom rate, instantly and without a single network call. A Bloom filter can only prove that a domain is taken, never that it’s free, so everything it doesn’t recognize moves on.
  • Many domains are settled by a DNS lookup: an active record means the domain is registered.
  • When DNS can’t decide, the check moves to RDAP, the modern WHOIS over HTTPS.
  • The rest, such as registries without RDAP, fall through to a classic WHOIS lookup.
  • A domain we checked recently can come straight from the cache, which costs nothing.

No polling, no pagination, no retry plumbing on your side. Results stream in as the pipeline works through the list.

A worked example

An illustrative run on 100,000 .com domains in Bloom mode, from a list where most names are already taken:

Answered by Share Why
Bloom filter ~70% Registered .com names the filter already knows.
DNS ~22% An active DNS record settles the rest of the taken ones.
RDAP ~7% Names with no DNS record need the registry’s answer.
WHOIS ~1% Registries without RDAP and other edge cases.

If you priced this against a flat-rate competitor at, say, $0.005 per check, you’d pay $500 for the 100,000 calls regardless of difficulty. With most of the list answered at the cheapest steps, the DomainRadar bill for the same list is far lower. The exact number depends on your volume and your mix of TLDs, but the principle is fixed: easy domains are billed easy, hard domains are billed hard, and you only ever pay for the step that answered.

For lists that lean toward available names or less common TLDs, fewer domains stop early, more of them reach RDAP and the bill grows. That’s the point: the cost reflects how hard your question actually is, not a flat fee that assumes every domain is equally hard.

What this leaves you free to ignore

Once one bulk check takes 100,000 domains and streams the answers back, a lot of code no longer needs to exist on your side:

  • No rate-limit handling. One job, one stream of results.
  • No retry logic. Work interrupted inside DomainRadar is picked up again automatically; you see the final result.
  • No batch orchestration. No “split the list into chunks, fan out, collect, reconcile.”

That’s hundreds of lines of code you don’t write, don’t maintain and don’t get paged about at 3 AM.

Why we built it this way

We needed bulk domain checking for our own product work: naming runs for clients, brand monitoring across portfolios, infrastructure inventory. The off-the-shelf options either capped us, billed us a flat rate regardless of difficulty, or both. The pipeline shape (cheapest method first, escalate only when needed, bill at the step that answered) is the design we wanted to use ourselves and couldn’t buy.

It’s the same pattern behind every other Norcube product, which we wrote about in Why we built Norcube: build for yourself first, and ship what you’d actually pay for.

So we built it, ran it in production, and made it available.

Try it yourself

Create a free Norcube account and run a list through a bulk check. The free tier covers 500,000 checks every month, split across the pipeline steps so the cheap steps don’t subsidize the expensive ones and a single bad list can’t burn through the whole allowance. Full pricing is on the DomainRadar product page, and the details are in the docs.


DomainRadar is part of the Norcube platform. Learn more about DomainRadar.

// tick. tick. tick.
0 ticks since founding
Coming soon

Join the PromptHub waitlist

PromptHub is in active development. Leave your email and we'll invite you as soon as it opens, with a free tier and no credit card.

One email when access opens. No newsletter, no spam.