Credential Breach Checker

Credential Breach Checker enables you to query comprehensive breach and leak intelligence sources powered by the IRBIS API. For each identifier you submit—whether an email address, phone number, password, full name, or social media ID—the actor checks against an extensive database of known data leaks and credential exposures.

What does Credential Breach Checker do?

Credential Breach Checker can check:

• Email addresses
• Phone numbers
• Passwords
• Full names
• Telegram IDs
• LinkedIn IDs
• Instagram IDs
• Twitter IDs
• Facebook IDs
• VK IDs

For each value, you receive the full breach record including breach source names, leaked data fields (passwords, usernames, IPs, etc.), breach dates, and data categories found.

Why use Credential Breach Checker?

Data breaches and credential leaks are a persistent security threat. Credential Breach Checker gives security teams, compliance professionals, and investigators on-demand access to breach intelligence without building or maintaining their own data pipeline.

Use cases include:

• Security reviews and KYC workflows — Verify customer identities during onboarding and ongoing compliance reviews
• Fraud prevention — Detect compromised credentials before they're exploited
• Identity verification — Confirm that personal information hasn't been exposed in known breaches
• Investigative research — Track credential exposure patterns during security investigations
• Corporate due diligence — Screen employee and business partner identities for breach exposure
• OSINT investigations — Gather breach intelligence for threat research and intelligence work

How to use Credential Breach Checker

1. Click on Try for free.
2. Select your lookup type from the available options (email, phone, password, full name, or social media ID).
3. Enter one or more values to scan (up to 25 values per run).
4. Click on Run.
5. When Credential Breach Checker has finished, preview or download your breach records from the Dataset tab.

Input configuration

Lookup Type	Description	Format Requirements
email	Email addresses	Must match user@domain.tld format
phone	Phone numbers	Numeric format with country code (e.g. +13469042690)
password	Passwords	Any string value
fullname	Full names	Letters and spaces only, up to 5 words
telegramid	Telegram IDs	Numeric only (no @usernames)
linkedinid	LinkedIn profile IDs	Alphanumeric slug (e.g. anand-dubey-b8902463)
instagramid	Instagram usernames	Without @ symbol
twitterid	Twitter handles	Without @ symbol
facebookid	Facebook profile IDs	Numeric
vkid	VK (VKontakte) IDs	Numeric

You can submit up to 25 values per run. Each value is validated before scanning — invalid formats return a validation_error status and are not charged.

Output format

Results are stored in the actor's dataset. Each item represents one scanned value:

{
  "input": "foxproject@bk.ru",
  "lookupType": "email",
  "status": "success",
  "irbisResponseId": "abc123",
  "pollAttempts": 3,
  "result": {
    "breaches_found": 4,
    "breach_records": [
      {
        "source": "ExampleBreach2021",
        "breach_date": "2021-03-15",
        "leaked_fields": ["email", "password", "username", "ip_address"],
        "data_categories": ["credentials", "personal_info"]
      }
    ]
  }
}

Status values:

• success — breach data retrieved
• no_results — no breaches found for this identifier
• validation_error — input did not pass format validation
• timeout — backend did not respond in time
• error — unexpected error during lookup

How much will it cost?

Credential Breach Checker uses Pay-Per-Event pricing at $0.40 per successful breach scan result. You are only charged for values that return a result — validation failures and no-result lookups are free.

Apify platform costs are minimal (typically under $0.01 per run for compute).

Estimated monthly volume by plan:

• Starter plan ($49/month) → ~122 successful scans/month
• Scale plan ($499/month) → ~1,247 successful scans/month

Tips for using Credential Breach Checker

• Batch your lookups — Submit up to 25 values per run to minimize platform overhead.
• Validate inputs before submitting — Use the correct format for each lookup type to avoid wasted runs.
• Check the status field — Only success results are charged; inspect validation_error items to fix input formatting.
• Use for legitimate purposes only — This actor is intended for security research, compliance, and fraud prevention. Do not use it to access data on individuals without legal authorization.