Bulk DNS Lookup
Paste up to 10 hostnames or IP addresses — one per line — and resolve them all at once. Hostnames return their A, AAAA, MX, NS and SPF records; IP addresses return their reverse-DNS (PTR) name. Pure DNS queries only, free, and no account.
What bulk DNS lookup is for
Checking one domain at a time is fine when you have one domain. The moment you manage a portfolio of
sites, run a migration, or inherit an estate of domains you have never seen before, doing the same five
DNS queries by hand over and over becomes the slow part of the job. A bulk lookup collapses that into a
single paste-and-go: every hostname comes back with its A (IPv4) and AAAA
(IPv6) addresses, its MX mail servers in priority order, its authoritative
NS name servers, and its SPF record — the one TXT entry that
starts with v=spf1 and decides whether your mail is trusted. Paste IP addresses instead and
each one is reverse-resolved to its PTR name, which is how you confirm an address actually belongs to the
host you think it does.
Real situations where running ten at once pays off:
- Server & DNS migrations: after re-pointing records, list every affected hostname and confirm A/AAAA and MX have all flipped to the new infrastructure — before you tell anyone the move is done.
- Audits & hand-offs: take inventory of a domain portfolio in one pass, spotting stale A records, missing SPF, or name servers that still point at a registrar you left years ago.
- Mergers & acquisitions: when you inherit another company’s domains, a bulk sweep is the fastest honest map of where their sites and mail actually live.
- Catching drift: compare today’s answers against what you expected. An MX that quietly changed, or an SPF record someone edited, is exactly the kind of silent change that breaks email weeks later.
This tool performs pure DNS queries only. It never opens a connection to any of the hosts you enter — it just asks the DNS resolver what they resolve to — so there is nothing intrusive about it and no traffic ever reaches your targets. Results reflect what your server’s resolver returns at that instant; a single global view is not the same as worldwide DNS propagation, which can take anywhere from minutes to a day or two to settle everywhere.
Frequently asked questions
Why is there a 10-entry limit?
Each hostname triggers five separate DNS queries (A, AAAA, MX, NS and TXT/SPF), so ten hostnames can be fifty lookups in one request. Capping at ten keeps the tool fast and fair to share for free. If you submit more, we process the first ten and tell you the rest were skipped. For continuous watching or larger batches, see the monitoring and pricing options.
Why did a record come back empty?
An empty cell means that record type genuinely does not exist for that name, or the resolver could not reach the authoritative server at that moment. A domain with no MX, for example, simply does not receive mail at that name — that is a real answer, not an error. Recently changed records may also still be propagating.
Do you support reverse DNS for IPv6 addresses?
Not in this tool. IPv4 addresses are reverse-resolved to their PTR name, but IPv6 PTR resolution is inconsistent across server platforms, so rather than risk showing you a wrong or misleading result we flag IPv6 entries and skip the PTR step honestly.
Which SPF record do you show?
We list every TXT record on the name that begins with v=spf1. A correctly configured
domain has exactly one. If you see two, that is a misconfiguration worth fixing — multiple SPF
records cause receivers to treat SPF as permerror, which can hurt deliverability.
How this tool works: This tool runs in your browser and on our server in real time. Depending on the tool, results are computed directly from the input you provide or retrieved from live, authoritative data sources at the moment you run a lookup. We do not sell your data, and your lookups are kept private — any history shown here is stored only on your device.