> 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/zh/what-would-you-like-to-learn-about/advocate-program/protect-your-advocate-program/block-an-email-domain-for-advocate.md).
# 为 Advocate 屏蔽电子邮件域名
您的 Advocate 计划支持标记使用可疑域名邮箱地址注册的参与者。
我们会将推荐与一个公开来源且定期更新的 [列表](https://github.com/martenson/disposable-email-domains) 进行比对，该列表包含一次性和临时电子邮件域名。您也可以创建自己的自定义电子邮件域名屏蔽列表。
#### 创建自定义域名屏蔽列表
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在……下 *Advocate 设置*，选择 **安全**.
3. 在……下 *屏蔽电子邮件域名*，输入要屏蔽的域名，并选择 **添加**.
* 您可以在以下位置查看或移除该域名 *被屏蔽域名列表*.
4. 可选地，  **\[开启]** **屏蔽临时电子邮件地址** 以屏蔽所有使用临时电子邮件域名的用户。
5. 向下滚动到底部并选择 **保存**.
---
# 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/zh/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.
