Lazyrecon : Tool To Automate Your Reconnaissance Process In An Organized Fashion

Lazyrecon is a subdomain discovery tool that finds and resolves valid subdomains then performs SSRF/LFI/SQLi fuzzing, brute-force and port scanning. It has a simple modular architecture and is optimized for speed while working with github and wayback machine.


  • Super fast asynchronous execution
  • CI/CD ready
  • HTML/pdf reports
  • Discord integration
  • Background listen server
  • Domain name, list of domains, IP, CIDR input – notations support
  • Teardown and program exit housekeeping



This script is intended to automate your reconnaissance process in an organized fashion by performing the following:

  • Creates a dated folder with recon notes for a target
  • Grabs subdomains using subfinder, assetfindergauwaybackurlsgithub-subdomains
  • Additionally finds new subdomains through alterations and permutations using dnsgen
  • Searches subnets and new assets using math Mode
  • Filters out live subdomains from a list of hosts using shuffledns
  • Checks 1-200,8000-10000 for http(s) probes using httpx
  • Gets visual part using headless chromium
  • Performs masscan on live servers
  • Scanns for known paths and CVEs using nuclei
  • Shots for SSRF/LFI/SQLi based on wayback machine’s data
  • Checks for potential request smuggling vulnerabilities using smuggler
  • Performs ffuf supercharged by interlace using custom WordList based on the top10000.txt
  • Generates report and send it to Discord

The point is to get a list of live IPs (in form of socket addresses), attack available network protocols, check for common CVEs, perform very simple directory bruteforce then use provided reports for manual research.


Linux Mac tested

Pre Requirements

python >= 3.7
pip3 >= 19.0
go >= 1.14

CI/CD way

You can use stateful/stateless build agent (worker). There is no additional time is required for provisioning. It may look tricky cause masscan/nmap/naabu root user required.

  • Fill in these required environment variables inside: ./lazyconfig:

export HOMEUSER= # your normal, non root user: e.g.: kali
export HOMEDIR= # user’s home dir e.g.: /home/kali
export STORAGEDIR= # where output saved, e.g.: ${HOMEDIR}/lazytargets
export GITHUBTOKEN=XXXXXXXXXXXXXXXXXX # a personal access token here
export DISCORDWEBHOOKURL= #{}/{webhook.token}
export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin:$GOROOT/bin:$HOME/.local/bin:$HOME/go/bin:$HOMEDIR/go/bin
export GO111MODULE=on

  • Enable new environment source ./lazyconfig
  • Call sudo -E ./
  • Execute sudo -E ./ ""

Github Actions way

Customize .github/workflows/test-recon-action.yaml using DISCORDWEBHOOKURL and GITHUBTOKEN secrets, enable --discord to receive a report

– name: Install & Recon
run: |
export STORAGEDIR=”${HOMEDIR}”/lazytargets
sudo -E ./
sudo -E ./ “” –quiet –discord

Hard way

Config your environment variables and dependencies using INSTALL.MD

If you faced with some issues, feel free to join Discord, open PR or file the bug.


Execute with sudo because of masscan:

▶ sudo -E ./ –wildcard

–wildcardSubdomains reconnaissance ‘*’ (default)./ –wildcard
–singleOne target instance ‘’./ –single
–ipSingle IP of the target machine./ –single –ip
–listList of subdomains to process for./ “./testa.txt” –list
–cidrPerform network recon, CIDR notation./ “” –cidr
–madWayback machine’s stuff./ –mad
–fuzzSSRF/LFI/SQLi fuzzing./ –mad –fuzz
–altAdditionally permutate subdomains (* only)./ –wildcard –alt
–bruteBasic directory bruteforce (time sensitive)./ –single –brute
–discordSend notifications to discord./ –discord
–quietEnable quiet mode./ –quiet


  • Use dnsperftest to know your best resolvers
  • Run ./
  • Check output reports of chromium, nuclei, masscan, server_log, ssrf, lfi
  • Explore file upload vulnerabilities
  • Perform Google, Trello, Atlassian, Github, Bitbucket dorking
  • Check JS sources for credentials, API endpoints
  • Investigate XHR requests, fuzz parameters and variables
  • Check for target-specific CVE
  • GET/POST Bruteforce for directories: fuzbo0oM-top10000 –> raft –> target specific
  • Continue bruteforcing using custom Headers (X-Custom-IP-Authorization:; X-Original-URL:)
  • Try bypass 401/403 errors using notable methods (%23/%2e/ etc)
  • Look for XSS or XSSTRON