Performing Subdomain Enumeration With Subfinder
Overview
Cybersecurity skill for performing subdomain enumeration with subfinder. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing subdomain enumeration with subfinder"
"Enumerate subdomains of target domains using ProjectDiscovery's Subfinder passiv"
During the reconnaissance phase of penetration testing or bug bounty hunting
When mapping the external attack surface of a target organization
Before performing vulnerability scanning on discovered subdomains
When building an asset inventory for continuous security monitoring
During red team engagements requiring passive information gathering
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Go 1.21+ installed for building from source
- Subfinder v2 installed (
go install -v github.com/projectdiscovery/subfinder/v2/cmd/subfinder@latest)
- API keys configured for passive sources (Shodan, Censys, VirusTotal, SecurityTrails, Chaos)
- Provider configuration file at
$HOME/.config/subfinder/provider-config.yaml
- Network access to passive DNS and certificate transparency sources
- httpx or httprobe for validating discovered subdomains
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for subdomain enumeration operations.
- Prepare Environment — Set up tools, access, and data sources required for subdomain enumeration.
- Execute Core Workflow — Use subfinder to perform subdomain enumeration operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- subfinder — Primary tool for this skill
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-subdomain-enumeration-with-subfinder3description: Use when enumerate subdomains of target domains using ProjectDiscovery's4 Subfinder passive reconnaissance tool to map the attack surface during security5 assessments. Use when working with performing subdomain enumeration with subfinder.6domain: cybersecurity7tags:8- subdomain-enumeration9- reconnaissance10- bug-bounty11- attack-surface12- subfinder13- passive-recon14- osint15subdomain: web-application-security16version: '1.0'17author: oyi7718license: Apache-2.019nist_csf:20- PR.PS-0121- ID.RA-0122- PR.DS-1023- DE.CM-0124category: cybersecurity25metadata:26 source: https://skillmd.com/skills/oyi77/performing-subdomain-enumeration-with-subfinder27---2829# Performing Subdomain Enumeration With Subfinder3031## Overview3233Cybersecurity skill for performing subdomain enumeration with subfinder. Follows industry best practices and security standards.3435## When to Use36**Trigger phrases:**37- "performing subdomain enumeration with subfinder"38- "Enumerate subdomains of target domains using ProjectDiscovery's Subfinder passiv"3940- During the reconnaissance phase of penetration testing or bug bounty hunting41- When mapping the external attack surface of a target organization42- Before performing vulnerability scanning on discovered subdomains43- When building an asset inventory for continuous security monitoring44- During red team engagements requiring passive information gathering454647## When NOT to Use4849- When you lack proper authorization for testing50- For production systems without change management51- When the task requires legal or compliance expertise beyond technical scope525354## Prerequisites55- Go 1.21+ installed for building from source56- Subfinder v2 installed (`go install -v github.com/projectdiscovery/subfinder/v2/cmd/subfinder@latest`)57- API keys configured for passive sources (Shodan, Censys, VirusTotal, SecurityTrails, Chaos)58- Provider configuration file at `$HOME/.config/subfinder/provider-config.yaml`59- Network access to passive DNS and certificate transparency sources60- httpx or httprobe for validating discovered subdomains6162## Workflow6364```python65# Example: IOC detection66import re6768IOC_PATTERNS = {69 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",70 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",71 "hash_md5": r"\b[a-f0-9]{32}\b",72 "hash_sha256": r"\b[a-f0-9]{64}\b",73}7475def extract_iocs(text: str) -> dict:76 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}77```78791. **Plan Operations** — Define objectives, scope, and success criteria for subdomain enumeration operations.802. **Prepare Environment** — Set up tools, access, and data sources required for subdomain enumeration.813. **Execute Core Workflow** — Use subfinder to perform subdomain enumeration operations following established procedures.824. **Validate Results** — Verify that results meet quality standards and objectives.835. **Report Findings** — Document results, observations, and recommendations.846. **Follow Up** — Track remediation actions and verify fixes where applicable.8586## Tools8788- **subfinder** — Primary tool for this skill89- **Analysis Platform** — Data processing and visualization90- **Collaboration Tools** — Team coordination and knowledge sharing919293## Process94951. **Design** — Define interface, identify patterns, plan implementation961. **Implement** — Write code following existing conventions, add tests971. **Verify** — Run tests, check integration, validate behavior9899## Verification100101- [ ] All subdomain enumeration procedures executed completely and documented102- [ ] Findings validated against multiple data sources103- [ ] False positives identified and filtered104- [ ] Results documented with evidence and timestamps105- [ ] Recommendations provided with risk-based prioritization106107## Anti-Rationalization Table108109| Rationalization | Reality |110|---|---|111| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |112| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |113| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |