1. Footprint sweep
In an authorized engagement, theHarvester collects publicly indexed emails and hosts for a domain to show what the organization already exposes.
theHarvester -d example.com -b allTyporithm · medium
Step 1 of 8 · intro card
Corporate Footprint
In an authorized assessment, security teams map an organization's public footprint — its email naming pattern and publicly listed roles — using theHarvester and hunter.io. The point is to measure what the org leaks and harden it, never to target individuals.
An organization's public footprint is everything an outsider can learn without any access: indexed email addresses, the naming convention behind them, and the roles people publish about themselves. theHarvester sweeps public sources for a domain to surface this.
The email pattern matters most. Once first.last@example.com is known, every address becomes predictable, which is exactly what phishing-awareness testing is designed to defend against. Aggregators like hunter.io and phonebook.cz show how widely that data is already exposed.
This is strictly an authorized, defensive activity scoped to the organization. The deliverable is a hardening report — trim oversharing, brief staff, tighten what is published — not a list used to single out or harass any individual.
theHarvester maps a domain's public emails and hosts.
The email naming pattern makes every address predictable.
Use it to harden the org, never to target people.
theHarvester -d example.com -b all
# email pattern: first.last@example.com
# hunter.io and phonebook.cz
# public employee roles from sitesConnect each part of the code to the concept before you type.
In an authorized engagement, theHarvester collects publicly indexed emails and hosts for a domain to show what the organization already exposes.
theHarvester -d example.com -b allSpotting the org's email convention is what awareness testing hardens — once known, the format is predictable for everyone.
# email pattern: first.last@example.comhunter.io and phonebook.cz aggregate publicly listed addresses, measuring how much contact data the organization leaks.
# hunter.io and phonebook.czPublic role listings reveal org structure; the defensive goal is to reduce oversharing, not to single out any person.
# public employee roles from sitesRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.