How to Check Domain Availability in Bulk Natively on the Cloudflare Edge

If you have ever attempted to check a list of 500 domain names using a traditional web application, you know how slow the experience can be.

You paste your list, hit scan, and watch a loading spinner rotate for three minutes while the server makes sluggish, sequential database requests.

Often, the page times out halfway through, forcing you to reload and start over.

Traditional web applications are slow because they query domains from a centralized server located in a single physical data center (like AWS us-east-1).

For every name on your list, the server must run a standard socket lookup, wait for the global DNS network to route the response, and return the output.

Modern serverless computing and edge networks (like Cloudflare Workers) have completely changed this architecture.

This guide details the physics of edge-based name resolution, explains the DNS-over-HTTPS (DoH) protocol, and outlines how concurrent edge queries run scans in seconds.

---

Quick answer

To check domain availability in bulk at high speed, modern web tools execute queries natively on the network edge using DNS-over-HTTPS (DoH).

Instead of routing your entire list to a single centralized server, an edge-based worker intercepts the request at the user’s nearest local network node.

The worker then splits the domain list and sends parallel, asynchronous DoH requests to public resolvers (like Cloudflare 1.1.1.1 or Google 8.8.8.8).

Because these queries execute concurrently across thousands of global edge nodes, a scan of 100 domains completes in less than a single second.

---

What is DNS-over-HTTPS (DoH)?

To understand why edge checking is so fast, we must look at how browsers query domain records.

Traditionally, computers run DNS queries using raw UDP or TCP packets. These packets are unencrypted and require specialized system sockets, which cannot run natively inside a standard web browser environment.

DNS-over-HTTPS (DoH) translates these raw network packets into standard HTTPS GET requests.

Instead of opening a legacy network socket, a browser or serverless worker sends a clean JSON request to a secure DoH endpoint:

https://cloudflare-dns.com/dns-query?name=example.com&type=A

The DoH resolver processes the query, locates the domain’s active records, and returns a structured JSON response back over HTTPS:

{
  "Status": 0,
  "TC": false,
  "RD": true,
  "RA": true,
  "AD": false,
  "CD": false,
  "Question": [
    {
      "name": "example.com.",
      "type": 1
    }
  ],
  "Answer": [
    {
      "name": "example.com.",
      "type": 1,
      "TTL": 3600,
      "data": "93.184.216.34"
    }
  ]
}

If the Answer array is returned containing active record coordinates, it proves the domain has configured nameservers and is currently taken.

---

The architectural magic of serverless edge workers

A serverless worker does not run on a traditional virtual machine. It operates inside a lightweight V8 isolate container distributed across hundreds of global data centers.

When you paste a list into a modern bulk checker:

1. Anycast Routing: Your web request is automatically routed to the closest physical data center node (minimizing network travel latency).
2. V8 Isolate Startup: The worker container boots up instantly (in less than 1 millisecond), bypassing traditional cold-start delays.
3. Asynchronous Concurrency: The worker utilizes Javascript’s native asynchronous environment (Promise.all) to send all 100 DoH requests at the exact same millisecond.
4. Edge Aggregation: The edge node processes the parallel responses as they arrive, aggregates the status data into a single payload, and streams it back to your browser window.

By running this process close to the user and utilizing massive parallel requests, edge resolution completely eliminates centralized server delays.

---

DNS record status vs RDAP registry status

When auditing domains at high volumes, you must understand the limitations of DoH queries:

• DNS Resolution (DoH): Fast, lightweight, and completely free of rate-limiting blocks. It is the perfect tool to filter out 90 percent of taken domains instantly. However, if a domain is registered but has no configured records, a DNS check will show it as “free”.
• RDAP Registry Checks: Queries the official domain registry database directly to prove actual legal ownership. It is 100 percent accurate, but it is much slower and subject to strict IP rate-limiting policies.

A modern, high-velocity domain audit uses DoH to filter down a massive brainstorm list to a tiny shortlist, then runs RDAP checks purely on those remaining candidates to confirm final registration safety.

---

Checklist: Architecting a high-speed domain audit

• Does your audit tool use asynchronous Promise grouping to run concurrent scans?
• Are you routing queries through Anycast edge networks to minimize local network latency?
• Did you confirm that your DNS queries use JSON-based DoH requests rather than raw UDP packages?
• Are you caching DNS records with appropriate Time-To-Live (TTL) targets to save bandwidth?
• Did you verify that your code handles registry RDAP rate-limiting fallbacks safely?

---

FAQ

Why does Cloudflare DNS-over-HTTPS return a different response than Google DoH?

Both resolvers pull from the same global root registries, but they may cache responses differently. If a domain was registered in the last five minutes, one resolver’s cache may not have updated yet, resulting in a temporary mismatch.

Is there a limit to how many domains I can check concurrently using DoH?

Public DoH resolvers (like 1.1.1.1) allow thousands of requests per minute from a single IP. However, to maintain optimal performance and prevent browser thread blocks, you should chunk your concurrent batches to 50 domains per request group.

What does the “Status” number in a DoH JSON response mean?

A status of 0 means the query completed successfully (and active records are returned). A status of 3 (NXDOMAIN) means the domain does not exist in the routing grid, which is a strong signal that the name might be available.

---

Next step

Experience the performance difference of serverless computing. Paste a list of up to 100 domain names into our bulk checker right now. Our Cloudflare Worker will execute parallel DoH queries directly on the edge, returning complete availability signals in under a single second.

Disclaimer: Edge-based DNS availability check results represent active nameserver configuration. Always perform final registrar lookups before making registration and branding decisions.