Reverse DNS (PTR) Bulk Lookup
Pricing
from $2.00 / 1,000 ip resolveds
Reverse DNS (PTR) Bulk Lookup
Resolve IP addresses to hostnames (PTR records) in bulk via DNS-over-HTTPS. Supports IPv4 and IPv6. For network mapping, log enrichment, security and email checks. No key, no proxy.
Pricing
from $2.00 / 1,000 ip resolveds
Rating
0.0
(0)
Developer
Bruno
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
23 days ago
Last modified
Categories
Share
Resolve IP addresses to hostnames (PTR records) in bulk, fast, over DNS-over-HTTPS. Works with IPv4 and IPv6. No API key, no proxy.
What it does
Give it a list of IPs and get the hostname each one points to (its PTR record) — the reverse of a normal DNS lookup. Great for making raw IPs human-readable at scale.
Use cases
- Log & traffic enrichment — turn server/firewall logs of IPs into readable hostnames.
- Network mapping — see what lives behind a range of IPs.
- Security & threat hunting — spot suspicious or unexpected hosts.
- Email deliverability — check that a sending IP has a valid PTR (rDNS), which mail servers require.
Input
| Field | Type | Description |
|---|---|---|
ips | array | IP addresses to look up (IPv4 or IPv6), e.g. ["8.8.8.8", "1.1.1.1", "2606:4700:4700::1111"]. |
Example input
{ "ips": ["8.8.8.8", "1.1.1.1"] }
Output
{ "ip": "8.8.8.8", "hostname": "dns.google", "found": true }
If an IP has no PTR record, found is false and hostname is null.
Export to JSON, CSV, Excel or Google Sheets, or pull it via the Apify API.
Tips
- Send thousands of IPs in one run — it batches automatically.
- Pair it with an IP-geolocation or ASN Actor to fully enrich your logs.
FAQ
Do I need a key? No. No proxy either — it uses public DNS-over-HTTPS.
IPv6 supported? Yes, both IPv4 and IPv6.
How am I charged? Pay per result (per IP resolved).