BIN + IP Lookup Checker

What does BIN + IP Lookup Checker do?

This Actor combines a public BIN/IIN lookup from Binlist with optional public IP geolocation from ipapi.co. It returns structured card-scheme, issuer-country, and IP-country data for risk research. It does not accept full card numbers, credentials, private IPs, or protected tokens.

Why use BIN + IP Lookup Checker?

• Process a bounded list of unique BIN + public-IP pairs.
• Keep the older { "bins": [...], "ip": "..." } input shape working.
• Control maximum items, concurrency, request timeouts, retries, backoff, and pacing.
• Compare issuing and IP country codes with a simple COUNTRY_MISMATCH flag.
• Use Apify scheduling, API access, monitoring, webhooks, and integrations around a repeatable public-data workflow.
• Stop safely when a source reports CAPTCHA, login, paywall, geofence, device, WAF, access-denial, or rate-limit signals.

What data does the Actor extract?

Field	Type	Description
recordType	string	lookup for a public BIN row or diagnostic for a non-success row.
bin	string	Six to eight digit BIN queried.
ip	string	Public IP queried, when supplied and accepted.
scheme, type, brand	string	Public card metadata.
bankName, bankUrl	string	Public issuer information when returned.
cardCountry, ipCountry	string	Issuer and IP country codes.
ipCountryName, ipContinent	string	IP country and derived continent names.
ipVersion, ipNetwork	string	IP version and public network prefix.
ipRegion, ipRegionCode, ipCity, ipZip	string	Public IP location labels.
ipTimezone, ipUtcOffset	string	Public timezone and UTC offset.
ipCallingCode, ipCurrency, ipCurrencyName	string	Public country calling and currency metadata.
ipLanguages	array	Unique public language codes for the IP country.
ipCountryArea, ipCountryPopulation	number	Published country area and population values.
ipAs, ipOrg	string	Autonomous-system identifier and organization.
countryMatch, riskFlag	boolean/string	Country comparison and mismatch indicator.
ipLookupStatus	string	IP enrichment status, including not_requested, success, no_data, failed, and rejected.
found, dataAvailable	boolean	Successful lookup rows set both to true; diagnostic rows set both to false and are excluded from success counts.
diagnosticCode, message	string	Safe diagnostic details for non-success rows.

How to run a BIN and IP lookup

1. Open the Input tab and provide lookups with safe public examples such as 457173 + 1.1.1.1.
2. Set maxItems to the maximum number of unique pairs you want to process.
3. Adjust concurrency, requestTimeoutMs, maxRetries, retryDelayMs, and pacingMs if the public sources require a slower run.
4. Run the Actor and inspect the dataset. Use recordType, found, and dataAvailable to separate results from diagnostics.
5. Download the dataset in JSON, HTML, CSV, or Excel format, or use the API tab for programmatic access.

The legacy input form remains supported:

{
  "bins": ["457173", "411111"],
  "ip": "8.8.8.8",
  "maxItems": 2
}

How much does it cost?

Apify compute and storage usage apply according to your Apify plan. The Actor makes only bounded public requests controlled by the input limits; the public data sources may also impose their own rate limits. No cloud deployment or proxy purchase is required by this Actor.

Output example

{
  "recordType": "lookup",
  "position": 1,
  "bin": "457173",
  "ip": "1.1.1.1",
  "scheme": "visa",
  "cardCountry": "DK",
  "ipCountry": "AU",
  "ipCountryName": "Australia",
  "ipContinent": "Oceania",
  "ipNetwork": "1.1.1.0/24",
  "ipOrg": "Cloudflare, Inc.",
  "countryMatch": false,
  "riskFlag": "COUNTRY_MISMATCH",
  "found": true,
  "dataAvailable": true,
  "ipLookupStatus": "success"
}

Non-success conditions are always emitted as explicit diagnostic rows so empty or blocked runs cannot look successful:

{
  "recordType": "diagnostic",
  "bin": "000000",
  "found": false,
  "dataAvailable": false,
  "diagnosticCode": "BIN_NOT_FOUND",
  "message": "No public BIN record was returned."
}

Tips and troubleshooting

Use public IPv4 or IPv6 values only. Private, internal, loopback, link-local, shared, multicast, and documentation ranges are rejected before any IP request. A full card number is never a valid BIN input. Duplicate pairs are processed once, and out-of-range controls fail validation rather than being silently changed. If a source returns a denial or rate-limit signal, the run stops and emits a diagnostic instead of retrying or bypassing the restriction.

Key-value store

Lookup and diagnostic rows are stored in the dataset. The OUTPUT key-value record stores the dataset ID, requested and emitted counts, truthful status and availability flags, timestamps, and the last diagnostic code when present.

FAQ, disclaimer, and support

Does this Actor use a browser?

No. The Actor uses one bounded direct structured-response path per public source; it does not force Chrome, Playwright, CAPTCHA solving, login, or alternate denial workarounds.

Does it process private card or IP data?

No full card numbers, credentials, protected tokens, or private/internal IPs should be submitted. The Actor only requests public BIN and public-IP enrichment.

Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

For feedback, use the Issues tab. For programmatic access, use the API tab.