Bulk IP Lookup: Trace an Entire List in One Pass
Paste up to several hundred IP addresses into the field above in whatever shape you have them — one per line, comma-separated, or buried inside surrounding text. The parser extracts every valid IPv4 and IPv6 address, discards duplicates, and traces each one against the same data sources used by the single-address IP lookup: DB-IP Lite geolocation and RIPE AS-name records.
The output is a single ranked dossier table — address, country, probable region, AS operator, and a confidence rating for each row — plus one map plotting every traced address together. Ranges operated by hosting providers or VPN services are flagged LIKELY datacenter/VPN, a heuristic drawn from the AS operator name, never proof.
Where batch tracing earns its keep
- Blocklist review. Before you ban a list of addresses, see which countries and networks you would actually be blocking — and which entries are shared datacenter ranges rather than individual connections.
- CDN and monitoring inventories. Confirm that your edge nodes, probes, or health-check sources sit in the regions your dashboard claims they do.
- Abuse reports. Turn a raw list of offending addresses into a table grouped by network operator, so each report goes to the right abuse contact. The ASN lookup digs deeper into any single operator.
Limits and fair use
Each run returns at most 250 results; anything beyond that is dropped, with a note telling you how many were skipped. Rate limits apply per client, so very large jobs are better split across a few minutes than fired all at once. If your source material is a raw server log rather than a clean list, the log analyzer is the better tool — it parses common log formats and extracts the addresses for you.
Reading the results honestly
Country-level results are reliable, roughly 95–99% accurate. Region and city are estimates — about 55–80% and 50–75% respectively on fixed broadband, and frequently wrong for mobile carriers, VPN exits, and satellite links. That is why every row carries a confidence rating rather than a single confident pin. And to be plain about what this data is: IP geolocation describes networks, not people. It cannot identify an individual or resolve a street address, as explained in how accurate IP geolocation is. Want a feel for one dossier before pasting a hundred? See the example trace for 8.8.8.8.