Quick Start_
A guided, step-by-step environment setup checklist. Complete each phase in order to prepare your system for the full ReconDB toolchain. Your progress is saved automatically in your browser.
System Preparation
Phase 1Update your OS and install core build dependencies
Update & Upgrade System Packages
Ensure your package manager is up to date before installing any tools. This prevents dependency conflicts and ensures you receive the latest security patches.
Install Core Build Dependencies
These packages are required by the majority of recon tools. Installing them upfront prevents repeated dependency errors during individual tool installations.
Install pipx for Isolated Python Tools
pipx installs Python CLI tools in isolated environments, preventing dependency conflicts between tools. It is strongly recommended over installing tools globally with pip.
Go Environment
Phase 2Required for Subfinder, Amass, Naabu, Nuclei, Katana, and more
Install Go (Latest Stable)
The majority of modern recon tools are written in Go. You need Go 1.21 or later. The official binary distribution is the most reliable installation method.
Install Core Go-Based Recon Tools
Install the most widely used Go recon tools in a single batch. These will be placed in ~/go/bin which was added to your PATH in the previous step.
Update Nuclei Templates
Nuclei relies on community-maintained templates for vulnerability detection. Always update templates before running a scan to ensure you have the latest CVE and misconfiguration checks.
Python Environment
Phase 3Required for Sherlock, Maigret, theHarvester, SpiderFoot, and more
Verify Python 3.9+ is Installed
Most modern Python recon tools require Python 3.9 or later. Python 3.11 is recommended for the best compatibility.
Install Core Python-Based Recon Tools
Install the most widely used Python recon tools. Using pip3 install directly is acceptable for these CLI tools.
Clone and Install Git-Based Python Tools
Some Python tools are best installed by cloning their repositories directly. This gives you the latest version and allows easy updates via git pull.
Docker Environment
Phase 4Optional but recommended — run tools in isolated containers
Install Docker Engine
optionalDocker provides isolated, reproducible environments for running tools without polluting your host system. It is especially useful for tools with complex dependencies.
Pull Key Tool Docker Images
optionalPre-pull Docker images for tools you plan to use frequently. This avoids delays when you first run a scan.
Final Verification
Phase 5Confirm your environment is fully operational
Verify All Go Tools
Run a quick version check on all installed Go-based tools.
Verify All Python Tools
Run a quick version check on all installed Python-based tools.
Test a Live Passive Scan
Run a safe, passive scan against a public test target to confirm your toolchain is working end-to-end. Use only targets you own or that are explicitly authorized for testing.
Only scan systems you own or have explicit written permission to test. scanme.nmap.org is the only public host authorized for this purpose.