The blocklist prevents Reachkit from sending emails to specific addresses or entire domains. Anything on your blocklist is automatically skipped during campaign sending.

Why Use the Blocklist?

A specific person asked not to be contacted
You want to avoid emailing competitors, partners, or existing customers across their whole company
You need to comply with an opt-out request outside the normal unsubscribe flow
You want to protect certain domains from receiving outreach

How It Works

The blocklist is workspace-wide, so it applies to all campaigns. When a campaign is about to send, it checks the blocklist first. If the recipient matches, the email is skipped.

You can block:

A specific email, like jane@acme.com
A whole domain, like acme.com. This also blocks every subdomain of acme.com, so anyone@mail.acme.com and anyone@sales.acme.com are both skipped.

Unrelated lookalike domains are not affected. Blocking acme.com does not block fakeacme.com.

Adding Entries

Go to Settings > Blocklist to manage your entries. You can add them in two ways:

Manual entry: paste emails or domains, one per line. Reachkit figures out which is which based on whether the line contains @.
Select from leads: search your existing leads and either block that one email or block the entire domain with one click.

Automatic Blocklisting

Reachkit can also add leads to the blocklist for you when they opt out, from Settings > Blocklist:

Unsubscribes (on by default): a lead who opts out of your outreach is blocked across all your campaigns, not just the one they replied to. This covers both the formal unsubscribe link (and the one-click header) and a reply that explicitly asks to be removed, like “unsubscribe” or “take me off your list”. The written-reply part is a checkbox under the Unsubscribes switch, on by default, and you can turn it off if you only want to act on link clicks.
Negative replies (off by default): a lead whose reply says they’re not interested. This relies on Reachkit reading the reply, so it’s opt-in. “Not now” and wrong-contact replies are left alone.

Automatic entries carry a source label (for example “Wrote unsubscribe”) and a lock icon while their setting is on. They stay in sync with the reply: if the lead’s situation changes (say you relabel their reply, or they reply again positively), Reachkit updates the blocklist for you. Because of that they’re locked while the setting is on, so a deletion wouldn’t stick.

Turning a setting off doesn’t remove anything it already added, those opt-outs stay blocked, so you never accidentally re-expose people who opted out. It just stops adding new ones and unlocks the existing entries, which you can then remove individually (or with “select all”) like any manual entry.

Removing Entries

Click a manual entry (or an unlocked automatic one) and Remove. The change takes effect immediately and that address (or domain) becomes eligible for campaign sends again. Automatic entries are locked (shown with a lock icon) while their setting is on; turn that setting off first to remove them.

Blocklist via API

On the Scale plan, you can manage your blocklist programmatically:

GET /api/v1/blocklist lists all entries
GET /api/v1/blocklist/check?email=... returns whether an email would be blocked (including domain matches)
POST /api/v1/blocklist adds entries. Two forms are supported:
- { "value": "acme.com" } for a single email or domain (kind is inferred from the value)
- { "entries": ["jane@acme.com", "acme.com"] } for bulk
DELETE /api/v1/blocklist/:id removes an entry

See the API Documentation article for full details.

Blocklist vs. Unsubscribe

These work together:

Manual blocklisting is controlled by you. You decide who to block, add or remove entries yourself, and they never change on their own.
Unsubscribes are initiated by the recipient, whether they click the unsubscribe link, use the one-click header, or reply asking to be removed. With automatic blocklisting on (the default), these are added to your blocklist for you so they’re skipped in every campaign, not just the one they replied to.

Both prevent future emails; one is your call, the other reflects the recipient’s.