Ip Location Check at a glance
Ip Location Check is a ready-to-run Apify actor from abotapi for collecting agents data. Its documented output includes ip address, country, code, region and city, which you can export as JSON, CSV or Excel or read through the Apify API. The actor itself is free; you pay only for Apify platform usage.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Agents, Developer Tools, SEO tools
- Pricing
- Free actor, platform usage only
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 8 options
Look up geographic locations for IP addresses. Supports batch lookups with country, city, subdivision, coordinates, and timezone data.
What Ip Location Check can do
- Batch lookups in one run. Submit any number of IPv4 or IPv6 addresses in a single call and get one record back per address.
- Country down to city and coordinates. Country, region, city, postal code, latitude, longitude, timezone and an approximate accuracy radius for each address.
- Multi-language place names. Country, region and city names come back in the language you choose, not just English.
- Honest failures, not silent nulls. An address that cannot be resolved comes back with success: false and a plain-language error, instead of a record full of nulls that looks like a real match.
- IPv4 and IPv6 side by side. Mix both address families in the same input list.
- Fresh location data without extra work. The location database is refreshed automatically: each run reuses a copy that is less than 24 hours old, and fetches the latest version once that copy is older.
Choose what to collect
These inputs let you configure Ip Location Check. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
ipAddressesarray · required | List of IP addresses to look up (IPv4 or IPv6) |
languagestring | Language for location names (ISO 639-1 code) |
resumeFromRunIdstring | Optional. ID of a previous run of this actor (or of its dataset). Addresses already in that dataset are skipped, so this run returns only the remaining ones. For recurring monitoring use Incremental mode below instead. |
incrementalModeboolean | Turn this on for scheduled runs. Each address is tracked together with its language. The first run returns every address as NEW; later runs return only NEW and UPDATED addresses, and unchanged addresses are not returned and not billed. An address counts as UPDATED when any of these fields changes: country, countryCode, subdivision, city, postalCode, latitude, longitude, timezone, accuracyRadius, success, error, continent, continentCode, isInEuropeanUnion, registeredCountry, registeredCountryCode, subdivisionCode, network, metroCode, asn and asOrganization. The input and data fields are not compared. If the ASN database is temporarily unavailable, the remembered asn and asOrganization are kept so that is not reported as a change. Every returned row gets changeType, changedFields, firstSeenAt and lastSeenAt. Fields listed under 'Ignore fields' below never count as changes though they are still returned. Addresses you stop submitting are not reported as expired. To continue one interrupted run instead, use Resume above. |
ignoreFieldsForChangesarray | Output field names that should NOT make an address count as UPDATED, for example accuracyRadius or postalCode. By default every field counts. Ignored fields are still returned in the output. |
mcpConnectorsarray | Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write or digest. Leave empty to skip; never changes the dataset output. |
notionParentPageUrlstring | URL or id of the Notion page under which result pages are created. Required to enable the Notion export; ignored by other connectors. |
Show 1 more input
| Input | What it controls |
|---|---|
maxNotifyListingsinteger | Cap on results written to each connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
ipIP AddresscountryCountrycountryCodeCodesubdivisionRegioncityCitylatitudeLat (number)longitudeLng (number)timezoneTimezonesuccessOKpostalCodePostal CodeaccuracyRadiusAccuracy Radius (km)errorErrorShow 15 more fields
changeTypeChange TypechangedFieldsChanged FieldsfirstSeenAtFirst Seen AtlastSeenAtLast Seen AtinputInputcontinentContinentcontinentCodeContinent CodeisInEuropeanUnionIn European UnionregisteredCountryRegistered CountryregisteredCountryCodeRegistered Country CodesubdivisionCodeSubdivision CodenetworkNetworkmetroCodeMetro CodeasnASNasOrganizationAS OrganizationExample output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"ip": "203.0.113.42",
"country": "Example Country",
"countryCode": "ZZ",
"subdivision": "Example Region",
"city": "Example City",
"postalCode": "00000",
"latitude": 12.345,
"longitude": 67.89,
"timezone": "Etc/UTC",
"accuracyRadius": 50,
"continent": "Example Continent",
"continentCode": "ZZ",
"isInEuropeanUnion": false,
"registeredCountry": "Example Country",
"registeredCountryCode": "ZZ",
"subdivisionCode": "EX",
"network": "203.0.113.0/24",
"metroCode": null,
"asn": 64500,
"asOrganization": "Example Network Ltd",
"success": true,
"error": null,
"input": "203.0.113.42",
"data": {
"ip": "203.0.113.42",
"country": "Example Country",
"asn": 64500
}
}Ways to use this data
- Ad targeting validation: confirm ad impressions and click traffic are landing in the geographic regions you're paying to target.
- Fraud and account-abuse checks: flag sign-ups, orders or logins whose IP location doesn't match the address or region a user claims.
- Content and pricing localization: route visitors to the right language, catalog or price list based on where their IP resolves.
- Access and compliance controls: enforce geographic restrictions on an API or content library, or identify traffic from specific jurisdictions.
- Analytics enrichment: attach country, city and timezone to IP-based logs, sign-up funnels or usage analytics.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does Ip Location Check return?
The documented output for Ip Location Check includes ip address, country, code, region, city, lat, lng and timezone. Availability of each field depends on the source page and the selected mode.
How much does Ip Location Check cost?
The actor itself is free; you pay only for Apify platform usage. The Apify listing shows the current rate for every plan.
Why did my run finish with an empty dataset?
Either the IP addresses list was empty or held only blank entries (the run logs a warning and ends without looking anything up), or Incremental changes for scheduled runs was on and no address changed since the last run, or Resume from a previous run pointed at a run that already covered every address. Addresses that can't be located never make the run fail: each one still returns a record with success: false. A run only fails outright when the location database itself can't be loaded; run it again in a few minutes.
What do input and data contain?
input is the exact string you submitted, before whitespace is trimmed. data repeats the full lookup record as one nested object, for pipelines that expect a single object per address. asn and asOrganization are null when the ASN database is temporarily unavailable (in incremental mode the remembered values are kept instead). The databases are cached in a small named storage in your account (about 31 MB in total, kept between runs).
Can it look up my own IP address automatically?
No. There is no auto-detect option. List the address or addresses you want to look up in IP addresses.
Why did a lookup come back with success: false and every location field null?
Three cases produce this: the address string isn't a valid IPv4 or IPv6 address, the address is private, reserved or otherwise not covered by the location database, or the address matches a known network that the database has no country, city or coordinate data for. Check that record's error field for which one applies.
