Gobuster and ffuf on Parrot Linux: Directory Enumeration in Your Lab

Directory and content discovery is one of the first things you do after mapping a target in your lab. On Parrot Linux, two tools dominate this job: Gobuster and ffuf. Both brute-force hidden paths, files, and virtual hosts against a web server, but they take different approaches to speed, filtering, and output. This guide walks you through installing and using gobuster on Parrot Linux alongside ffuf, so you can enumerate directories confidently and read the results without drowning in noise.

Before anything else: run these tools only against systems you own or are explicitly authorised to test. That means your own lab targets — DVWA, a local web app, or a Hack The Box / TryHackMe machine you have started. Hammering a third-party website with a wordlist is both noisy and, in most places, illegal.

Why directory enumeration matters

Web applications rarely link to every page they host. Admin panels, backup files, old test scripts, and API endpoints often sit at predictable paths with no link pointing to them. Directory enumeration throws a list of common names at the server and watches the HTTP status codes that come back. A 200 or a 301 on /admin tells you something is there, even though nothing on the homepage ever mentioned it.

This is the same reflex you use with a port scanner. If you have not set up a safe practice environment yet, read our walkthrough on how to build a home pentesting lab with Parrot Linux first, then come back here to point these tools at it.

Installing Gobuster and ffuf on Parrot Linux

Parrot Linux ships with a large toolset in its Security edition, but the versions in the repositories can lag behind upstream. Start by updating your package lists, then install both tools:

sudo apt update
sudo apt install gobuster ffuf

Confirm they are present and check their versions:

gobuster version
ffuf -V

If you want the newest build — which sometimes matters for ffuf, as it evolves quickly — you can install it with Go instead. Parrot is Debian-based, so the Go toolchain installs cleanly:

sudo apt install golang-go
go install github.com/ffuf/ffuf/v2@latest

Binaries installed this way land in ~/go/bin. Add that directory to your PATH if it is not already there, by appending this line to ~/.zshrc (Parrot uses Zsh by default):

export PATH="$PATH:$HOME/go/bin"

Open a new terminal, or run source ~/.zshrc, and the ffuf from Go will take priority.

Wordlists: the real engine

Neither tool is useful without a wordlist. Parrot bundles the SecLists collection and the classic dirb and dirbuster lists. Common starting points live under:

ls /usr/share/wordlists/
ls /usr/share/seclists/Discovery/Web-Content/

For a first pass, /usr/share/seclists/Discovery/Web-Content/common.txt is small and fast. When you want deeper coverage, step up to directory-list-2.3-medium.txt. Bigger lists find more but take far longer and generate far more requests, so match the list to your patience and the target.

Running Gobuster: directory mode

Gobuster’s most-used mode is dir, which brute-forces paths under a base URL. A basic run against a lab target looks like this:

gobuster dir -u http://10.10.10.10 -w /usr/share/seclists/Discovery/Web-Content/common.txt

Break down the flags you will reach for most:

  • -u — the target URL, including the scheme.
  • -w — the wordlist path.
  • -t — number of concurrent threads (default 10; raising it speeds things up but hits the server harder).
  • -x — file extensions to append, e.g. -x php,txt,bak to find login.php or config.bak.
  • -o — write results to a file.

A more complete command that looks for PHP and backup files, with results saved, reads:

gobuster dir -u http://10.10.10.10 
  -w /usr/share/seclists/Discovery/Web-Content/common.txt 
  -x php,txt,bak -t 40 -o gobuster-dir.txt

Gobuster prints each found path with its status code and size. If you see a wall of 301 redirects that all point to the same place, the server is likely redirecting everything — add -r to follow redirects, or filter them out with status-code flags.

Handling status codes and false positives

Some servers return 200 for every request, even paths that do not exist, which makes enumeration useless. Gobuster lets you blacklist a status code with -b or whitelist the ones you care about with -s. If a target answers 200 to nonsense, try filtering by response size instead with --exclude-length, pointing it at the byte count of the “not found” page.

Other Gobuster modes

Beyond dir, Gobuster can enumerate DNS subdomains (dns mode) and virtual hosts (vhost mode). Virtual-host discovery matters when one IP serves several sites by hostname:

gobuster vhost -u http://target.lab -w /usr/share/seclists/Discovery/DNS/subdomains-top1million-5000.txt --append-domain

Running ffuf: fuzzing with FUZZ

ffuf takes a different design philosophy. Instead of a fixed mode, you place the keyword FUZZ wherever you want ffuf to substitute each wordlist entry. For directory discovery that looks like:

ffuf -u http://10.10.10.10/FUZZ -w /usr/share/seclists/Discovery/Web-Content/common.txt

Because FUZZ can go anywhere in the request, ffuf also fuzzes parameters, headers, and POST data. To fuzz a GET parameter value, for example:

ffuf -u 'http://10.10.10.10/page?id=FUZZ' -w /usr/share/seclists/Discovery/Web-Content/common.txt

ffuf’s filtering is where it shines. You can match or filter on status code (-mc / -fc), response size (-ms / -fs), word count (-fw), and line count (-fl). A clean run that only shows real hits and hides the 404 noise might be:

ffuf -u http://10.10.10.10/FUZZ 
  -w /usr/share/seclists/Discovery/Web-Content/directory-list-2.3-medium.txt 
  -mc 200,301,302,403 -t 50 -o ffuf-dir.json -of json

The -of json flag writes structured output you can parse later, which is handy when you are feeding results into notes or another script.

Dealing with a chatty server in ffuf

When a target returns the same size page for every miss, grab that size from one failed request and filter it out:

ffuf -u http://10.10.10.10/FUZZ -w common.txt -fs 4242

Replace 4242 with the byte size of the standard “not found” response. This single trick cleans up most false-positive floods.

Gobuster vs ffuf: which to reach for

FactorGobusterffuf
Learning curveSimpler, mode-basedFlexible but more flags
Raw speedVery fastVery fast, often faster
Fuzzing scopePaths, DNS, vhostsAnything via FUZZ keyword
FilteringStatus and lengthStatus, size, words, lines, regex
Output formatsPlain textJSON, CSV, HTML, plain

In practice, many people run Gobuster for a quick first sweep because the command is short and memorable, then switch to ffuf when a target needs careful filtering or parameter fuzzing. Learning both pays off. Once you have found interesting endpoints, a tool like Burp Suite helps you probe them by hand — see our guide on Burp Suite on Parrot Linux. And if you came to directory busting straight after a port scan, our Nmap essential commands guide covers the step that comes before this one.

Good habits for lab enumeration

Keep your thread count reasonable on shared lab infrastructure — Hack The Box machines are used by many people at once, and 200 threads can degrade the box for everyone. Save your output to files so you can review hits without re-running. And always note which wordlist produced a finding, because reproducing a result later is far easier when you know the exact command you ran. If you are building toward certifications or structured practice, our guide on Parrot Linux for beginners puts these tools in a wider learning path.

FAQ

Is Gobuster or ffuf better for beginners?

Gobuster is gentler to start with because its dir mode needs only a URL and a wordlist. Move to ffuf once you need finer filtering or want to fuzz parameters and headers.

Why does my scan return every path as found?

The server is likely returning a 200 or a fixed-size page for missing paths. Filter by response size — --exclude-length in Gobuster or -fs in ffuf — using the byte count of a known-bad request.

Do I need the SecLists wordlists separately?

Parrot’s Security edition usually ships SecLists under /usr/share/seclists/. If it is missing, install it with sudo apt install seclists.