Skip to content

Give identity exposure a place in your fraud review.

Review employee and customer-facing service matches linked to your domains. Supply your security and fraud teams with account context to investigate.

Create a free account to start investigating.

An example review scopeexample.com
  1. Staff access

    staff.example.com
  2. Customer-facing portals

    portal.example.com
  3. Partner platforms

    payments.example.net
Illustration with fictional data.
The data behind LeakRadar

See which accounts and services are exposed in your sector.

644,961,994,529lines across indexed leak files

File lines, not a count of unique accounts.

Updated

Plaintext passwords, with their account context

Inspect the exposed password alongside the account and, for stealer logs, its service URL. When the source includes plaintext, that detail helps your team scope password resets and investigate exposed access.

Compare plans for plaintext access and included unlock points.

  • Stealer logs

    Connect a captured login to its service URL, username and password to understand which access is exposed.

    url:user:pass
  • Combolists

    Find email/password and username/password pairs, including records without a service URL.

    email:passuser:pass
  • Raw leak files

    Search the text of leaked files, database dumps and unstructured records beyond normalized credential fields.

  • Dark web forums

    Search indexed forum posts for mentions of your organization and examine the discussion's source context.

Get notified via Email, Slack, Discord, Telegram or Webhook when new exposed credentials match your monitored domains or email addresses.

Explore our data coverage
The situation

An exposed account is a lead to assess.

A record mentions a banking portal or a staff address. Separate those situations before escalating: your own account and transaction records establish who is affected and whether suspicious activity occurred.

Where to focus your review

  1. Staff access

    Review company addresses used on internal or external services, with attention to privileged roles confirmed in your directory.

  2. Customer-facing portals

    Examine records associated with your service domains and route relevant findings to the account protection team.

  3. Partner platforms

    Investigate employee accounts used on external financial tools. A match is not a security assessment of the provider.

Your workflow

From exposure to an assigned follow-up

  1. Search your domain

    Sign in and review the employee, third-party and customer categories. Compare matches with the accounts and services you actually use.

  2. Set up monitoring

    Get notified via Email, Slack, Discord, Telegram or Webhook when new exposed credentials match your monitored domains or email addresses.

  3. Document and follow up

    Use the domain PDF report for an overview and available exports for relevant records. Your team handles account checks and remediation in its own systems.

Before you get started

Does LeakRadar detect fraudulent transactions?

No. It provides credential exposure data. Transaction analysis and decisions remain in your fraud and banking systems.

Does monitoring establish regulatory compliance?

No. Reports can inform an internal review, but do not certify compliance or replace your control assessment.