Skip to main content
The D0pam1ne engine is the open-source heart of D0pam1ne: a self-contained terminal application that takes a target from first scope to a one-page report, entirely from the command line. It is free, it runs standalone, and it is the same engine D0pam1ne Pro runs under the hood. Nothing in Pro bypasses it.
The D0pam1ne engine welcome screen

Press Enter to launch: the engine remembers your last project, scope and run

Built for red teamers, bug bounty hunters and cybersecurity practitioners, the engine fuses a fast, modular recon pipeline, a scope guard that never lets a tool stray, and an attack toolkit that turns what recon found into ready-to-run commands. One registry drives all of it, so the toolchain is identical whether you work from the terminal or from the Pro web app.

​
The main menu

Launch d0pam1ne and you land in the console: your project and scope on the left, the menu in the middle, and a plain-language explanation of whatever is selected on the right. Everything is one keystroke away, and nothing runs until you choose it.
The D0pam1ne engine main menu

Project and scope, the menu, and what each action does, side by side

​
The shape of a run

Every engagement is the same shape: a project carries the client and scope, a profile sets how fast or quiet to go, recon walks an ordered pipeline of stages, and everything lands in one run folder as lists, JSON and a report.
The D0pam1ne flow: project and scope, recon, results, attack toolkit

Project and scope, to recon, to results and report, to the attack toolkit

1

Scope guard

Every target is checked against the project’s in-scope and out-of-scope rules before any tool touches it. Out of scope always wins, and anything refused is written down with the reason, never probed. See Client and scope.
2

Profile

One of fast, stealth, normal or deep sets the pacing, concurrency, wordlist sizes and time limits for the whole run. See Recon profiles.
3

Pipeline

Fifteen ordered stages, from subdomains to JavaScript secrets, each running only the tools that apply and that are installed. See The recon pipeline.
4

Results and report

Each stage writes its files into the run folder. The results browser shows them live, and a one-page HTML report is named after the client. See Results and report.
5

Attack toolkit

When recon is done, the attack toolkit turns the findings into in-scope target lists and tested commands you run by hand. See The attack toolkit.

​
Three ways to drive it

Interactive console

Run d0pam1ne with no arguments for the guided, menu-driven session you see above: pick a project, run recon, read results, open the attack toolkit.

The CLI

Scriptable subcommands for every action: recon, attack, project, tools, scope, doctor. Built for automation and CI. See the CLI reference.

D0pam1ne Pro

Pro runs this same engine and streams its live events into a multi-user web app, adding attack orchestration, OSINT, AI triage and client reporting.

​
Key building blocks

A project is one engagement: a client, a scope, per-tool settings and its recon runs. Create, switch and edit them from the menu or with d0pam1ne project new|list|edit|use|show. The current project is the default target of recon, attack and results.
Editing a project in the D0pam1ne engine

Editing a project: name, client, engagement type, rules of engagement and scope

The scope guard supports exact domains, *.wildcards, single IPs, CIDR ranges, and path or port limited web rules. A path-limited host is crawled and probed only within its allowed URLs and is never port scanned. Every tool’s input and output passes through it. Full detail in Client and scope.
A profile sets the run-wide pacing. Per-project project settings --set tool.key=value overrides individual tool behavior (for example naabu.ports=full, katana.depth=3, gau.enabled=off). The two are merged for each run. See Recon profiles.
One registry lists every tool, what it does, how to find it and how to install it (Homebrew, apt, go, pip, cargo or git). d0pam1ne doctor checks the system and every tool against the latest release; d0pam1ne tools update brings them current. See the full tool reference.
The d0pam1ne doctor output

d0pam1ne doctor: system dependencies and every tool, core, optional or built-in

Updating tools in the D0pam1ne engine

Updating the toolchain, streamed live as each tool is checked and built

Active discovery uses SecLists. The engine finds an existing copy ($D0P_SECLISTS, /usr/share/seclists, Homebrew) or installs its own, and each profile picks the wordlist size that fits. See Wordlists.
The engine is open source and runs standalone from the terminal. D0pam1ne Pro adds the multi-user web app, attack orchestration, OSINT, triage and local-AI reporting on top of this same core. See Free engine and Pro, and support the project by starring the engine on GitHub.