Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is ffuf?

ffuf is a fast web fuzzer that substitutes wordlist entries into any part of an HTTP request, used to discover hidden directories, files, parameters, and virtual hosts.

Illustration for the cybersecurity term ffuf
Home / Blog / Cybersecurity Terms / What Is ffuf?
17 November 2026

What Is ffuf?

What Is ffuf?

ffuf, short for Fuzz Faster U Fool, is a web fuzzer written in Go. The idea behind it is simple and more general than the directory brute-forcers it replaced: you place the keyword FUZZ anywhere in an HTTP request, supply a wordlist, and ffuf sends one request per entry with the keyword substituted.

Because the keyword can go anywhere, one tool covers several discovery problems. Put it in the path and you are finding hidden directories and files. Put it in a query string name and you are hunting undocumented parameters. Put it in the Host header and you are enumerating virtual hosts on a shared address. Put it in a POST body or a cookie and you are testing values. Multiple keywords can be used at once, with the wordlists iterated in pairs or as a full product.

The Part That Decides Whether It Works

Sending thousands of requests is easy. Deciding which responses are interesting is the entire problem, because most web servers do not return a clean 404 for content that does not exist. Many return a 200 with a friendly error page, a redirect to a login screen, or a soft error that looks identical for every wrong guess.

ffuf handles this with matchers and filters applied to status code, response size, word count, line count, response time, and regular expressions against the body. The practical workflow is to run a short scan, observe what a known-bad request returns, and filter that signature out. Its automatic calibration feature does this unattended by sending deliberately random requests first, recording how the server answers nonsense, and filtering accordingly.

Getting this wrong in either direction ruins the result. Too little filtering buries one real finding in four thousand false ones. Too much filtering removes the finding along with the noise. This is the main reason that discovery output needs reviewing by a person rather than pasting into a report.

What It Finds in Practice

Wordlist quality matters more than speed. SecLists is the common source, and for a specific technology stack a targeted list of a few hundred relevant entries outperforms a generic list of a million.

How It Compares

Against Gobuster, ffuf is more flexible because the keyword can be placed anywhere, while Gobuster’s dedicated modes are simpler for straightforward directory and DNS work. Against Burp Suite’s Intruder, ffuf is dramatically faster, particularly in the free Burp edition where Intruder is deliberately throttled. Most testers run discovery in ffuf and bring the interesting findings back into Burp for manual work.

What Defenders Should Do

The activity is extremely loud, which is an advantage if anyone is looking at the logs.

A web application firewall will block naive scanning, but a patient tester at one request per second with a realistic user agent generally passes through it. Logging and review remain the controls that work.

At Privia Security, our Web Application Security Services include content and parameter discovery as a routine part of application assessments.

FAQ – Frequently Asked Questions

Is ffuf Only for Finding Directories?

No, and that is its main advantage over older tools. The FUZZ keyword can be placed in any part of the request: the path, a query parameter name or value, a header including Host for virtual host discovery, a cookie, or a POST body. Multiple keywords can be used simultaneously, which supports credential testing and combined parameter and value fuzzing.

Why Are the Results Full of False Positives?

Because many servers do not return a clean 404 for content that does not exist, answering instead with a 200 and an error page, or a redirect to a login screen. Use matchers and filters on status code, response size, word count, and body content, or enable automatic calibration so ffuf learns the server’s response to nonsense requests and filters it out.

How Do We Detect Content Discovery Against Our Site?

Alert on the volume of distinct 404 responses per source address in a short window. Hundreds of non-existent paths from one client within a minute has no legitimate explanation and is one of the highest-confidence web alerts available. Watch also for requests to backup extensions and version control paths, which no normal user ever requests.

Does a Web Application Firewall Stop It?

It stops careless scanning at default speed with a default user agent. A patient tester running at one request per second with a realistic header set, distributed across source addresses, will usually pass through. Treat a firewall as a control that raises the cost and improves your logging, not as a reason to leave backup files and old API versions reachable.

Related Terms

You May Be Interested In These

What Is OT Backup and Restore?

Cybersecurity Terms

17 November 2026

What Is OT Backup and Restore?

Read More
What Is AI Red Teaming?

Cybersecurity Terms

17 November 2026

What Is AI Red Teaming?

Read More