Bulk IP Lookup: Free Geolocation for 20 IPs

A bulk IP lookup tool checks several IP addresses in one run and returns the location, ISP and coordinates for each one. Paste up to 20 IPs, one per line, and you get a results table plus a CSV export. It suits log reviews, traffic audits, fraud checks and server investigations.

What Is a Bulk IP Lookup?

A bulk IP lookup is a geolocation check run on a list of IP addresses instead of one address at a time. For every IP, a data provider returns its best estimate of where the address is used and which network owns it. You get a table you can scan, sort and share.

An IP address is a numeric label assigned to a device or network, such as 8.8.8.8. It does not carry a street address. Providers build location estimates from registration records, routing data and other signals, so every result is an approximation, not a GPS fix.

This tool returns these fields for each address: city, region, country, country code, ISP, latitude and longitude. Each row also shows where the data came from and when it was retrieved, when that information is available.

How to Use the Bulk IP Lookup Tool

You can check a full list in under a minute. Follow these steps:

1. Open the IP addresses box. The hint reads "Enter up to 20 IPs (Each IP must be on separate line)".
2. Paste or type your addresses with one IP per line. The placeholder shows the format: 171.24.46.35, 8.8.8.8, 1.1.1.1.
3. Watch the counter under the box. It shows how many lines you have entered out of the 20 allowed (for example 0 / 20).
4. Complete the verification step if one appears, then press the lookup button under the box.
5. Wait while the progress bar fills. The tool checks addresses one after another and adds each row to the table as it finishes.
6. Review the table, then use the export button to download the results as a CSV file.
7. Select Try New IP to clear the page and start another batch.

Worked Example: Checking Five Addresses From a Log

Say you pulled five IPs from a web server log after a spike in traffic and want to know where they came from. You enter:

• 8.8.8.8
• 1.1.1.1
• 171.24.46.35
• 203.0.113.9
• 999.1.1.1

The counter reads 5 / 20, so you are within the limit. After the run, the first three addresses return rows with country, ISP and coordinates. You would expect the first two to resolve to well-known public DNS services, which tells you they are infrastructure, not human visitors. The fourth may return limited data because it sits in a range reserved for documentation examples.

The fifth is not a valid IPv4 address, because no octet can exceed 255. That row stays in the table with a note instead of vanishing, and it also appears in the CSV. This is useful: you can see exactly which line in your list needs fixing.

Next, you group the valid rows by country and ISP. If three of your five suspicious hits belong to one hosting provider, you have a stronger lead than three unrelated residential addresses.

How Do You Read the Results?

Each row answers two questions: where does this address appear to be, and who runs the network behind it. The table below explains the main columns.

What a good result looks like

A good row has a country, a named ISP and coordinates, with a source and retrieval time. For most investigations, country plus ISP is enough to decide what to do next.

What a weak result looks like

Rows marked as provider-unverified mean the lookup failed, timed out, or returned something the tool could not read. Check that address again in a new batch. If it fails twice, the data provider may simply have no record for it.

How to act on what you see

• Many hits from one data center ISP: likely bots, scrapers or a proxy service. Consider rate limiting or blocking the range.
• Unexpected countries: compare against your real audience. A US-only store with several hits from far-off regions deserves a closer look.
• Mobile carrier ISPs: often real people. Many users can share one carrier address, so avoid blocking it.

When Should You Use a Bulk IP Lookup?

Use it whenever you have a short list of addresses and need context fast. Typical situations include:

• Log analysis: identify where crawlers, spikes or failed login attempts originate.
• Fraud and order review: compare the billing country with the visitor's IP country for a handful of suspicious orders.
• Analytics cleanup: check the addresses behind odd referral or form spam traffic before you build a filter.
• Email header checks: look at the sending IPs from a few messages to see which network sent them.
• Server and hosting audits: confirm that your own server IPs sit with the provider you expect.
• Competitor and client research: note where a set of sites is hosted, a common step in reverse IP lookup work.

Tips, Common Mistakes and Troubleshooting

Most problems come from the input list, not the results. These fixes cover the cases people hit most often.

Put one IP on each line

Commas, spaces or several addresses on one line will not be read as separate entries. If your data comes from a spreadsheet column, copy the column directly and each cell lands on its own line.

Remove ports and extras

A log entry like 8.8.8.8:443 includes a port number. Strip it so only the address remains. Do the same for brackets, quotes and labels copied from a report.

Start from domains? Convert them first

This tool accepts IP addresses, not domain names. If you only have domains, run them through a domain to IP converter and then paste the resulting addresses here.

Stay inside the 20 IP limit

Each run handles up to 20 addresses. If you have 100 IPs, split them into five batches of 20 and export each CSV. Merge the files in a spreadsheet afterward. Searches for lists of 500, 1,000 or 10,000 addresses will need that batching approach, or a different workflow for very large files.

Expect the 45 second cutoff

A batch stops after 45 seconds. Any rows not yet checked are marked as unverified with a note, and they remain in the table and CSV. Re-run only those addresses in a new batch.

Check your own address separately

If you want to know what your own connection looks like, use the My IP Address page and then paste the result here to compare it with other IPs.

Open the CSV in a spreadsheet

The export has these columns: IP, City, Region, Country, Country code, ISP, Latitude, Longitude, Status, Source, Retrieved UTC and Notes. It opens in Excel or Google Sheets, where you can sort by country, filter by ISP or count repeated networks with a pivot table.

How Accurate Is IP Geolocation?

IP geolocation is reliable at the country level and much less reliable at the city level. The page itself says locations are approximate provider estimates, and you should treat them that way.

• Country is usually the safest field. City and coordinates can be off by many miles, especially on mobile networks.
• VPNs, proxies and corporate networks show the location of the exit point, not the person behind it.
• Cloud and hosting addresses often resolve to the data center's region, which may differ from where the company operates.
• An address can be reassigned, so the same IP may map to different places at different times. The retrieval time on each row helps you judge freshness.

Never use a single IP result as proof of identity or legal location. Combine it with other evidence, such as account history or request patterns.

For deeper network context, an ASN lookup shows the autonomous system and IP ranges behind an address. If you need to expand a range into individual addresses first, a CIDR to IP range converter will list the first and last IP. You can find more utilities in the Network and IP tools collection.

Paste your list into the box above and run the lookup. In a few seconds you will have a clear table of locations and networks, and a CSV ready for your next step.