> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/email-security/blocklist.md).

# Blocklist

Block a sender or a whole domain yourself, without contacting us. Use it when a sender keeps sending unwanted emails, or to stop all emails from a domain, whatever the sender.

## Add a rule

1. In Stoïk Protect, go to `Suspicious emails` > `Settings` and open the `Blocklist` tab.
2. Click `+ Add`.
3. Choose what to block: a `Sender` or a `Domain`, and enter it.
4. Pick the tenants where the rule applies.
5. Optionally, add a note to remember why you blocked it.
6. Save the rule.

The rule applies only to the tenants you selected.

## What happens to a blocked email

* It goes to quarantine, with a generic suspicious banner added to it.
* No alert is raised in Stoïk Protect.

## Edit or delete a rule

Edit or delete a rule at any time from the `Blocklist` tab. Each rule shows the tenants it applies to and, if you added one, the note explaining why it exists.

If an email you expected to be blocked still reaches your inbox, write to us at <protect@stoik.io>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/email-security/blocklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
