# Automated Scanners

[**Kn0ck**](https://github.com/telnet22/Kn0ck)**:** Kn0ck is an automated scanner that can be used during a penetration testing to enumerate and scan for vulnerabilities.

&#x20;[**yasuo**](https://github.com/0xsauby/yasuo)**:** A ruby script that scans for vulnerable & exploitable 3rd-party web applications on a network.

![](/files/-MX4VKr7tCwRWrM1KHx7)

&#x20;[**jok3r**](https://github.com/koutto/jok3r)**:** Jok3r v3 BETA 2 - Network and Web Pentest Automation Framework.

{% embed url="<https://youtu.be/z4cf_8EQ59Q>" %}

## osmedeus

{% embed url="<https://github.com/j3ssie/osmedeus>" %}

## Sn1per

{% embed url="<https://github.com/1N3/Sn1per>" %}

Exegol: Multiple containers for pentesting

{% embed url="<https://github.com/ThePorgs/Exegol?tab=readme-ov-file>" %}

## bbot

{% embed url="<https://github.com/blacklanternsecurity/bbot>" %}

```
bbot -t evilcorp.com -p subdomain-enum
```

## ReconFTW

{% embed url="<https://github.com/six2dez/reconftw>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook.seguranca-informatica.pt/tools/infrastructure-and-network/automated-scanners.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
