> 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/ja/hacking-tools/osint/osint-methodology.md). # OSINT 手法 調査中に公開情報、メール、漏洩情報、メタデータ、電話番号、ID の痕跡を収集するための OSINT 手法。 OSINTは、ユーザー、ドメイン、認証情報、公開ファイル、メタデータ、外部攻撃対象領域を明らかにし得る公開情報を収集することで、偵察を支援します。 OSINTの主要な対象には、メールアドレス、漏えいした認証情報、パスワード漏えい、EXIFメタデータ、電話番号、公開プロフィール、インフラストラクチャ参照が含まれます。

:envelope-open:

メールOSINT

組織やドメインに関連付けられたメールアドレスの検索、検証、相関分析。メール OSINT

:unlock-keyhole:

漏えい情報とパスワードのOSINT

データ漏えい、流出したパスワード、侵害された認証情報に関連するリスクの分析。漏洩とパスワードの OSINT

:image:

メタデータOSINT

EXIFメタデータを抽出・分析して、隠された機密情報を特定する。メタデータ OSINT

:mobile-screen-button:

電話OSINT

電話番号の調査、キャリア、形式、一時番号、関連する公開痕跡。電話 OSINT
--- # 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/ja/hacking-tools/osint/osint-methodology.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.