Introduction to AtDork¶
Welcome to the official documentation for AtDork, a professional Open Source Intelligence (OSINT) and advanced dorking tool engineered for security researchers, penetration testers, and bug bounty hunters.
AtDork automates the extraction of exposed documents, vulnerable parameters, misconfigured server indexes, and leaked credentials from public search engine indexing.
Why AtDork?¶
Unlike conventional dorking scripts that easily trigger captchas and face IP bans, AtDork incorporates sophisticated engineering principles to guarantee high availability and evasion:
- Blazing Fast Parallelism – Highly optimized multi-threaded processing with configurable concurrency limits.
- Multi-Engine Aggregator – Queries DuckDuckGo, Google, Bing, Startpage, Yandex, Yahoo, and more.
- Ironclad Anonymity – Native Tor integration, persistent proxy rotation pools, and
--ip-guardto prevent identity leaks. - Intelligent Resilience – Built-in circuit breakers, adaptive jitter delays, and error classification algorithms.
- Seamless Pipelines – Directly pipe discovered endpoints into vulnerability scanners like
wpscanorsqlmap. - Template System – YAML-based dork collections with
{target}substitution and selective execution. - Dork Package Manager –
atdork search/install/updateover 994,600+ dorks in Atdork-DB — 123 dork packages across 31@folders, plus 7 installable@plugins/tools — all browsable in the web catalog. - Workflow Engine – Sequential multi-step dork campaigns in YAML: threshold-triggered retries, worker pools, guarded outputs, resumable state (
atdork workflow run,--run-workflow). - Plugin System – Install extra Python tools from Atdork-DB (
atdork install @plugins/<tool>), a git repo, a.pyURL or your own registry (--source); each surfaces as--<plugin>-<option>flags (--dorkbuilder-text "…"). - Watch Mode – Cron-friendly monitoring:
atdork watch add+watch runre-runs dorks and reports only new findings (webhook alerts via--notify). - Docker Ready – Official image
ghcr.io/amnottdevv/atdorkships the CLI and the full database — zero setup (Docker).
Document Layout¶
To master AtDork, explore the documentation layout based on your skill level:
- Installation – PyPI, source, Docker, and the one-time Atdork-DB setup.
- Quick Start – Run your first queries within 60 seconds.
- Basic Usage – Common commands and practical examples.
- Docker – Containerized usage, volumes, and compose.
- Dork Database – Packages, package manager, and the web catalog.
- Features – Deep dive into resilience, proxy, templates, and batch processing.
- Environment – Isolated workspaces: every result, log and cache file stays inside one root folder.
- Workflows – Sequential multi-step campaigns: thresholds, retries, workers, resume.
- Plugins – Installable tools exposed as
--<plugin>-<option>flags. - Watch Mode – Cron-friendly monitoring: report only new findings, with webhook alerts.
- CLI Reference – The full master matrix containing all 50+ configuration flags.
- Configuration – The
atdork.ymlguide: layered files, sections,${ENV}interpolation. - Engines & Providers – Scraping engines plus Serper / SerpApi / Brave Search API providers.
- Troubleshooting – Common issues and how to resolve them.
Quick Stats¶
- 994,600+ Dorks – Across 123 packages in 31 themed
@folders, refreshed weekly (web catalog). - 50+ CLI Flags – Complete control over every aspect of your search.
- 6+ Search Engines – DuckDuckGo, Google, Bing, Startpage, Yandex, Yahoo.
- 3 API Providers – Serper.dev, SerpApi and Brave Search API via
engines:inatdork.yml. - 565 Unit Tests – Production-ready stability and reliability, run on Python 3.10 / 3.12 / 3.14.
- 10+ Templates – Pre-built dork collections for SQLi, XSS, WordPress, and more.
Ethical Use
AtDork is intended for legal, authorized security testing only. You must have explicit written permission from the target owner before scanning. Unauthorized access to systems or data is strictly prohibited.
Quick Navigation¶
| Section | Description |
|---|---|
| Installation | Install via pip, source, or Docker |
| Docker | Containerized usage with the bundled database |
| Quick Start | First search in under 60 seconds |
| Basic Usage | Common commands and examples |
| Dork Database | Package manager + web catalog |
| Package Manager | search / install / update deep dive |
| Environment | Isolated workspaces — nothing written outside the root |
| Workflows | Multi-step campaigns — workflow run / --run-workflow |
| Plugins | Installable tools — --<plugin>-<option> flag system |
| Watch Mode | One-shot dork monitoring — watch run, new-findings-only alerts |
| Configuration | atdork.yml v2: sections, layering, ${ENV} interpolation |
| Engines & Providers | Built-in engines + Serper / SerpApi / Brave API providers |
| Resilience System | Circuit breakers, adaptive delays, and fallback |
| Proxy & Anonymity | Proxy pools, Tor, strict mode, IP guard |
| Vulnerability Filter | Platform detection with custom wordlists |
| Template System | YAML templates with {target} substitution |
| Batch Processing | Parallel execution and resume capability |
| Output Formats | JSON, CSV, TXT, and SQLite |
| CLI Reference | Complete flag reference (50+ flags) |
| Troubleshooting | Common issues and solutions |
Get Started¶
Ready to start? Run your first search now:
pip install atdork # install the CLI
git clone https://github.com/amnottdevv/Atdork-DB.git ~/Atdork-DB # dork data (once)
atdork -q "site:gov filetype:pdf" -r 10 # first search
Or use Docker — no Python or clone needed:
Explore the Quick Start guide for a step-by-step tutorial, browse the dork packages in the web catalog, or dive into the Dork Database workflow.