> 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/hacking-tools/osint/osint-methodology/email-osint.md).

# Email OSINT

OSINT techniques for finding, validating, and correlating email addresses linked to a domain or organization during reconnaissance.

Email OSINT, helps identify valid addresses, naming patterns, employee accounts, exposed inboxes, and potential usernames for password spraying or phishing simulations.

## Location of email addresses:

{% hint style="info" %}
When conducting a security investigation or OSINT collection, it is useful to locate email addresses associated with a specific domain. This can help identify employees, account naming patterns, exposed inboxes, and likely usernames. The maintained tool catalog for email, people, and breach research is available in [People and Breach Research](/hacking-tools/osint/people-and-breach-research.md).
{% endhint %}

When collecting email addresses, document:

* The source where each address was found.
* The email format used by the organization.
* Whether the address appears current, historical, personal, or role-based.
* Any confidence level or validation status.

## Checking the Existence of Emails:

{% hint style="info" %}
It is important to confirm whether collected email addresses are valid before using them in any authorized testing action. Email verification tools are listed in [People and Breach Research](/hacking-tools/osint/people-and-breach-research.md).
{% endhint %}

## Creating temporary email addresses:

{% hint style="info" %}
In some cases, temporary email addresses are useful for safe registration testing or controlled account verification. Disposable email resources are listed in [People and Breach Research](/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/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.