dirsearch - Web path discovery

An advanced web path brute-forcer

dirsearch is being actively developed by @maurosoria and @shelld3v

Reach to our Discord server to communicate with the team at best

Supported Platforms

dirsearch runs on multiple platforms and can be used either via Python or standalone binaries:

Platform	Python	Standalone Binary
Linux (x86_64)	Python 3.9+	`dirsearch-linux-amd64`
Windows (x64)	Python 3.9+	`dirsearch-windows-x64.exe`
macOS (Intel)	Python 3.9+	`dirsearch-macos-intel`
macOS (Apple Silicon)	Python 3.9+	`dirsearch-macos-silicon`

Standalone binaries are self-contained executables that don't require Python installation.

Installation & Usage

Requirement: python 3.9 or higher

Choose one of these installation options:

Install with git: git clone https://github.com/maurosoria/dirsearch.git --depth 1 (RECOMMENDED)
Install with ZIP file: Download here
Install with Docker: docker build -t "dirsearch:v0.4.3" . (more information can be found here)
Install with PyPi: pip3 install dirsearch or pip install dirsearch
Install with Kali Linux: sudo apt-get install dirsearch (deprecated)

Standalone Binaries

Pre-built standalone binaries are available for all major platforms. These don't require Python to be installed.

Download from Releases

Platform	Binary Name	Architecture
Linux	`dirsearch-linux-amd64`	x86_64
Windows	`dirsearch-windows-x64.exe`	x64
macOS Intel	`dirsearch-macos-intel`	x86_64
macOS Apple Silicon	`dirsearch-macos-silicon`	ARM64

Usage:

# Linux/macOS - make executable first
chmod +x dirsearch-linux-amd64
./dirsearch-linux-amd64 -u https://target

# Windows
dirsearch-windows-x64.exe -u https://target

Note: Standalone binaries include bundled db/ wordlists and config.ini. Session files are stored in $HOME/.dirsearch/sessions/ when using bundled builds.

Wordlists (IMPORTANT)

Summary:

Wordlist is a text file, each line is a path.
About extensions, unlike other tools, dirsearch only replaces the %EXT% keyword with extensions from -e flag.
For wordlists without %EXT% (like SecLists), -f | --force-extensions switch is required to append extensions to every word in wordlist, as well as the /.
To apply your extensions to wordlist entries that have extensions already, use -O | --overwrite-extensions (Note: some extensions are excluded from being overwritted such as .log, .json, .xml, ... or media extensions like .jpg, .png)
To use multiple wordlists, you can separate your wordlists with commas. Example: wordlist1.txt,wordlist2.txt.
Bundled wordlist categories live in db/categories/ and can be selected with --wordlist-categories. Available: extensions, conf, vcs, backups, db, logs, keys, web, common (use all to include everything).

Wordlist Examples (click to expand)

Examples:

Normal extensions:

index.%EXT%

Passing asp and aspx as extensions will generate the following dictionary:

index
index.asp
index.aspx

Force extensions:

admin

Passing php and html as extensions with -f/--force-extensions flag will generate the following dictionary:

admin
admin.php
admin.html
admin/

Overwrite extensions:

login.html

Passing jsp and jspa as extensions with -O/--overwrite-extensions flag will generate the following dictionary:

login.html
login.jsp
login.jspa

Options

Full Options List (click to expand)

