The idea
A port scan tells me a service exists; footprinting tells me what it will give up. The goal is to turn "445 is open" into usernames, shares, versions and misconfigurations I can act on. Each protocol has its own questions worth asking.
How I work through it
SMB — list shares and look for anonymous or guest access, then spider anything readable:
smbclient -L //10.10.10.10 -N
nxc smb 10.10.10.10 -u '' -p '' --shares
SNMP — a public community string often leaks processes, users and network config:
snmpwalk -v2c -c public 10.10.10.10
DNS — always try a zone transfer; when it works it hands over the whole internal map:
dig axfr internal.local @10.10.10.10
FTP — check for anonymous login and browse for config or backup files. For databases (MySQL, MSSQL), I note the version and test default credentials before anything else.
Pitfalls I watch for
- Enumerate with and without credentials. Guest SMB access often shows far more than anonymous, and the difference is easy to miss.
- Banner versions are a lead, not proof. I confirm a version maps to a real, exploitable issue before committing time to it.
- Keep a running list of every username and hostname found — these feed password spraying and Active Directory attacks later.
Takeaway
Footprinting is methodical, not clever: ask each service the standard questions, record every scrap of identity data, and the attack path usually reveals itself.