> 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/de/hacking-tools/exploitation/bug-bounty-and-research-resources.md). # Ressourcen für Bug-Bounty und Forschung Ressourcen für Bug-Bounty- und Sicherheitsforschung zu öffentlichen Write-ups, Schwachstellendatenbanken, Exploit-Referenzen, Methodiknotizen und Payload-Recherche. Nutze diese Ressourcen für Schwachstellenforschung, öffentliche Writeups, Exploit-Referenzen und methodische Inspiration. Halte technische Nachweisschritte auf den relevanten Schwachstellen- oder Writeup-Seiten fest. ## Ressourcen
NameBeschreibungOffizieller LinkTitelbild
Pentester LandÖffentliche Bug-Bounty-Writeups und Referenzen zur Sicherheitsforschung.https://pentester.land/image.png
Rapid7-SchwachstellendatenbankSuche nach CVEs, Schwachstellendetails, Exploit-Referenzen und Metasploit-Modulkontext.https://www.rapid7.com/db/Screenshot 2026-07-20 155200.png
Exploit-DBDurchsuche öffentliche Exploits, Proof-of-Concept-Code, Papers und Referenzen zur Google Hacking Database.https://www.exploit-db.com/Screenshot 2026-07-20 155602.png
HackTricksNutze Playbooks und Angriffspfade über Technologien und Umgebungen hinweg.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/de/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.