> For the complete documentation index, see [llms.txt](https://www.pentest-book.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pentest-book.com/readme.md).

# /home/six2dez/.pentest-book

This book contains a bunch of info, scripts and knowledge used during my pentests.

Thanks to visit this site, please consider enhance this book with some awesome tools or techniques you know, you can contact me by Telegram([@six2dez](https://t.me/six2dez)), Twitter([@six2dez1](https://twitter.com/Six2dez1)) or Discord([six2dez#8201](https://discordapp.com/users/six2dez#8201)), GitHub pull request is welcomed too ;) **Hack 'em all**

### **Usage: Just use the search bar at the upper or navigate through the sections of the left zone. Enjoy it** :blush: 

**Don't you know where to go now?** Let me introduce you to some of the most **popular pages** on this wiki:

* Know your target! Make a proper [recon](/recon/public-info-gathering.md)!
* What can you do in those strange [ports](/enumeration/ports.md)?
* Doing a [web pentest](/enumeration/web.md)? Don't forget to check out any of these common attacks!
* Do you have the same hype as me with [cloud ](/enumeration/cloud.md)services? They also have their vulnerabilities
* Stuck again with Windows and [Kerberos](/post-exploitation/windows/ad/kerberos-attacks.md)? Here is my cheatsheet
* The mobile world does not stop growing, see my tips for [Android ](/mobile/android.md)and [iOS](/mobile/ios.md)
* [Burp Suite ](/others/burp.md)is the tool most loved by everyone, but you have to know a few tricks, also check my [preferred extensions](/others/burp.md#preferred-extensions)
* I'm really proud of [Pentesting Web Checklist](/others/web-checklist.md)
* If you want to know which web fuzzer fits you best, take a look at the [comparison](/others/web-fuzzers-comparision.md).

**Important note**: I use this wiki daily for my work and I am constantly updating it. I'm very sorry if a link to a page changes or I move it, if you need something you are free to contact me.

You can support this work buying me a coffee: 

{% embed url="<https://www.buymeacoffee.com/six2dez>" %}

### Stargazers over time

![Stargazers over time](https://starchart.cc/six2dez/pentest-book.svg)


---

# 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://www.pentest-book.com/readme.md?ask=<question>&goal=<user_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.