QuickStart
▶ ENVIRONMENT SETUPQuick Start Guide

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 1

Update your OS and install core build dependencies

0/3 steps
01

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.

02

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.

03

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 2

Required for Subfinder, Amass, Naabu, Nuclei, Katana, and more

0/3 steps
01

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.

02

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.

03

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 3

Required for Sherlock, Maigret, theHarvester, SpiderFoot, and more

0/3 steps
01

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.

02

Install Core Python-Based Recon Tools

Install the most widely used Python recon tools. Using pip3 install directly is acceptable for these CLI tools.

03

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 4

Optional but recommended — run tools in isolated containers

0/2 steps
01

Install Docker Engine

optional

Docker provides isolated, reproducible environments for running tools without polluting your host system. It is especially useful for tools with complex dependencies.

02

Pull Key Tool Docker Images

optional

Pre-pull Docker images for tools you plan to use frequently. This avoids delays when you first run a scan.

Final Verification

Phase 5

Confirm your environment is fully operational

0/3 steps
01

Verify All Go Tools

Run a quick version check on all installed Go-based tools.

02

Verify All Python Tools

Run a quick version check on all installed Python-based tools.

03

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.