Skip to content
LeakRadar
HomeFeaturesSolutionsIndustriesPricingLiveFAQ
For SOC and response teams

A leak alert arrived. Find what needs a closer look.

Investigate reported credential exposure, identify the associated accounts and services, and prepare findings for the team handling the response.

Examine an exposureSee how it works

Create a free account to start investigating.

LeakRadarExample
  1. 01

    Exposed account reported

    alex@example.com

  2. 02

    Examine the service and context

    login.example.net

  3. 03

    Prepare the response

    Hand off to the security team

Illustration with fictional data.
The data behind LeakRadar

Investigate the exposed records, with the data to act.

639,837,032,019lines 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

The alert rarely tells the whole story.

An exposed address may relate to a historical record, a third-party service or an account that has changed. Investigate the available context before deciding how it relates to the event your team is handling.

Connect the leak record to your own evidence.

Your workflow

From an alert to an informed handoff

  1. 01

    Start with the indicator

    Sign in and search the email or domain from the alert using the appropriate mode.

  2. 02

    Establish the context

    Examine the service, source and available dates. Compare the findings with your organization's own records.

  3. 03

    Prepare the follow-up

    Export useful material, pass it to the response team and configure monitoring where continued visibility is needed.

LeakRadar

What you can work with

Access that fits your work

Start with a free account, then choose the plan that fits your datasets, monitoring, exports and team.

Compare plans

Targeted investigation

Move from a reported address or domain to the matching records available in LeakRadar.

Evidence for responders

Use exports and domain reports to support investigation notes and communication with the responsible team.

Monitoring after review

Keep relevant domains or addresses under observation after the initial investigation.

Incident investigation

Before you get started

Does LeakRadar reset passwords or revoke sessions?

No. Your team applies account and device remediation in its own systems. LeakRadar supplies data to support those decisions.

Does a newly found record mean a new compromise?

Not necessarily. Discovery or indexing time is not the time of compromise. Compare the available source context with your own logs.

Security research

Search leak data by email, domain or advanced criteria. Examine the available context, save useful searches and export findings for your analysis.

Domain monitoring

Monitor your corporate domains, examine exposed accounts and third-party services, and give your security team a clear starting point for investigation.