Skip to content
Finowl

FINOWL INTELLIGENCE / EMAIL BREACHES

An email. Its known exposures.

Look up breach records connected to an email address. Give your security workflows more context, without mistaking a signal for the whole story.

Isometric email tile connected to known breach records.

HOW IT WORKS

One address in.
Exposure context out.

A single request returns what your workflow needs to decide what happens next.
STEP / 01

Send an address

Post a single email address to the Email Breaches endpoint, authenticated with your API key.

STEP / 02

Match known breaches

Finowl looks the address up against records of known, publicly reported data breaches.

STEP / 03

Get breach context

Receive a breached flag and the matching records, ready for your account security workflow.

SEE IT IN ACTION

From an address
to exposure context.

Finowl Intelligence

POST/v1/breaches/email

RequestcURL
curl https://api.finowl.co/v1/breaches/email \  -H "Authorization: Bearer $FINOWL_API_KEY" \  -H "Content-Type: application/json" \  --data '{    "email": "alex@example.com"  }'
ResponseJSON200 OK
{  "email": "alex@example.com",  "breached": false,  "breaches": []}

WHERE IT FITS

A useful signal,
at the right moment.

  • Account reviews

    Add known email exposure to the context you review when assessing account security.

  • Security notifications

    Use breach records to inform relevant notifications and recommend an account review.

  • Sign-in context

    Bring an exposure signal into your sign-in workflow alongside your existing security checks.

Use exposure data responsibly. A breach match should inform a proportionate response, not automatically label someone as unsafe.

THE RESPONSE

Clear fields. Honest limits.

Every response tells you whether known exposures were found, together with the matching breach records.

Keep those records in context: exposure is a reason to review account security, not proof of present-day compromise.

email
The address associated with this check.
breached
Whether a matching known exposure was found.
breaches
The matching records. An empty list is not a guarantee that no exposure has ever occurred.

A FEW GOOD QUESTIONS

Email breach questions, answered.

Put email exposure in context.

Bring known breach records into your next account-security workflow.