SUBFINDER: COLLECT PUBLISHED SUBDOMAINS FOR A DOMAIN YOU OPERATE
A passive subfinder pass on a domain you operate: which sources need keys, what a published name is not, and how a later dnsx lookup stays polite and in scope.
EST_TIME: 40 MIN
PHASES: 5
Ticks last until you refresh. This page does not keep a score.
Names a passive source has already published
The job is a list of subdomains that passive sources already associate with a domain you operate. Each name stays attached to the dataset that returned it. You stop when the note can say which binary ran, which flags stayed off, and which names you are willing to repeat. A longer list is not the finish line.
ProjectDiscovery subfinder is the tool. The README at tag v2.17.0, published 8 October 2026, calls it a subdomain discovery tool that returns valid subdomains for websites using passive online sources, and says it is built for passive subdomain enumeration. The same README's feature list also advertises resolution and wildcard-elimination modules. Both sentences are in the file on purpose. This lesson is the passive half. Resolution is a second question, asked later, and only of names that sit on a domain you operate.
"Valid", in that README sentence, is the tool's word. With the active flag off, a name in the output is a string a source returned. It is not proof the name resolves, that a website answers, or that you are allowed to treat the host as yours. The v2.17.0 help text is where the second half of the tool shows itself. -nW and -active are documented there as "display active subdomains only." -t is "number of concurrent goroutines for resolving (-active only)" with a default of 10. -oI and -ip are "include host IP in output (-active only)." Those flags are how a passive binary starts talking to DNS. This lesson leaves them off, so the published list and any later lookup stay in separate notes.
The licence file at that tag is MIT, copyright 2021 ProjectDiscovery, Inc. Running the binary for this exercise is ordinary use of the tool. A modified copy you ship later has to keep the copyright and permission notice. The README also points at DISCLAIMER.md. That file, at the same tag, says the tool is for research or internal work, and that a commercial use has to agree to the terms of the services it leverages. The disclaimer names Bufferover, CommonCrawl, certspotter, crt.name, dnsdumpster, Google Transparency, Alienvault, and Subdomain Center. That is a list of parties whose terms the project told you to read. It is not the full source catalogue, and it is not a finding about your domain.
The running page on the ProjectDiscovery docs, read for this lesson, shows a banner along the lines of "Use with caution. You are responsible for your actions" and "By using subfinder, you also agree to the terms of the APIs used." The sample on that page was labelled v2.4.9 and was aimed at a real company's domain. The banner is the part worth keeping. The domain in the sample is not. Do not copy a target out of upstream documentation. If your banner reads differently, quote the one your binary printed.
Flags move. The v2.17.0 README prints a help block and then tells you to run subfinder -h. Where this lesson and your help text disagree, -h wins, and so does subfinder -version. A cheatsheet that cannot name its build is a souvenir. The release notes for v2.17.0 added the passive sources crtname and subdomaincenter, added -match-regex and -filter-regex, and fixed a bug that dropped names reported with uppercase letters or a trailing dot. An older binary can therefore omit a real string for a boring parsing reason. Write the version down before you brief the gap.
@latest moves as well. The README's install line is go install -v github.com/projectdiscovery/subfinder/v2/cmd/subfinder@latest, and it says that line wants Go 1.26. The install page, read the same day, says the tool wants the latest Go and does not pin 1.26. If those two pages still disagree when you install, the page in front of you wins. The release this lesson checked is v2.17.0. If the module has moved past that tag, your -version output is the number in the note.
The useful line is a name, the source that published it, and the version that printed it. Volume is how a passive exercise starts sounding like a map of the company.