Usage: dirsearch.py [-u|--url] target [-e|--extensions] extensions [options]

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit

  Mandatory:
    -u URL, --url=URL   Target URL(s), can use multiple flags
    -l PATH, --urls-file=PATH
                        URL list file
    --stdin             Read URL(s) from STDIN
    --cidr=CIDR         Target CIDR
    --raw=PATH          Load raw HTTP request from file (use '--scheme' flag
                        to set the scheme)
    --nmap-report=PATH  Load targets from nmap report (Ensure the inclusion of
                        the -sV flag during nmap scan for comprehensive
                        results)
    -s SESSION_FILE, --session=SESSION_FILE
                        Session file
                        Note: legacy .pickle/.pkl sessions are no longer supported.
    --config=PATH       Path to configuration file (Default:
                        'DIRSEARCH_CONFIG' environment variable, otherwise
                        'config.ini')

  Dictionary Settings:
    -w WORDLISTS, --wordlists=WORDLISTS
                        Wordlist files or directories contain wordlists
                        (separated by commas)
    --wordlist-categories=CATEGORIES
                        Comma-separated wordlist category names (e.g.
                        common,conf,web). Use 'all' to include all bundled
                        categories
    -e EXTENSIONS, --extensions=EXTENSIONS
                        Extension list separated by commas (e.g. php,asp)
    -f, --force-extensions
                        Add extensions to the end of every wordlist entry. By
                        default dirsearch only replaces the %EXT% keyword with
                        extensions
    -O, --overwrite-extensions
                        Overwrite other extensions in the wordlist with your
                        extensions (selected via `-e`)
    --exclude-extensions=EXTENSIONS
                        Exclude extension list separated by commas (e.g.
                        asp,jsp)
    --remove-extensions
                        Remove extensions in all paths (e.g. admin.php ->
                        admin)
    --prefixes=PREFIXES
                        Add custom prefixes to all wordlist entries (separated
                        by commas)
    --suffixes=SUFFIXES
                        Add custom suffixes to all wordlist entries, ignore
                        directories (separated by commas)
    -U, --uppercase     Uppercase wordlist
    -L, --lowercase     Lowercase wordlist
    -C, --capital       Capital wordlist

  General Settings:
    -t THREADS, --threads=THREADS
                        Number of threads
    --list-sessions     List resumable sessions and exit
    --sessions-dir=PATH Directory to search for resumable sessions (default:
                        dirsearch path /sessions, or $HOME/.dirsearch/sessions
                        when bundled)
    --async             Enable asynchronous mode
    -r, --recursive     Brute-force recursively
    --deep-recursive    Perform recursive scan on every directory depth (e.g.
                        api/users -> api/)
    --force-recursive   Do recursive brute-force for every found path, not
                        only directories
    -R DEPTH, --max-recursion-depth=DEPTH
                        Maximum recursion depth
    --recursion-status=CODES
                        Valid status codes to perform recursive scan, support
                        ranges (separated by commas)
    --subdirs=SUBDIRS   Scan sub-directories of the given URL[s] (separated by
                        commas)
    --exclude-subdirs=SUBDIRS
                        Exclude the following subdirectories during recursive
                        scan (separated by commas)
    -i CODES, --include-status=CODES
                        Include status codes, separated by commas, support
                        ranges (e.g. 200,300-399)
    -x CODES, --exclude-status=CODES
                        Exclude status codes, separated by commas, support
                        ranges (e.g. 301,500-599)
    --exclude-sizes=SIZES
                        Exclude responses by sizes, separated by commas (e.g.
                        0B,4KB)
    --exclude-text=TEXTS
                        Exclude responses by text, can use multiple flags
    --exclude-regex=REGEX
                        Exclude responses by regular expression
    --exclude-redirect=STRING
                        Exclude responses if this regex (or text) matches
                        redirect URL (e.g. '/index.html')
    --exclude-response=PATH
                        Exclude responses similar to response of this page,
                        path as input (e.g. 404.html)
    --skip-on-status=CODES
                        Skip target whenever hit one of these status codes,
                        separated by commas, support ranges
    --min-response-size=LENGTH
                        Minimum response length
    --max-response-size=LENGTH
                        Maximum response length
    --max-time=SECONDS  Maximum runtime for the scan
    --exit-on-error     Exit whenever an error occurs

  Request Settings:
    -m METHOD, --http-method=METHOD
                        HTTP method (default: GET)
    -d DATA, --data=DATA
                        HTTP request data
    --data-file=PATH    File contains HTTP request data
    -H HEADERS, --header=HEADERS
                        HTTP request header, can use multiple flags
    --headers-file=PATH
                        File contains HTTP request headers
    -F, --follow-redirects
                        Follow HTTP redirects
    --random-agent      Choose a random User-Agent for each request
    --auth=CREDENTIAL   Authentication credential (e.g. user:password or
                        bearer token)
    --auth-type=TYPE    Authentication type (basic, digest, bearer, ntlm, jwt)
    --cert-file=PATH    File contains client-side certificate
    --key-file=PATH     File contains client-side certificate private key
                        (unencrypted)
    --user-agent=USER_AGENT
    --cookie=COOKIE

  Connection Settings:
    --timeout=TIMEOUT   Connection timeout
    --delay=DELAY       Delay between requests
    -p PROXY, --proxy=PROXY
                        Proxy URL (HTTP/SOCKS), can use multiple flags
    --proxies-file=PATH
                        File contains proxy servers
    --proxy-auth=CREDENTIAL
                        Proxy authentication credential
    --replay-proxy=PROXY
                        Proxy to replay with found paths
    --tor               Use Tor network as proxy
    --scheme=SCHEME     Scheme for raw request or if there is no scheme in the
                        URL (Default: auto-detect)
    --max-rate=RATE     Max requests per second
    --retries=RETRIES   Number of retries for failed requests
    --ip=IP             Server IP address
    --interface=NETWORK_INTERFACE
                        Network interface to use

  Advanced Settings:
    --crawl             Crawl for new paths in responses

  View Settings:
    --full-url          Full URLs in the output (enabled automatically in
                        quiet mode)
    --redirects-history
                        Show redirects history
    --no-color          No colored output
    -q, --quiet-mode    Quiet mode

  Output Settings:
    -o PATH/URL, --output=PATH/URL
                        Output file or MySQL/PostgreSQL URL (Format:
                        scheme://[username:password@]host[:port]/database-
                        name)
    --format=FORMAT     Report format (Available: simple, plain, json, xml,
                        md, csv, html, sqlite, mysql, postgresql)
    --log=PATH          Log file

