Bulk DNS Lookup
Resolve up to 25 targets with controlled concurrency and exportable results.
Explicit network action
Resolve a bounded list
Request disclosure
- Destination
- https://cloudflare-dns.com/dns-query
- Provider
- Cloudflare 1.1.1.1
- Requests
- 0 credentialless HTTPS GETs
- Scheduling
- At most 4 concurrent · 5 seconds each · no retry
Every target leaves the browser.
Cloudflare receives each query name, selected record type, your connection IP, and normal HTTPS metadata. Targets are present in GET URLs. StackCache does not proxy, persist, or retry the requests.
No requests made
Review the request count before submitting.
Working notes
Use Bulk DNS Lookup with the boundary visible.
Bulk DNS Lookup resolves up to 25 unique targets for one selected record type through the disclosed Cloudflare DNS-over-HTTPS endpoint. Requests use controlled concurrency, retain per-target outcomes in memory, and can be exported as spreadsheet-safe CSV or structured JSON.
What is Bulk DNS Lookup?
When managing multiple domains, migrating DNS, or auditing infrastructure, looking up records one domain at a time is inefficient. Bulk DNS Lookup resolves the same record type across up to 25 domains in a single batch operation. You can query any standard record type — A, AAAA, MX, CNAME, TXT, NS, SOA, CAA, PTR, and more — for all targets at once, with controlled concurrency (at most four parallel queries) to avoid overwhelming the resolver. Each result shows the DNS status code (NOERROR, NXDOMAIN, SERVFAIL), the DNSSEC AD flag, answer records with TTLs, and any error details. Results can be exported as spreadsheet-safe CSV (properly escaped for Excel/Sheets) or structured JSON for programmatic use. Common use cases include verifying that MX records are consistent across all your domains, checking that TXT records (SPF, DMARC) are published for every domain in your portfolio, and confirming that DNS changes have propagated after a migration. Queries go through Cloudflare's DNS-over-HTTPS resolver, which provides a single recursive resolver perspective — not a global propagation check.
When to use it
- Domain portfolio auditing — check that all your domains have correct MX, SPF, and DMARC records published.
- DNS migration verification — after changing nameservers or records, verify that the new records resolve correctly for all affected domains.
- SPF/DMARC compliance checking — batch-query TXT records for _dmarc.domain and domain to verify that email authentication records exist across all domains.
- Infrastructure monitoring — periodically check that A/AAAA records for all your services still point to the correct IP addresses.
- Competitive analysis — look up MX or NS records for multiple domains to see which email and DNS providers competitors use.
How to use it
- 01Enter one hostname, domain, or PTR-compatible address per line, select a record type, and review the exact request count.
- 02Submit explicitly to run at most four credentialless requests concurrently; cancel to discard partial results.
- 03Review each target's DNS status, DNSSEC AD flag, and answers, then copy or download the complete result set as CSV or JSON.
Common mistakes
- Confusing with propagation checking — this tool queries one resolver (Cloudflare). A successful result here does not mean the record has propagated to all resolvers worldwide.
- PTR record format — for reverse DNS lookups, enter the IP address directly. The tool constructs the correct in-addr.arpa or ip6.arpa name automatically.
- Duplicate targets — the tool deduplicates targets before querying. If you enter the same domain twice, it counts as one query.
- Missing trailing dot — DNS fully qualified domain names end with a dot, but you do not need to include it. The tool normalizes input automatically.
- Rate expectations — with controlled concurrency of 4, a batch of 25 targets completes in approximately 6-7 sequential rounds. Large batches take a few seconds.
Synthetic example
Three-domain MX lookup
Input
example.com cloudflare.com iana.org · MX
Result
Three ordered per-target results with MX answers, TTLs, status, and DNSSEC AD state
Related standards
Limits and data boundary
- Each unique target creates a separate GET request. Cloudflare receives every query name, record type, connection IP, and normal HTTPS metadata.
- Results reflect one recursive resolver at one moment; they do not establish global DNS propagation or authoritative-server agreement.
- There are no automatic retries. Cancellation discards partial results, and completed results remain in memory unless explicitly downloaded.
Frequently asked questions
- How many domains can I look up at once?
- Up to 25 unique targets in a single batch. Requests run with controlled concurrency (at most four in parallel) to avoid overwhelming the resolver.
- Can I export the results?
- Yes. Download results as CSV (spreadsheet-safe with proper escaping) or structured JSON. Both formats include all targets, statuses, and answers.
- Does this check DNS propagation?
- No. Results reflect one query to Cloudflare's resolver at one moment. For propagation checking, you would need to query multiple resolvers in different locations.
Keep working