Data Points

🌿 Subdomain

A host under a parent domain — often reveals staging, admin, and forgotten infrastructure.
Network

Sources

0
0 no-auth

Disciplines

0
that use it

Mission domains

0
reach

Workbench

native tool

🔍 Lookup

📜 Playbook — Subdomain exploitation

  1. Direction — frame the requirement for Subdomain: what decision does this support, by when?
  2. Collection — pull the 0 mapped sources (0 free) and the native workbench (open); capture provenance and observe OPSEC.
  3. Processing — normalize, de-duplicate and enrich the collected data.
  4. Analysis — correlate against local holdings; apply ACH; assign confidence.
  5. Dissemination — open a case, draft a report, share via STIX/MISP.
  6. Feedback — set an alert rule / watchlist to monitor for change.

⚡ AI Skills & Automation

🤖 Copilot brief⚡ AI SkillsResolveEnrichAuto-CollectHuntReportExport

Automate unattended via the cron pipeline (collect → ingest → resolve → enrich → score → alert).

🎫 Subdomain

A subdomain is a label prefixed to a parent domain (e.g. mail.example.com) that delegates a distinct host, service, or environment. In investigations subdomains expose an organization's attack surface, staging and admin panels, and phishing/lookalike hosts, and they inherit or diverge from the parent's hosting to reveal infrastructure structure.

Format: Dot-separated labels under a registered eTLD+1; each label <=63 chars, LDH rule; full FQDN <=253. Wildcard (*.example.com) and punycode labels valid.

📡 How it is collected

  • Certificate Transparency SAN enumeration
  • Passive DNS records
  • DNS brute-force / wordlist resolution
  • Search-engine and scraping (site: dorks)
  • Zone-transfer (AXFR) where misconfigured
  • VirusTotal / OTX relations

🧩 Analysis &amp; hunting techniques

  • CT-log passive enumeration
  • DNS brute-force with permutation wordlists
  • Dangling-CNAME subdomain-takeover detection
  • Virtual-host / co-hosting analysis
  • Wildcard-DNS filtering
  • Service fingerprinting per host
  • Staging/dev environment discovery
  • Historical resolution diffing

🔧 Tools

  • Amass
  • subfinder
  • assetfinder
  • dnsx
  • puredns
  • massdns
  • SecurityTrails
  • nuclei

⚡ Workbench actions

  • Enumerate from CT logs
  • Brute-force with wordlist
  • Resolve A/AAAA/CNAME
  • Detect dangling-CNAME takeover
  • Fingerprint running services
  • Diff against historical passive DNS
  • Screenshot live hosts
  • Map to hosting ASN

📊 Dashboard KPIs

Total subdomains discoveredLive/resolving ratioTakeover-vulnerable countNew subdomains since last scanDistinct hosting IPs/ASNs
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports

🤖 AI Copilot

🔍 Lookup & Enrich

💡 Recommendations

⚙ Automation

Cron: 0 * * * * php /home/zaptf0zdggll/public_html/threats/cron.php