> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leakcheck.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts & contacts

> Where breach-monitoring alerts go — Telegram, e-mail, extra addresses, Slack, Discord and your own webhooks — and how to set each one up.

Breach monitoring watches the identifiers you add on the
[Breach monitoring page](https://leakcheck.io/notify) — e-mail addresses,
usernames, phone numbers and, on Enterprise, whole company domains — and sends an
**alert** whenever new records for them are added to LeakCheck. This page is about
where those alerts go.

> [!NOTE]
>
> Monitoring is part of the paid plans (25 monitors on Monthly, 50 on Lifetime,
> 1,000 on Enterprise). It is managed in the dashboard — there is no API for it.

## The contact list

Open the **Alerts** dialog on the Breach monitoring page. Every entry in the list
is a destination, and **every destination gets every alert**:

| Contact | What it is |
| - | - |
| Telegram (account) | The Telegram account linked to your LeakCheck account through [our bot](https://leakcheck.io/telegram-bot). |
| E-mail (account) | Your account's verified e-mail address. |
| E-mail (extra) | Any other address — a colleague, a shared security mailbox, a SIEM inbox. |
| Slack | A channel, through a Slack incoming webhook. |
| Discord | A channel, through a Discord webhook. |
| Webhook | Your own HTTPS endpoint, receiving a signed JSON payload — see [Webhooks](/monitoring/webhooks). |

The two account rows have an on/off switch each. Extra contacts (e-mail, Slack,
Discord, webhook together) are limited to **5** per account, **20** on Enterprise.

If Telegram is switched on and e-mail is off, an alert that Telegram refuses (for
example, you blocked the bot) is sent to your account e-mail instead, so it is not
lost. Any contact can be switched off without removing it.

## Extra e-mail addresses

An address you add gets a **confirmation e-mail** first and receives alerts only
after its link has been opened — so nobody can point alerts at a mailbox that did
not ask for them. Until then the contact shows *Awaiting confirmation*; you can
send the link again from the list.

* The link is valid for 24 hours.
* Confirmation e-mails are limited: 5 per hour per account, and 3 per day to any
  one address, whoever adds it.
* Your own account address cannot be added — switch it on in the list instead.
* Every alert sent to an extra address ends with a **Stop these alerts** link
  that removes the contact, no login needed.

## Slack

Alerts are posted to a channel through a Slack *incoming webhook*:

1. Open [api.slack.com/apps](https://api.slack.com/apps) → **Create New App** →
   **From scratch**, and pick your workspace.
2. In the app, open **Features → Incoming Webhooks**, switch them on, then
   **Add New Webhook to Workspace** and choose the channel.
3. Copy the webhook URL (it starts with `https://hooks.slack.com/services/`) and
   paste it into the **Slack** form of the Alerts dialog, with a name for the contact.

The message uses Slack's Block Kit: a header, the monitored value, the list of
sources with the kinds of data they expose, and a button to the dashboard.

## Discord

1. In Discord, open the channel's settings (the gear) → **Integrations → Webhooks**.
2. **New Webhook** → **Copy Webhook URL**.
3. Paste it into the **Discord** form of the Alerts dialog.

The alert arrives as an embed. `@everyone`, `@here` and role or user mentions
that appear in leaked data never ping anyone.

## What an alert contains

An alert names the **monitored value**, the **sources** the new records come from
and the **kinds of data** each source exposes (for example `email, password`). It
never contains the leaked values themselves — passwords and other data stay in the
dashboard, behind the button in every alert.

A **domain monitor** (Enterprise) alert also carries totals: how many new records
there are, how many accounts are affected, how many of the records belong to the
domain's own e-mail accounts and how many are info-stealer log-ins to the
company's sites, plus the most affected accounts.

## When your plan ends

Monitors are not removed when a plan ends, and they keep being checked. What
changes is the alert: without a plan that includes monitoring it only says that
new records were found for the monitored value — no sources, no kinds of data —
with a link to renew. It goes to your account's Telegram / e-mail only; extra
contacts (addresses, Slack, Discord, webhooks) pause until the plan is renewed,
and so do the details. New contacts cannot be added without a plan.

## Testing a contact

Every Slack, Discord and webhook contact has a **Send test** action that delivers
a sample alert (marked as a test) right away, so you can check the channel,
the formatting or your endpoint without waiting for a real leak.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.