> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/protect-your-advocate-program/block-an-email-domain-for-advocate.md).
# Block an Email Domain for Advocate
Your Advocate program supports flagging participants who have signed up with an email address from a suspicious domain.
We check referrals against a publicly-sourced and regularly updated [list](https://github.com/martenson/disposable-email-domains) of disposable and temporary email domains. You can also create your own custom email domain block list.
#### Create a custom domain block list
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. Under *Advocate Settings*, select **Security**.
3. Under *Block Email Domains*, enter the domain/s you want to block and select **Add**.
* You can view or remove the domain under *List of Blocked Domains*.
4. Optionally,  **\[Toggle on]** **Block temporary email addresses** to block all users using a temporary email domain.
5. Scroll down to the bottom and select **Save**.
---
# 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://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/protect-your-advocate-program/block-an-email-domain-for-advocate.md?ask=&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.
