> 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/leak-and-password-osint.md).

# Leak and Password OSINT

OSINT notes for checking exposed credentials, data breaches, leaked passwords, password strength, and hash cracking resources.

Credential leak analysis helps identify exposed emails, reused passwords, breached accounts, hashes, and password patterns that may affect the target organization.

## Secure passwords:

Password strength, hash lookup, cracking, and wordlist tools are centralized in [Credential and Password Tools](/hacking-tools/credentials.md). Use this page for the investigation workflow and the Hacking Tools hub for the maintained tool catalog.

## Exposed email addresses:

Centralized breach and exposure tools are listed in [People and Breach Research](/hacking-tools/osint/people-and-breach-research.md). Use this page for methodology notes and the Hacking Tools hub for the maintained external resource list.

## Exposed passwords:

People lookup and breach research tools are centralized in [People and Breach Research](/hacking-tools/osint/people-and-breach-research.md).

## Crack passwords:

Hash lookup and cracking tools are listed in [Credential and Password Tools](/hacking-tools/credentials.md).

## Large password dictionaries

Wordlist resources are listed in [Credential and Password Tools](/hacking-tools/credentials.md).


---

# 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/leak-and-password-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.