> 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/neutrosint.md). # NeutrOSINT Check if an email address or username exists on ProtonMail. ## Source * Repository: * License: MIT ## Install ```bash otinstaller install neutrosint ``` otinstaller clones `https://github.com/Kr0wZ/NeutrOSINT.git` at ref `a51a133444c366ea3a60a8c400a3624625d79e6d` into a dedicated virtualenv, then installs the clone itself as a package. ## Credentials No API keys needed. ## Input types | Input | Typed input | Tool arguments | | ----------- | ----------------------- | ----------------------------- | | email (`e`) | `e:example@example.com` | `--email example@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 neutrosint: ------------------------------------------------------------ username and password not specified, using light mode... (NeutrOSINT banner omitted) [-] Proton email does not exist: doesnotexist9k2x@example.com [+] Valid email: exampleuser@proton.me - PGP key creation date: 2021-03-14T09:41:51+00:00 - Fingerprint: 1A2B3C4D5E6F7890ABCDEF1234567890ABCDEF12 - Algorithm: rsa3072 [?] Not a protonmail address, can't determine validity: someone@gmail.com [-] Error when requesting the API ------------------------------------------------------------ (Example trimmed - real output starts with an ASCII banner) ``` ## Run Plain arguments after `--` are passed to the tool unchanged: ```bash otinstaller run neutrosint -- --email example@example.com ``` Typed inputs are mapped to this tool's flags: ```bash otinstaller run neutrosint e:example@example.com ``` Results are saved to `./results/neutrosint//`. --- # 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/neutrosint.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.