Skip to content

Dork Database (Atdork-DB)

AtDork ships code only — the dork data lives in the separate Atdork-DB repository, which the built-in package manager treats like a package registry.

Packages 123 dork files
Folders 31 themed @folders
Dorks 994,603 unique queries
Refresh GHDB re-synced weekly by CI

🔎 Browse the web catalog

→ https://amnottdevv.github.io/Atdork-DB/

The web catalog is the visual index of everything below:

  • Instant search across every package (s3, shodan, cve, discord, …)
  • @folder filter chips — click a category to see only its packages
  • Detail pages per package — preview of the first lines, dork count, size, sha256, raw download, and every other package in the same folder
  • One-click install commands — copy atdork install <ref> straight from the table

Every folder has its own README in the repository (generated into the catalog) and a folder page in the catalog, e.g. @shodan, @cms, @github.


5-minute workflow

0. One-time setup — clone the data repo

AtDork looks for an Atdork-DB checkout in this order (--db-repo → env ATDORK_DB_REPO → config db_repo → ~/Atdork-DB → sibling of the AtDork checkout → ./Atdork-DB):

git clone https://github.com/amnottdevv/Atdork-DB.git ~/Atdork-DB

Skip this entirely with Docker — the image bundles the database (see Docker).

1. Search the index

atdork search cve            # find packages mentioning "cve"
atdork search shodan         # all Shodan packages
atdork index                 # full package listing (ref | dorks | size | description)

2. Install packages

atdork install @cve/cve_1.txt      # canonical ref: folder + file
atdork install c@cve_1.txt         # shorthand (unique folder prefix)
atdork install @ghdb               # whole folder
atdork installed                   # what's in my store (~/.atdork/packages)?

3. Run them as queries

# Load an installed package (or any ref straight from Atdork-DB) as batch dorks
atdork --batch-file c@cve_1.txt -r 20

# Or load directly from the database root
atdork --database-dork @cve/cve_1.txt -r 20
atdork --database-dork @ghdb/01_footholds --database-preview   # show, don't run
atdork --database-dork @cms --database-r 50 --database-seed 7  # random 50 from the folder

4. Keep data fresh

atdork update     # git pull --ff-only on the Atdork-DB checkout

Package ref grammar

Ref Meaning
@cve/cve_1.txt Canonical — folder + file
c@cve_1.txt Shorthand — unique folder prefix (c → @cve)
cve_1.txt Bare file name (must be unique across the index)
@cve Whole folder (install/uninstall, or load all .txt with --database-dork)
@cve, @lfi Multiple refs, comma-separated

Lines starting with # in any dork file are comments and are skipped by the loader.


All folders

Browse any folder in the web catalog (click a name for its live folder page):

Folder Packages Dorks Theme
@crypto 9 637,139 Crypto/BTC themed harvested sets
@targets 7 11,596 Domain lists for site: scoping
@movie 3 91,733 Open directory movie listings
@network 2 99,175 Direct-IP access & server detection
@google 6 33,423 Classic large Google dork collections
@gaming 5 30,329 Gaming marketplaces & items
@cms 5 27,678 WordPress, Joomla, Magento, Laravel
@shopping 3 11,152 Shop parameter dorks
@cloud 6 10,690 S3/Azure/GCP buckets
@carding 2 3,266 E-commerce checkout parameters
@shodan 7 3,712 Shodan queries & filters
@lfi 1 7,322 Local File Inclusion parameters
@ghdb 15 7,976 Exploit-DB GHDB, weekly refresh
@rfi 1 2,866 Remote File Inclusion parameters
@duckduckgo 2 1,848 DDG-tuned dorks
@common 5 1,627 SQLi/LFI/XSS/RCE/debug classes
@iot 4 1,370 Cameras & embedded UIs
@admin 2 462 Admin login discovery
@github 5 819 GitHub secret hunting
@exploit-db 15 6,229 Exploit-DB categories mirror
@bing 2 505 Bing-only operators
@bug-bounty 2 105 Program & disclosure discovery
@sensitive 5 3,160 Exposed logs, hidden files
@censys 1 221 Censys ICS/service queries
@vuln 1 112 Banner-based vuln discovery
@virustotal 1 34 VT Intelligence queries
@cve 1 14 CVE reference hunting
@yandex 1 10 Cyrillic keyword dorks
@social 2 19 Discord/LinkedIn dorks
@onion 1 9 Dark web (.onion) discovery
@test 1 2 Reference-syntax demo

Category guides

Deep-dive pages for the most-used categories:

Also see the Package Manager feature page for ref resolution, the store layout and --db-repo details, and Docker for running everything in a container.


⚠️ Ethical use

The database is a collection of search queries, not of compromised data. Use them only against targets you own or are explicitly authorized to test (see each category page's disclaimer), and report findings responsibly.