Bulk Lookup
Run one tool across a list of domains or IPs.
Enter a value above to run Bulk Lookup
e.g. mx
Quick answer
Bulk Lookup runs a single DNSLab tool across a whole list of domains or IP addresses at once and returns the results side by side. Use it to check many hosts in one pass instead of querying each one separately.
Bulk Lookup takes a single diagnostic tool and runs it against a whole list of domains or IP addresses at once, instead of you checking them one by one. Paste or upload your list, pick the tool you need, and get a row-by-row table of results you can scan or export. It is built for people who manage many names at scale: hosting providers auditing customer domains, security teams checking IP reputation, or an admin verifying that every domain in a portfolio has the correct record before or after a migration.
How it works
You supply a list of targets, one per line, and choose which underlying tool to apply, such as an A/AAAA lookup, MX check, or reverse DNS. Bulk Lookup then iterates through each entry, runs that same query, and collects the responses into one table. Queries are typically throttled and processed in small batches to avoid hammering resolvers and to stay within provider rate limits, so a large list finishes in sequence rather than all at once.
How to read the results
Each input becomes a row, with columns showing the target and the value returned by the chosen tool. A blank or NXDOMAIN cell means that domain has no such record, which is often the finding you care about. Compare rows to spot inconsistencies: one domain pointing at an old IP, a missing MX, or a stray record. Sort or export the table to CSV so you can hand it to a colleague or track changes over time.
Why it matters
Checking domains individually does not scale and invites mistakes. During a server migration, a TLS rollout, or a mail provider switch, you need confidence that every name is consistent, not just the handful you remembered to test. Bulk Lookup turns a tedious, error-prone manual loop into a single pass, making it easy to catch the one outlier in a hundred that would otherwise cause an outage or a delivery failure.
Frequently asked questions
- How many domains can I check at once?
- There is a practical limit to keep queries responsive and to respect resolver rate limits, so very large lists are processed in batches and may take longer. For lists of thousands of entries, split them into smaller groups or run them in sessions. Start with a modest batch to gauge timing before submitting your full list.
- Can I mix domains and IP addresses in the same list?
- It depends on the tool you select. A forward DNS lookup expects domain names, while reverse DNS and IP reputation checks expect IP addresses. Keep each list matched to the tool so every row returns a meaningful result. If you need both, run the domain-based tool on one list and the IP-based tool on another.
- Why do some rows return no result or an error?
- A blank or error row usually means that domain genuinely lacks the record you queried, the name does not resolve, or a lookup timed out. Timeouts can happen with slow authoritative servers; simply rerun those specific entries. Errors are useful signals too, since a missing MX or unresolved domain is often exactly the problem you set out to find.