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

# 泄露与密码 OSINT

用于检查暴露凭据、数据泄露、泄露密码、密码强度和哈希破解资源的 OSINT 笔记。

凭据泄露分析有助于识别可能影响目标组织的泄露电子邮件、重复使用的密码、遭入侵的账户、哈希值和密码模式。

## 安全密码：

密码强度、哈希查询、破解和字典列表工具集中在 [凭据和密码工具](/zh/hacking-tools/credentials.md)。请将此页面用于调查工作流程，并将“黑客工具”中心用于维护的工具目录。

## 泄露的电子邮件地址：

集中式泄露和暴露工具列在 [人员与泄露研究](/zh/hacking-tools/osint/people-and-breach-research.md)。请将此页面用于方法说明，并将“黑客工具”中心用于维护的外部资源列表。

## 泄露的密码：

人员查询和泄露研究工具集中在 [人员与泄露研究](/zh/hacking-tools/osint/people-and-breach-research.md).

## 破解密码：

哈希查询和破解工具列在 [凭据和密码工具](/zh/hacking-tools/credentials.md).

## 大型密码字典

字典列表资源列在 [凭据和密码工具](/zh/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/zh/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.