> 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/exploitation/bug-bounty-and-research-resources.md). # Bug Bounty and Research Resources Bug bounty and security research resources for public writeups, vulnerability databases, exploit references, methodology notes, and payload research. Use these resources for vulnerability research, public writeups, exploit references, and methodology inspiration. Keep technical proof steps in the relevant vulnerability or writeup pages. ## Resources

Name	Description	Official link	Cover image
Pentester Land	Public bug bounty writeups and security research references.	https://pentester.land/	image.png
Rapid7 Vulnerability Database	Search CVEs, vulnerability details, exploit references, and Metasploit module context.	https://www.rapid7.com/db/	Screenshot 2026-07-20 155200.png
Exploit-DB	Browse public exploits, proof-of-concept code, papers, and Google Hacking Database references.	https://www.exploit-db.com/	Screenshot 2026-07-20 155602.png
HackTricks	Use playbooks and attack paths across technologies and environments.	https://book.hacktricks.xyz/	Screenshot 2026-07-20 155648.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/exploitation/bug-bounty-and-research-resources.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.