Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Recon-DNSSubdomainWordlistEnumeration.
Upgrade to ProDetect DNS Subdomain Wordlist Brute-Force Enumeration in CrowdStrike LogScale
Adversaries iteratively query an organization's authoritative or recursive DNS infrastructure with large wordlists of candidate subdomain labels (dev, staging, vpn, mail-old, api-internal, etc.) to discover hostnames that were never intentionally published — forgotten staging environments, internal-only services accidentally exposed, or third-party integrations. Unlike the HTTP directory/file wordlist scanning covered by generic Active Scanning detections, this technique operates entirely at the DNS layer using tools such as massdns, puredns, gobuster's dns mode, dnsrecon, fierce, and amass's active enumeration mode, which resolve thousands of candidate FQDNs per minute and rely on the high NXDOMAIN response rate as an intrinsic side effect of brute-forcing an unknown namespace. Because these queries never touch a web server or generate an HTTP log line, they are invisible to WAF- and web-access-log-based scanning detections and require dedicated visibility into DNS server query logs (authoritative nameserver, recursive resolver, or DNS security gateway) plus endpoint process telemetry for internal pivot scanning.
MITRE ATT&CK
- Tactic
- Reconnaissance
LogScale Detection Query
#event_simpleName=ProcessRollup2
| FileName=/(?i)(massdns|gobuster|puredns|dnsrecon|fierce|amass|dnsx|altdns)/
| Signal := "InternalDNSEnumTool"
| groupBy([ComputerName, UserName, FileName, CommandLine], function=[count(as=EventCount)])
| sort(EventCount, order=desc)
// Companion search for DNS-server-side NXDOMAIN volume (requires DNS log source ingested to LogScale):
// #event_simpleName=DnsQueryLog ResponseCode=NXDOMAIN
// | groupBy([SourceIp, BaseDomain], function=[count(as=NxDomainCount), collect(QueriedFqdn)])
// | test(NxDomainCount >= 50)CrowdStrike LogScale query over ProcessRollup2 endpoint telemetry detecting execution of named DNS subdomain enumeration tools (massdns, gobuster, puredns, dnsrecon, fierce, amass, dnsx, altdns). A companion search (commented) aggregates NXDOMAIN volume per source from a DNS query log source ingested into LogScale for the network-layer confirmation branch, since Falcon endpoint telemetry alone does not capture DNS server response codes.
Data Sources
Required Tables
False Positives & Tuning
- Security engineering or ASM vendors running authorized subdomain discovery tooling
- Approved red team engagements actively enumerating the DNS namespace
Other platforms for THREAT-Recon-DNSSubdomainWordlistEnumeration
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulated DNS Subdomain Wordlist Query Burst
Expected signal: Authoritative/recursive DNS server query log entries showing 60 sequential NXDOMAIN responses for distinct subdomains of example.com from the executing host's source IP within a short window.
- Test 2gobuster DNS Mode Execution
Expected signal: Process creation event for gobuster with CommandLine containing 'dns -d example.com -w' and the wordlist file path.
- Test 3massdns Bulk Subdomain Resolution
Expected signal: Process creation event for massdns with CommandLine containing '-r' and '-t A' flags; DNS query log entries for the listed candidate subdomains.
Unlock playbooks & atomic tests with Pro
Get the full detection package for THREAT-Recon-DNSSubdomainWordlistEnumeration — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month