Configuration

Configuration File Reference (click to expand)

By default, config.ini inside your dirsearch directory is used as the configuration file but you can select another file via --config flag or DIRSEARCH_CONFIG environment variable.

# If you want to edit dirsearch default configurations, you can
# edit values in this file. Everything after `#` is a comment
# and won't be applied

[general]
threads = 25
async = False
recursive = False
deep-recursive = False
force-recursive = False
recursion-status = 200-399,401,403
max-recursion-depth = 0
exclude-subdirs = %%ff/,.;/,..;/,;/,./,../,%%2e/,%%2e%%2e/
random-user-agents = False
max-time = 0
exit-on-error = False
# subdirs = /,api/
# include-status = 200-299,401
# exclude-status = 400,500-999
# exclude-sizes = 0b,123gb
# exclude-text = "Not found"
# exclude-regex = "^403$"
# exclude-redirect = "*/error.html"
# exclude-response = 404.html
# skip-on-status = 429,999

[dictionary]
default-extensions = php,aspx,jsp,html,js
force-extensions = False
overwrite-extensions = False
lowercase = False
uppercase = False
capitalization = False
# exclude-extensions = old,log
# prefixes = .,admin
# suffixes = ~,.bak
# wordlists = /path/to/wordlist1.txt,/path/to/wordlist2.txt

[request]
http-method = get
follow-redirects = False
# headers-file = /path/to/headers.txt
# user-agent = MyUserAgent
# cookie = SESSIONID=123

[connection]
timeout = 7.5
delay = 0
max-rate = 0
max-retries = 1
## By disabling `scheme` variable, dirsearch will automatically identify the URI scheme
# scheme = http
# proxy = localhost:8080
# proxy-file = /path/to/proxies.txt
# replay-proxy = localhost:8000

[advanced]
crawl = False

[view]
full-url = False
quiet-mode = False
color = True
show-redirects-history = False

[output]
## Support: plain, simple, json, xml, md, csv, html, sqlite
report-format = plain
autosave-report = True
autosave-report-folder = reports/
# log-file = /path/to/dirsearch.log
# log-file-size = 50000000

How to use

Some examples for how to use dirsearch - those are the most common arguments. If you need all, just use the -h argument.

Simple usage

python3 dirsearch.py -u https://target

python3 dirsearch.py -e php,html,js -u https://target

python3 dirsearch.py -e php,html,js -u https://target -w /path/to/wordlist

More Usage Examples (click to expand)

Pausing progress

dirsearch allows you to pause the scanning progress with CTRL+C, from here, you can save the progress (and continue later), skip the current target, or skip the current sub-directory.

Recursion

