Bulk Reverse DNS Lookup

About this tool

Resolve a whole list of IP addresses to hostnames in one run. Useful for reviewing firewall logs, auditing an address range or checking that every mail server in a fleet has a PTR record that confirms forward.

How to use it

  1. Paste up to 20 entries, one per line: single addresses, CIDR blocks such as 192.0.2.0/28, or short ranges such as 192.0.2.1-20.
  2. Run the lookup. Addresses are resolved in parallel and the table fills as results arrive.
  3. Scan the summary for how many addresses have PTR records and how many pass forward confirmation.
  4. Download the CSV to keep the result or to join it with the log you started from.

What the result contains

Each row shows the address, whether a PTR record exists, every hostname returned, whether at least one hostname resolves back to the same address, and the country, city and ISP from geolocation. The CSV export uses semicolons as separators so that hostnames containing commas stay in one column, and includes the same fields plus a header row.

Typical workflows

Log review: export the distinct source addresses from a web server or firewall log, paste them here, and the hostnames reveal which are search engine crawlers, which are cloud providers and which are consumer ISPs. Crawlers from major search engines publish PTR records that forward-confirm, so a client claiming to be a search engine bot without a matching PTR is misrepresenting itself.

Mail fleet audit: paste the addresses of every outbound mail server. Each one should show a PTR record naming the server and a passing forward confirmation. Any row that fails is a server whose mail is at elevated risk of rejection.

Address range inventory: a CIDR block expands to its individual addresses, so a /28 shows all sixteen with whatever reverse DNS the provider has set, which is a quick way to see which addresses in an allocation are in use and named.

Frequently asked questions

How should I format the list?

One entry per line, up to 20 addresses per run. Single IPv4 or IPv6 addresses, CIDR blocks such as 192.0.2.0/28 and short ranges such as 192.0.2.1-20 are accepted; blank lines are ignored.

Can I export the results?

Yes. Results download as a semicolon-delimited CSV with the address, whether a PTR record exists, the hostnames found, whether the hostname resolves back to the same address, and the country, city and ISP.

Why do some addresses show no PTR record?

The owner of that address block has not published reverse DNS for it. This is common for residential ranges and for cloud addresses that were never configured.

Why is the limit 20 addresses?

Each address needs several DNS queries plus a geolocation lookup, and the tool is free and shared. Split a longer list into batches; a CIDR block counts as the number of addresses it expands to.