> 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/people-and-breach-research.md). # People and Breach Research People and breach research resources for responsible email, phone, name, username, credential exposure, and breach-intelligence workflows. Use these resources to investigate public identity signals, breached data exposure, emails, phone numbers, names, usernames, and account traces in a responsible and authorized manner. ## Name, Email, and Phone Research

Name	Description	Official Link	Cover image
Bellingcat Name Variant Search	Generate and search variants of a person's name across Google queries.	https://bellingcat.github.io/name-variant-search/	image.png
Aware Online OSINT	Public OSINT people-search resource collection for identity and account research.	https://www.aware-online.com/en/osint-tools/people-search-tool/	image.png
theHarvester	Collects emails, hosts, and public OSINT data from search engines and public sources.	https://github.com/laramies/theHarvester	image.png
Hunter.io	Email discovery and verification platform for finding addresses associated with a domain.	https://hunter.io/	image.png
Hunter Email Verifier	Email verification tool for checking whether an address appears valid and active.	https://hunter.io/email-verifier	image.png
Email-checker	Online email validation service for checking whether an address appears syntactically and operationally valid.	https://email-checker.net/	image.png
Phonebook.cz	Search public domains, subdomains, URLs, and email-related records from indexed public sources.	https://phonebook.cz/	image.png
Temp-Mail	Temporary email service for receiving disposable messages during safe testing workflows.	https://temp-mail.org/	image.png
Epieos	Checks where an email address may have been used, based on Holehe-style account discovery techniques.	https://epieos.com/	image.png
GetContact	Crowdsourced phone-number identification platform based on contact-book data.	https://getcontact.com/en/	image.png
NeutrOSINT	Tool for investigating Proton Mail addresses.	https://github.com/Kr0wZ/NeutrOSINT	image.png

## Breach and Exposure Intelligence

Name	Description	Official Link	Cover image
Have I Been Pwned	Check whether an email address appears in known public data breaches.	https://haveibeenpwned.com/	image.png
IntelX	Search public and indexed datasets for breach, credential, domain, and intelligence artifacts.	https://intelx.io/	image.png
DeHashed	Search compromised credentials, leaked records, and domain-related exposure data.	https://dehashed.com/	image.png
Leak-Lookup	Search public breach datasets for exposed credentials and compromised records.	https://leak-lookup.com/	image.png

--- # 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/people-and-breach-research.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.