Recursive brute-force is brute-forcing continuously the after of found directories. For example, if dirsearch finds admin/, it will brute-force admin/* (* is where it brute forces). To enable this feature, use -r (or --recursive) flag

python3 dirsearch.py -e php,html,js -u https://target -r

You can set the max recursion depth with --max-recursion-depth, and status codes to recurse with --recursion-status

python3 dirsearch.py -e php,html,js -u https://target -r --max-recursion-depth 3 --recursion-status 200-399

There are 2 more options: --force-recursive and --deep-recursive
- Force recursive: Brute force recursively all found paths, not just paths end with /
- Deep recursive: Recursive brute-force all depths of a path (a/b/c => add a/, a/b/)
If there are sub-directories that you do not want to brute-force recursively, use --exclude-subdirs

python3 dirsearch.py -e php,html,js -u https://target -r --exclude-subdirs image/,media/,css/

Threads

The thread number (-t | --threads) reflects the number of separated brute force processes. And so the bigger the thread number is, the faster dirsearch runs. By default, the number of threads is 25, but you can increase it if you want to speed up the progress.

In spite of that, the speed still depends a lot on the response time of the server. And as a warning, we advise you to keep the threads number not too big because it can cause DoS (Denial of Service).

python3 dirsearch.py -e php,htm,js,bak,zip,tgz,txt -u https://target -t 20

Asynchronous

You can switch to asynchronous mode by --async, let dirsearch use coroutines instead of threads to handle concurrent requests.

In theory, asynchronous mode offers better performance and lower CPU usage since it doesn't require switching between different thread contexts. Additionally, pressing CTRL+C will immediately pause progress without needing to wait for threads to suspend.

Prefixes / Suffixes

--prefixes: Add custom prefixes to all entries

python3 dirsearch.py -e php -u https://target --prefixes .,admin,_

Wordlist:

tools

Generated with prefixes:

tools
.tools
admintools
_tools

--suffixes: Add custom suffixes to all entries

python3 dirsearch.py -e php -u https://target --suffixes ~

Wordlist:

index.php
internal

Generated with suffixes:

index.php
internal
index.php~
internal~

Blacklist

Inside the db/ folder, there are several "blacklist files". Paths in those files will be filtered from the scan result if they have the same status as mentioned in the filename.

Example: If you add admin.php into db/403_blacklist.txt, whenever you do a scan that admin.php returns 403, it will be filtered from the result.

Filters

Use -i | --include-status and -x | --exclude-status to select allowed and not allowed response status-codes

For more advanced filters: --exclude-sizes, --exclude-texts, --exclude-regexps, --exclude-redirects and --exclude-response

python3 dirsearch.py -e php,html,js -u https://target --exclude-sizes 1B,243KB

python3 dirsearch.py -e php,html,js -u https://target --exclude-texts "403 Forbidden"

python3 dirsearch.py -e php,html,js -u https://target --exclude-regexps "^Error$"

python3 dirsearch.py -e php,html,js -u https://target --exclude-redirects "https://(.*).okta.com/*"

python3 dirsearch.py -e php,html,js -u https://target --exclude-response /error.html

Raw request

dirsearch allows you to import the raw request from a file. The content would be something looked like this:

GET /admin HTTP/1.1
Host: admin.example.com
Cache-Control: max-age=0
Accept: */*

Since there is no way for dirsearch to know what the URI scheme is, you need to set it using the --scheme flag. By default, dirsearch automatically detects the scheme.

Wordlist formats

Supported wordlist formats: uppercase, lowercase, capitalization

Lowercase:

admin
index.html

Uppercase:

ADMIN
INDEX.HTML

Capital:

Admin
Index.html

Exclude extensions

Use -X | --exclude-extensions with an extension list will remove all paths in the wordlist that contains the given extensions

python3 dirsearch.py -u https://target -X jsp

Wordlist:

admin.php
test.jsp

After:

admin.php

Scan sub-directories

From an URL, you can scan a list of sub-directories with --subdirs.

python3 dirsearch.py -e php,html,js -u https://target --subdirs /,admin/,folder/

Proxies

dirsearch supports SOCKS and HTTP proxy, with two options: a proxy server or a list of proxy servers.

python3 dirsearch.py -e php,html,js -u https://target --proxy 127.0.0.1:8080

python3 dirsearch.py -e php,html,js -u https://target --proxy socks5://10.10.0.1:8080

python3 dirsearch.py -e php,html,js -u https://target --proxylist proxyservers.txt

Reports

Supported report formats: simple, plain, json, xml, md, csv, html, sqlite, mysql, postgresql

python3 dirsearch.py -e php -l URLs.txt --format plain -o report.txt

python3 dirsearch.py -e php -u https://target --format html -o target.json

More example commands

cat urls.txt | python3 dirsearch.py --stdin

python3 dirsearch.py -u https://target --max-time 360

python3 dirsearch.py -u https://target --auth admin:pass --auth-type basic

python3 dirsearch.py -u https://target --header-list rate-limit-bypasses.txt

There are more to discover, try yourself!

Session Management

dirsearch supports saving and resuming scan sessions, allowing you to pause a long-running scan and continue it later.

Session Format

Sessions are stored in JSON format (directory-based structure) for human readability and easy inspection. Legacy .pickle/.pkl session files are no longer supported.

