We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Bulk lookup IP address locations and network details with city-level accuracy.
Input Format
One record per line, format: IP Address
Supports space, comma, tab separators
• Supports up to 500 records per batch
• Automatic IP Address validation after clicking 'Next'
• If deduplication is enabled, duplicate records will be removed automatically
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Submit a list of literal IPv4 or IPv6 addresses to look up the location and network details available for each entry. The result can include country, province or region, city, ISP, and network owner. Each row keeps its own status and returned information, so a list can be reviewed and exported as a spreadsheet.
IP geolocation is an association between an address and a network location in lookup data. It is useful for adding context to a log or an incident list; it does not identify a person or provide a device's exact physical position. A VPN, proxy, mobile carrier, company gateway, or cloud egress can affect which network location appears.
Addresses such as those in the private IPv4 ranges documented in RFC 1918 are reused inside networks and are not globally unique. The IETF's special-purpose registries also distinguish other IPv4 and IPv6 ranges from ordinary public address space. RFC 1918 and RFC 6890 describe these address categories; they are useful background when deciding which log entries to submit.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste one IPv4 or IPv6 address per line, or import a TXT, CSV, XLS, or XLSX file. For a spreadsheet, put the IP address in the first column and an optional note in the next column. Keep each address as a literal address rather than a hostname.
Check the parsed rows, remove stray headings or blank lines, and confirm the list is within the 500-row cap. The lookup requires at least 20 billable records. Duplicate removal is enabled initially; review that option and the displayed quantity because billing is per billable record.
Start the batch after reviewing the displayed charge. Check the status and returned location or network information for each address. Keep any note with its corresponding row when you compare results with your source log.
Export the completed results as an XLSX workbook for spreadsheet review or internal follow-up.
Use cases
See how the tool fits into real work and everyday tasks.
A security analyst can submit a set of addresses from an alert, then compare returned regions and network owners with timestamps, account activity, and other evidence before deciding what to investigate.
A support team can attach a short case reference as a note for each address, export the workbook, and use the row pairing to discuss results with the relevant ticket or customer report.
An operations team can use available region and provider fields to group a set of network records for an initial review, then verify those groups against its own logs and business context.
Q&A
Find concise answers to common questions and confusing cases.
Duplicate removal is enabled by default, so repeated valid addresses may count once toward the billable quantity. You can review the deduplication setting and the quantity shown before continuing.
It means the service did not return an interpretable location record for that row, or the lookup failed. Check that the row contains a valid literal IP address and review its status; do not treat an empty result as a confirmed location.
Yes. In an imported sheet, use the second column for a note; when entering rows as text, separate the address and note in the corresponding fields. Notes help you match results back to your own records.
Notes
Review scope, result limitations, and important precautions before use.
This tool accepts valid literal IPv4 and IPv6 addresses, processes up to 500 rows per batch, requires at least 20 billable records, charges per billable record, and exports XLSX. The connected lookup service receives each submitted IP address individually. Do not include addresses or notes unless you are authorized to submit them.
Returned location is an estimate associated with network data, not GPS coordinates, proof of a device's current location, a person's identity, or proof of residence. Available fields can vary by address and returned record; this tool does not promise city-level coverage, a particular accuracy, update schedule, or complete results. Private and special-use addresses may not yield public geolocation. VPNs, proxies, mobile networks, and shared gateways can point to an exit or network location instead of an end user's location. Use results as a lead to compare with independent records, not as a sole basis for a security, eligibility, or identity decision.
Related
Discover related tools, collections, and available API capabilities.