ffuf
v2.3.0 open-sourceThe section your link pointed to isn't on ffuf's page any more, so we've brought you to the top.
ffuf is a fast web fuzzer written in Go for directory, vhost, and parameter discovery using a FUZZ keyword in URLs, headers, or POST data.
ffuf -w wordlist.txt -u http://example.com/FUZZ --noninteractive
ffuf -u https://example.com/FUZZ -w wordlist.txt --interactive
ffuf -u https://example.com/FUZZ/FUZZ2 -w wordlist.txt --interactive --recursive-strategy root
ffuf -u https://example.com/FUZZ -w wordlist.txt -mc 200,405
ffuf -w wordlist.txt -u https://example.com/FUZZ -maxtime 60
ffuf -w wordlist.txt -u https://example.com/FUZZ -replay-proxy http://127.0.0.1:8080
ffuf -w wordlist1.txt:W1,wordlist2.txt:W2 -u https://target.com/FUZZ -of html -o report.html
ffuf -u https://target.com/ -X GET,POST,PUT -fc 404 -fs 10-20
ffuf -u https://target.com/FUZZ -w wordlist.txt -debug-log debug.log
ffuf -u https://example.com/FUZZ -w - --input-cmd 'echo "payload1\npayload2"'
cat /tmp/my_wordlist.txt | ffuf -u https://example.com/FUZZ -w -
ffuf -u https://example.com/FUZZ -w wordlist.txt -timeout 30s
ffuf -w wordlist.txt -u https://example.com/FUZZ -of csv -o results.csv
ffuf -w wordlist.txt -u https://example.com/FUZZ -e php
ffuf -u https://target.com/FUZZ -w wordlist.txt --regexp '^[0-9]{4}-[0-9]{2}-[0-9]{2}$'
Summary
ffuf is an open-source command-line web fuzzer, free to use, written in Go and run from a terminal by replacing a FUZZ keyword in a URL, header, or POST body with entries from a wordlist. It handles directory and file brute-forcing, virtual host and subdomain discovery, and parameter fuzzing, with clusterbomb and sniper modes for combining or targeting multiple wordlists, and its flags deliberately mirror curl's so anyone comfortable with curl can pick it up quickly. It's aimed at penetration testers and bug bounty hunters doing content discovery and recon rather than teams wanting a managed scanning platform. It sits in the same space as tools like gobuster and dirsearch, though its README doesn't name them directly. First committed in 2018, it remains active with 57 contributors and a release cut just 39 days ago.
ffuf is a fast web fuzzer written in Go for directory, vhost, and parameter discovery using a FUZZ keyword in URLs, headers, or POST data.
How ffuf helps
Which hidden directories and files exist on this web server that aren't linked anywhere?
runs a wordlist against the target path and reports every response that comes back with a status worth looking at, such as 200s, letting the reader filter out noise like 404s
Is this server quietly hosting other sites or environments under a different name?
substitutes candidate names into the Host header and compares response sizes across virtual hosts, surfacing the ones that differ from the default site even without DNS records
Did a set of test cases that failed with authentication last time start succeeding after a change?
filters results by response code, such as isolating 401s, so a rerun against the same wordlist shows whether previously blocked paths now return differently
Can I chase every subdirectory a scan turns up without babysitting it manually?
recursive fuzzing re-runs the wordlist against newly discovered directories automatically, with a per-job time limit so any one branch doesn't run indefinitely
How do I test combinations of two variables, like every subdomain against every path, in one pass?
clusterbomb mode pairs every entry from one wordlist against every entry from another, while pitchfork mode instead steps through both lists in lockstep for matched pairs like credential lists
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for ffuf, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail ffuf puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
20 entries
No entries match these filters.
- September 20261
- July 20262
- September 20231
- February 20231
- May 20221
- March 20221
- April 20212
- January 20211
- July 20201
- January 20201
- November 20192
- June 20191
- April 20191
- March 20191
- November 20183
Project health
Issue, contributor and maintainer activity in ffuf/ffuf, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 6 +4 vs prior 12 months
- Maintainers 1 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 539 days first maintainer reply 3.9 days
- Open backlog 165 of 554 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 165
- Contributors / month 3
- Commits / month 8
- Stars 16,682
- bugs 6%
- features 11%
- other 83%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 4, 2026Where ffuf turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 1
-
Comprehensive Guide on ffuf
In this article, we will learn how we can use ffuf, which states for “Fuzz Faster U Fool”, which is an interesting open-source web fuzzing tool.
2 more quotes
Since its release, many people have gravitated towards ffuf, particularly in the bug bounty scenario.
Many people have gravitated towards ffuf since its release, especially in the bug bounty scene.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.