# Wordlists

To conduct brute force and dictionary attacks, you can generate your own customized wordlists or use pre-compiled wordlists from the internet.

## Crunch <a href="#crunch" id="crunch"></a>

Crunch generates a custom password lists that can be used to guess passwords. These include:

```
crunch [min length] [max length] [charset] [options]​crunch 4 4 ABCDEFGHIJKLMNOPQRSTUVWXYZ -o /root/Desktop/wordlist.txt​crunch 5 5 0123456789 -o /root/Desktop/wordlist.txt​crunch 8 8 ABCDEFGHIJKLMNOPQRSTUVWXYZ -t @@@@1980 -o /root/Desktop/wordlist.txt​crunch 1 2 -p Dog Cat Mouse -o /root/Desktop/wordlist.txt
```

## CeWL <a href="#cewl" id="cewl"></a>

CeWL is a ruby app which spiders a given URL to a specified depth, optionally following external links, and returns a list of words which can then be used for password crackers such as John the Ripper.

```
cewl -d $pagedepth -m $minlength -w cewl.txt https://$TARGET
```

## SecLists <a href="#seclists" id="seclists"></a>

SecLists is the security tester's companion. It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells, and many more.

![](https://gblobscdn.gitbook.com/assets%2F-Lp8k2kJfQCMSNQRgFQf%2F-LpT4NK6HweEu8beEd23%2F-LpT5bFdhlDsikTwsOnX%2Fimage.png?alt=media\&token=a68484fb-b96d-43c9-a858-935fa124fc4e)

<https://github.com/danielmiessler/SecLists>


---

# 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://rabakuku.gitbook.io/oscp/password-attack-1/wordlist.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.