ankur@sec:~$

$ ls ~/tools

Tools

Sorted in the order an attacker uses them: first public data, then mapping, then testing. The last group is for you - fixing it at the source.

⚠ Recon your own assets, or targets you have written permission to test. Passive OSINT reads public data, but using it to target someone else's systems can still be illegal or against their terms. Examples on this site use example.com placeholders.

## osint / recon

Public data only. This is what an attacker learns before sending a single packet to you.

## map the surface

Light, active checks: which hosts are alive, which ports are open, what they say about themselves.

## test it

Actively looking for vulnerabilities. Your own apps or written permission only.

## fix at source

Run on your own code, configs and images - before anything reaches the internet.

Many of these are picked from awesome-security (MIT, © sbilly) - checked for active maintenance in November 2026. Each tool page says where it came from. See credits.