> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/zh/hacking-tools/osint/osint-methodology/email-osint.md).

# 电子邮件 OSINT

在侦察过程中查找、验证并关联与域或组织相关的电子邮件地址的 OSINT 技术。

电子邮件 OSINT 有助于识别有效地址、命名模式、员工账户、暴露的收件箱，以及用于密码喷洒或钓鱼模拟的潜在用户名。

## 电子邮件地址的位置：

{% hint style="info" %}
在进行安全调查或 OSINT 收集时，定位与特定域相关的电子邮件地址很有用。这有助于识别员工、账户命名模式、暴露的收件箱以及可能的用户名。用于电子邮件、人员和泄露研究的维护工具目录可在以下位置获取 [人员与泄露研究](/zh/hacking-tools/osint/people-and-breach-research.md).
{% endhint %}

在收集电子邮件地址时，请记录：

* 每个地址的发现来源。
* 组织使用的电子邮件格式。
* 该地址看起来是当前的、历史的、个人的还是基于角色的。
* 任何置信度或验证状态。

## 检查电子邮件是否存在：

{% hint style="info" %}
在将收集到的电子邮件地址用于任何授权测试操作之前，确认它们是否有效非常重要。电子邮件验证工具列于 [人员与泄露研究](/zh/hacking-tools/osint/people-and-breach-research.md).
{% endhint %}

## 创建临时电子邮件地址：

{% hint style="info" %}
在某些情况下，临时电子邮件地址可用于安全的注册测试或受控的账户验证。一次性电子邮件资源列于 [人员与泄露研究](/zh/hacking-tools/osint/people-and-breach-research.md).
{% endhint %}


---

# 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://hacking-notes.jord4n.pro/zh/hacking-tools/osint/osint-methodology/email-osint.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.