feroxbuster
v2.13.1 open-sourceThe section your link pointed to isn't on feroxbuster's page any more, so we've brought you to the top.
feroxbuster is a fast, simple, recursive content discovery tool written in Rust that uses brute force and wordlists to find unlinked web resources.
feroxbuster -u https://target.example.com -w wordlist.txt --scope https://target.example.com --scope https://api.example.com STATE_FILENAME=/tmp/scans/target1.state feroxbuster -u https://target.example.com -w wordlist.txt feroxbuster -u https://example.com -w wordlist.txt --unique feroxbuster -u https://api.example.com/v1 -w wordlist.txt --data-json @payload.json feroxbuster --request-file /tmp/burp_request.txt --protocol https -w /usr/share/wordlists/dirb/common.txt feroxbuster -u https://example.com -w /usr/share/wordlists/dirb/common.txt --scan-dir-listings feroxbuster -u https://example.com -w /usr/share/wordlists/dirb/common.txt --limit-bars 10 feroxbuster -u https://example.com --collect-backups bak,old,tar,zip feroxbuster -u https://target.example.com --client-cert /path/to/client.pem --client-key /path/to/client.key --server-certs /path/to/ca-bundle.crt install-nix.sh <custom_install_path> feroxbuster -u https://target.com -w wordlist.txt --dont-extract-links feroxbuster -u https://target.com -w https://example.com/words.txt choco install feroxbuster feroxbuster -u hackerone.com feroxbuster -u https://example.com -x .php php js feroxbuster -u https://example.com --burp feroxbuster --url https://example.com -w wordlist.txt --random-agent feroxbuster --url https://example.com -w wordlist.txt --dont-scan '/api/v[0-9]+/' feroxbuster -u https://example.com --dont-scan /admin feroxbuster --garbage-flag --help cat targets.txt | ./feroxbuster --stdin --parallel 10 feroxbuster -u https://target.com --auto-tune feroxbuster -u https://target.com --auto-bail feroxbuster -u http://target.com --rate-limit 50 feroxbuster -u http://target.com --silent | tee urls.txt feroxbuster -u http://target.com -o stats.json --json feroxbuster -u https://example.com --filter-similar-to https://example.com/homepage feroxbuster -u https://example.com --time-limit 300 time_limit: 600 feroxbuster --resume-from ferox_state.txt feroxbuster -u http://example.com -o results.json --debug-log logs.json --json feroxbuster -u https://example.com --word-count 100 feroxbuster -u https://target.com --replay-proxy http://127.0.0.1:8080 --replay-codes 403,500 feroxbuster --url https://example.com --filter-status 200,301,302 ./feroxbuster -u http://127.1 --scan-limit 2 ./feroxbuster -u http://127.1 --extract-links ./feroxbuster -u http://example.com -o trace.log -vvvv
Summary
feroxbuster is an open-source command-line tool, written in Rust, that brute-forces directories and files on a web server using wordlists to find content that isn't linked anywhere, recursing automatically into new directories as it finds them. It's built for penetration testers and red teamers doing content discovery during web-app assessments, and it supports scoping scans to specific hosts, feeding it raw requests captured from Burp Suite, fuzzing JSON or form-encoded APIs directly, and filtering duplicate or soft-404 responses to cut noise on large targets. A commercial Pro edition exists alongside the free tool for those wanting more thorough results with less noise, but the core scanner itself costs nothing. First committed in 2020, it remains active with 46 contributors and 60 commits in the past year, though its most recent release was 251 days ago.
feroxbuster is a fast, simple, recursive content discovery tool written in Rust that uses brute force and wordlists to find unlinked web resources.
How feroxbuster helps
What unlinked directories and files actually exist on this web server?
brute-forces the target with a wordlist and recurses automatically into every new directory it discovers, building out the exposed content tree instead of a flat list of hits
Which of these discovered paths are just noise from soft-404s or duplicate pages?
filters responses that are structurally identical or near-identical using response comparison, so a content-heavy target doesn't bury real finds under thousands of look-alike pages
Can I turn a request I already captured in Burp into a full content scan without rebuilding it by hand?
reads a raw HTTP request file, headers and body included, and drives the scan from exactly what was captured
How exposed is that open directory listing I just found?
recurses into the listing itself and enumerates the entire exposed file tree beneath it, rather than reporting just the one listing page
Did that scan wander off into hosts I never meant to test?
restricts crawling and recursion to explicitly defined in-scope targets, so redirects or links to other domains don't get followed
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 feroxbuster, 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 feroxbuster 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
42 entries
No entries match these filters.
- December 20251
- October 20251
- September 20251
- September 20241
- June 20241
- April 20241
- March 20241
- November 20231
- May 20231
- April 20232
- March 20232
- February 20231
- May 20221
- April 20222
- March 20221
- January 20221
- December 20211
- October 20211
- June 20212
- May 20211
- February 20213
- January 20213
- December 20204
- November 20204
- October 20204
Project health
Issue, contributor and maintainer activity in epi052/feroxbuster, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 +1 vs prior 12 months
- Maintainers 1 +0 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 14 days first maintainer reply 4 days
- Open backlog 19 of 326 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 19
- Contributors / month 2
- Commits / month 2
- Stars 8,068
- bugs 52%
- features 29%
- other 19%
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 feroxbuster 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
-
A Detailed Guide on Feroxbuster
This Feroxbuster guide covers everything you need to know about using this powerful tool to identify directories and files on web servers through brute-force techniques.
2 more quotes
Feroxbuster is a robust tool designed to identify directories and files on web servers using brute-force techniques .
Here we are going to discuss various tasks which we can perform using Feroxbuster .
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.
Choose a badge style and copy the code →