> For the complete documentation index, see [llms.txt](https://osintverse.gitbook.io/otinstaller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://osintverse.gitbook.io/otinstaller/tools/theharvester.md). # theHarvester Find emails, subdomains and names for a domain ## Source * Repository: * License: not stated ## Install ```bash otinstaller install theharvester ``` otinstaller clones `https://github.com/laramies/theHarvester.git` at ref `fd832dee7936458a4f6e2029bf37ba6797228676` into a dedicated virtualenv, then installs the clone itself as a package. ## Credentials Optional keys: `SHODAN_API_KEY`, `HUNTER_API_KEY`. Keys are stored in `~/.otinstaller/.env`, one `KEY=value` per line. This tool only receives the keys listed above. ## Input types | Input | Typed input | Tool arguments | | ------------ | --------------- | ---------------------- | | domain (`d`) | `d:example.com` | `--domain example.com` | ## Example output Illustrative output showing the general shape of a run. Real output depends on the tool version and the target. ``` example output for theharvester: ------------------------------------------------------------ [*] Target: example.com [*] Searching sources: google, bing, bingapi, duckduckgo, yahoo, duckduckgohtml, dogpile, twitter, linkedin, github, crtsh, certspotter, threatcrowd, virustotal, threatminer, otx, alienvault, rapiddns, sublist3r, bufferover, hackertarget, anubis, amass, dnsdumpster, urlscan, netcraft, wayback, commoncrawl, robtex, securitytrails, censys, certspotter, fofa, hunter, zoomeye, shodan, censys, binaryedge, greynoise, passive [*] Emails found (12): admin@example.com contact@example.com support@example.com info@example.com sales@example.com marketing@example.com hr@example.com jobs@example.com security@example.com abuse@example.com webmaster@example.com postmaster@example.com [*] Hosts found (24): example.com www.example.com mail.example.com ftp.example.com smtp.example.com pop.example.com imap.example.com webmail.example.com vpn.example.com remote.example.com dev.example.com staging.example.com test.example.com api.example.com blog.example.com shop.example.com docs.example.com help.example.com forum.example.com community.example.com status.example.com cdn.example.com static.example.com assets.example.com [*] IPs found (8): 192.0.2.1 192.0.2.2 192.0.2.3 198.51.100.1 198.51.100.2 198.51.100.3 203.0.113.1 203.0.113.2 [*] ASNs found (3): AS15169 (Google LLC) AS13335 (Cloudflare, Inc.) AS16509 (Amazon.com, Inc.) ------------------------------------------------------------ (Example truncated - real output contains more emails, hosts, and IPs) ``` ## Run Plain arguments after `--` are passed to the tool unchanged: ```bash otinstaller run theharvester -- --domain example.com ``` Typed inputs are mapped to this tool's flags: ```bash otinstaller run theharvester d:example.com ``` Results are saved to `./results/theharvester//`. --- # 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://osintverse.gitbook.io/otinstaller/tools/theharvester.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.