Session directory structure:

session_name/
├── meta.json        # Version, timestamps, output history
├── controller.json  # Scan state (URLs, directories, progress)
├── dictionary.json  # Wordlist state and position
└── options.json     # Command-line options used

Saving a Session

When you pause a scan with CTRL+C, you'll be prompted to save the session:

python3 dirsearch.py -u https://target -e php
# Press CTRL+C during scan
# Select "save" and provide a session name

Resuming a Session

Resume a saved session with the -s / --session flag:

python3 dirsearch.py -s sessions/my_session

Listing Available Sessions

View all resumable sessions with --list-sessions:

python3 dirsearch.py --list-sessions

This displays:

Session path
Target URL
Remaining targets and directories
Jobs processed
Error count
Last modified time

Custom Sessions Directory

Specify a custom directory to search for sessions:

python3 dirsearch.py --list-sessions --sessions-dir /path/to/sessions

Default session locations:

Source install: <dirsearch>/sessions/
Bundled binary: $HOME/.dirsearch/sessions/

Output History

Sessions maintain a history of previous scan outputs, allowing you to review results from interrupted scans. Each resume appends to the output history with timestamps.

Support Docker

Docker Installation & Usage (click to expand)

Install Docker Linux

Install Docker

curl -fsSL https://get.docker.com | bash

To use docker you need superuser power

Build Image dirsearch

To create image

docker build -t "dirsearch:v0.4.3" .

dirsearch is the name of the image and v0.4.3 is the version

Using dirsearch

For using

docker run -it --rm "dirsearch:v0.4.3" -u target -e php,html,js,zip

Building from Source

You can build standalone executables using PyInstaller. This creates a single binary file that includes all dependencies.

Requirements

Python 3.9+
PyInstaller 6.3.0+
All dependencies from requirements.txt

Quick Build

# Install dependencies
pip install -r requirements.txt
pip install pyinstaller==6.3.0

# Build using the spec file
pyinstaller pyinstaller/dirsearch.spec

# Binary will be in dist/dirsearch
./dist/dirsearch --version

Manual Build (Linux/macOS)

pyinstaller \
  --onefile \
  --name dirsearch \
  --paths=. \
  --collect-submodules=lib \
  --add-data "db:db" \
  --add-data "config.ini:." \
  --add-data "lib/report:lib/report" \
  --hidden-import=requests \
  --hidden-import=httpx \
  --hidden-import=urllib3 \
  --hidden-import=jinja2 \
  --hidden-import=colorama \
  --strip \
  --clean \
  dirsearch.py

Manual Build (Windows)

pyinstaller `
  --onefile `
  --name dirsearch `
  --paths=. `
  --collect-submodules=lib `
  --add-data "db;db" `
  --add-data "config.ini;." `
  --add-data "lib/report;lib/report" `
  --hidden-import=requests `
  --hidden-import=httpx `
  --hidden-import=urllib3 `
  --hidden-import=jinja2 `
  --hidden-import=colorama `
  --clean `
  dirsearch.py

Note: Windows uses ; instead of : as the path separator in --add-data.

Build Output

After building:

Linux/macOS: dist/dirsearch
Windows: dist/dirsearch.exe

The binary includes:

All Python dependencies
db/ directory (wordlists, blacklists)
config.ini (default configuration)
lib/report/ (Jinja2 templates for reports)

CI/CD & GitHub Workflows

dirsearch uses GitHub Actions for continuous integration and automated builds.

Available Workflows

Workflow	Trigger	Description
Inspection (CI)	Push, PR	Runs tests, linting, and codespell on Python 3.9/3.11 across Ubuntu and Windows
PyInstaller Linux	Manual, Workflow call	Builds `dirsearch-linux-amd64` binary
PyInstaller Windows	Manual, Workflow call	Builds `dirsearch-windows-x64.exe` binary
PyInstaller macOS Intel	Manual, Workflow call	Builds `dirsearch-macos-intel` binary
PyInstaller macOS Silicon	Manual, Workflow call	Builds `dirsearch-macos-silicon` binary
PyInstaller Draft Release	Manual	Builds all platforms and creates a draft GitHub release
Docker Image	Push, PR	Builds and tests Docker image
CodeQL Analysis	Push, PR, Schedule	Security scanning with GitHub CodeQL
Semgrep Analysis	Push, PR	Static analysis with Semgrep

Running Workflows Manually

PyInstaller builds can be triggered manually from the GitHub Actions tab:

