Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
January 9, 2023 11:16
February 14, 2019 15:23
September 7, 2017 16:37
February 14, 2019 15:23
January 2, 2022 08:30
April 7, 2020 18:26

Image of Dorkbot


Scan Google (or other) search results for vulnerabilities.

dorkbot is a modular command-line tool for performing vulnerability scans against sets of webpages returned by Google search queries or other supported sources. It is broken up into two sets of modules:

  • Indexers - modules that return a list of targets
  • Scanners - modules that perform a vulnerability scan against each target

Targets are stored in a database as they are indexed. Once scanned, a standard JSON report is produced containing any vulnerabilities found. Indexing and scanning processes can be run separately or combined in a single command (up to one of each).


$ pip3 install dorkbot wapiti3
$ dorkbot -i google_api -o key=your_api_credential_here -o engine=your_engine_id_here -o query="filetype:php inurl:id"
$ dorkbot -s wapiti


usage: dorkbot [-h] [-c CONFIG] [-r DIRECTORY] [--log LOG] [-v] [-V]
                  [-d DATABASE] [-u] [-l] [--list-unscanned]
                  [--add-target TARGET] [--delete-target TARGET]
                  [--flush-targets] [-i INDEXER] [-o INDEXER_OPTION]
                  [-s SCANNER] [-p SCANNER_OPTION] [-f] [-b BLACKLIST]
                  [--list-blacklist] [--add-blacklist-item ITEM]
                  [--delete-blacklist-item ITEM] [--flush-blacklist]

optional arguments:
  -h, --help            show this help message and exit
  -c CONFIG, --config CONFIG
                        Configuration file
  -r DIRECTORY, --directory DIRECTORY
                        Dorkbot directory (default location of db, tools,
  --log LOG             Path to log file
  -v, --verbose         Enable verbose logging (DEBUG output)
  -V, --version         Print version

  -d DATABASE, --database DATABASE
                        Database file/uri
  -u, --prune           Apply fingerprinting and blacklist without scanning

  -l, --list-targets    List targets in database
  --list-unscanned      List unscanned targets in database
  --add-target TARGET   Add a url to the target database
  --delete-target TARGET
                        Delete a url from the target database
  --flush-targets       Delete all targets

  -i INDEXER, --indexer INDEXER
                        Indexer module to use
  -o INDEXER_OPTION, --indexer-option INDEXER_OPTION
                        Pass an option to the indexer (can be used multiple

  -s SCANNER, --scanner SCANNER
                        Scanner module to use
  -p SCANNER_OPTION, --scanner-option SCANNER_OPTION
                        Pass an option to the scanner (can be used multiple

  -f, --flush-fingerprints
                        Delete all fingerprints of previously-scanned items

  -b BLACKLIST, --blacklist BLACKLIST
                        Blacklist file/uri
  --list-blacklist      List blacklist entries
  --add-blacklist-item ITEM
                        Add an ip/host/regex pattern to the blacklist
  --delete-blacklist-item ITEM
                        Delete an item from the blacklist
  --flush-blacklist     Delete all blacklist items



As needed, dorkbot will search for tools in the following order:

  • Directory specified via relevant module option
  • Located in tools directory (within current directory, by default), with the subdirectory named after the tool
  • Available in the user's PATH (e.g. installed system-wide)


All SQLite3 databases, tools, and reports are saved in the dorkbot directory, which by default is the current directory. You can force a specific directory with the --directory flag. Default file paths within this directory are as follows:

  • SQLite3 database file: dorkbot.db
  • External tools directory: tools/
  • Scan report output directory: reports/

Configuration files are by default read from ~/.config/dorkbot/ (Linux / MacOS) or in the Application Data folder (Windows), honoring $XDG_CONFIG_HOME / %APPDATA%. Default file paths within this directory are as follows:

  • Dorkbot configuration file: dorkbot.ini

Config File

The configuration file (dorkbot.ini) can be used to prepopulate certain command-line flags.

Example dorkbot.ini:



The blacklist is a list of ip addresses, hostnames, or regular expressions of url patterns that should not be scanned. If a target url matches any item in this list it will be skipped and removed from the database. By default the blacklist is stored in the dorkbot database, but a separate database or file can be specified by passing the appropriate connection uri or file path to --blacklist. Note: --add-blacklist-item / --delete-blacklist-item are not implemented for file-based blacklists, and --flush-blacklist deletes the file.

Supported external blacklists:

  • postgresql://[server info]
  • phoenixdb://[server info]
  • sqlite3:///path/to/blacklist.db
  • /path/to/blacklist.txt

Example blacklist items:


The first item will remove any target that doesn't contain a question mark, in other words any url that doesn't contain any GET parameters to test. The second attempts to avoid login functions, and the third blacklists all target urls on The fourth excludes targets with a hostname of and the fifth excludes targets whose host resolves to

Indexer Modules

(general options)

These options are applicable regardless of module chosen

  • source - label stored in source field for target, overrides label provided by module (if present and without a value during list operations, source field will be printed along with url)


Search for targets in a Google Custom Search Engine (CSE) via custom search element.

Requirements: PhantomJS


  • engine - CSE id
  • query - search query
  • phantomjs_dir - phantomjs base directory containing bin/phantomjs (default: tools/phantomjs/)
  • domain - limit searches to specified domain


Search for targets in a Google Custom Search Engine (CSE) via JSON API.

Requirements: none


  • key - API key
  • engine - CSE id
  • query - search query
  • domain - limit searches to specified domain


Search for targets within results.

Requirements: none


  • domain - pull all results for given domain or subdomain
  • index - search a specific index, e.g. CC-MAIN-2019-22 (default: latest)
  • filter - query filter to apply to the search
  • retries - number of times to retry fetching results on error (default: 10)
  • threads - number concurrent requests to (default: 10)


Search for targets within results.

Requirements: none


  • domain - pull all results for given domain or subdomain
  • filter - query filter to apply to the search
  • from - beginning timestamp
  • to - end timestamp


Search for targets via Bing Web Search API.

Requirements: none


  • key - API key
  • query - search query


Read targets from standard input, one per line.

Requirements: none

Options: none

Scanner Modules

(general options)

These options are applicable regardless of module chosen

  • report_dir - directory to save vulnerability report (default: reports/)
  • label - friendly name field to include in vulnerability report
  • count - number of urls to scan, or -1 to scan all urls (default: -1)
  • random - scan urls in random order


Scan targets with Arachni command-line scanner.

Requirements: Arachni


  • arachni_dir - arachni base directory containing bin/arachni and bin/arachni_reporter (default: tools/arachni/)
  • args - space-delimited list of additional arguments, e.g. args="--http-user-agent Dorkbot/1.0 --timeout 00:15:00"


Scan targets with Wapiti command-line scanner.

Requirements: Wapiti


  • wapiti_dir - wapiti base directory containing bin/wapiti (default: tools/wapiti/)
  • args - space-delimited list of additional arguments


The prune flag iterates through all targets, computes the fingerprints in memory, and marks subsequent matching targets as scanned. Additionally it deletes any target matching a blacklist item. The result is a database where --list-unscanned returns only scannable urls. It honors (a subset of) the options specified in SCANNER_OPTIONS as follows:

  • random - evaluate urls in random order when computing fingerprints