Go to Actions > Select workflow (e.g., "PyInstaller Linux")
Click Run workflow
Download artifacts from the completed run

Creating a Release

To create a new release with all platform binaries:

Go to Actions > PyInstaller Draft Release
Click Run workflow
Enter the tag (e.g., v0.4.4)
Select target branch
Optionally mark as prerelease
Review and publish the draft release

Build Matrix

The CI workflow tests on:

Python versions: 3.9, 3.11
Operating systems: Ubuntu (latest), Windows (latest)

References

Articles & Tutorials (click to expand)

Comprehensive Guide on Dirsearch by Shubham Sharma
Comprehensive Guide on Dirsearch Part 2 by Shubham Sharma
How to Find Hidden Web Directories with Dirsearch by GeeksforGeeks
GUÍA COMPLETA SOBRE EL USO DE DIRSEARCH by ESGEEKS
How to use Dirsearch to detect web directories by EHacking
dirsearch how to by VK9 Security
Find Hidden Web Directories with Dirsearch by Wonder How To
Brute force directories and files in webservers using dirsearch by Raj Upadhyay
Live Bug Bounty Recon Session on Yahoo (Amass, crts.sh, dirsearch) w/ @TheDawgyg by Nahamsec
Dirsearch to find Hidden Web Directories by Irfan Shakeel
Getting access to 25000 employees details by Sahil Ahamad
Best Tools For Directory Bruteforcing by Shubham Goyal
Discover hidden files & directories on a webserver - dirsearch full tutorial by CYBER BYTES

Tips

The server has requests limit? That's bad, but feel free to bypass it, by randomizing proxy with --proxy-list
Want to find out config files or backups? Try --suffixes ~ and --prefixes .
Want to find only folders/directories? Why not combine --remove-extensions and --suffixes /!
The mix of --cidr, -F, -q and will reduce most of noises + false negatives when brute-forcing with a CIDR
Scan a list of URLs, but don't want to see a 429 flood? --skip-on-status 429 will help you to skip a target whenever it returns 429
The server contains large files that slow down the scan? You might want to use HEAD HTTP method instead of GET
Brute-forcing CIDR is slow? Probably you forgot to reduce request timeout and request retries. Suggest: --timeout 3 --retries 1

Contribution

We have been receiving a lot of helps from many people around the world to improve this tool. Thanks so much to everyone who have helped us so far! See CONTRIBUTORS.md to know who they are.

Pull requests and feature requests are welcomed

License

Copyright (C) Mauro Soria ([email protected])

License: GNU General Public License, version 2

Name		Name	Last commit message	Last commit date
Latest commit History 2,601 Commits
.github		.github
db		db
lib		lib
pyinstaller		pyinstaller
sessions		sessions
static		static
tests		tests
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CHANGELOG.md		CHANGELOG.md
CONTRIBUTORS.md		CONTRIBUTORS.md
Dockerfile		Dockerfile
README.md		README.md
__init__.py		__init__.py
config.ini		config.ini
dirsearch.py		dirsearch.py
requirements.txt		requirements.txt
setup.cfg		setup.cfg
setup.py		setup.py
testing.py		testing.py

Uh oh!

maurosoria/dirsearch

Folders and files

Latest commit

History

Repository files navigation

dirsearch - Web path discovery

Table of Contents

Supported Platforms

Installation & Usage

Standalone Binaries

Wordlists (IMPORTANT)

Options

Configuration

How to use

Simple usage

Pausing progress

Recursion

Threads

Asynchronous

Prefixes / Suffixes

Blacklist

Filters

Raw request

Wordlist formats

Lowercase:

Uppercase:

Capital:

Exclude extensions

Scan sub-directories

Proxies

Reports

More example commands

Session Management

Session Format

Saving a Session

Resuming a Session

Listing Available Sessions

Custom Sessions Directory

Output History

Support Docker

Install Docker Linux

Build Image dirsearch

Using dirsearch

Building from Source

Requirements

Quick Build

Manual Build (Linux/macOS)

Manual Build (Windows)

Build Output

CI/CD & GitHub Workflows

Available Workflows

Running Workflows Manually

Creating a Release

Build Matrix

References

Tips

Contribution

Pull requests and feature requests are welcomed

License

About

Topics

Resources

Uh oh!

Stars

Watchers

Forks

Releases 16

Sponsor this project

Uh oh!

Packages 0

Used by 198

Contributors 95

Uh oh!

Languages

Packages