Repository navigation
DomainRecon AgentFlow
AnythingLLM AgentFlow for automated domain reconnaissance - performs passive DNS enumeration, WHOIS lookup, certificate transparency search, and web technology fingerprinting on a target domain.
Accepts a domain name, runs passive recon via public sources (crt.sh, WHOIS, Shodan, DNS records), and returns: subdomains, IP ranges, hosting providers, SSL certificate history, MX/SPF/DMARC configuration, and web tech stack.
Build a complete passive domain intelligence picture as the first step in an authorized engagement's reconnaissance phase.
Starting recon on an authorized target domain; identifying attack surface before active scanning; populating the target profile for scoping decisions.
Name: DomainRecon
Description:
Performs comprehensive domain reconnaissance including subdomains, DNS records,
certificates, and historical data for attack surface mapping.
Purpose: Map complete attack surface and discover hidden assets
Define these variables in the "Flow Variables" section:
| Variable Name | Initial Value | Description |
|---|---|---|
domain |
(empty) | Target domain (e.g., example.com) |
cert_data |
(empty) | Certificate transparency data |
subdomain_data |
(empty) | Discovered subdomains |
security_headers |
(empty) | Security headers analysis |
whois_data |
(empty) | WHOIS registration data |
recon_report |
(empty) | Final reconnaissance report |
Block Type: Web Scraping
Configuration:
-
URL:
https://crt.sh/?q=%.${domain} - Capture Page Content As: Text content only
- Content Summarization: Enabled
-
Result Variable:
cert_data
Purpose: Discover subdomains via SSL certificate logs
Note: crt.sh provides certificate transparency logs showing all issued certificates
Block Type: Web Scraping
Configuration:
-
URL:
https://viewdns.info/reverseip/?host=${domain}&t=1 - Capture Page Content As: Text content only
- Content Summarization: Enabled
-
Result Variable:
subdomain_data
Purpose: Find other domains hosted on same IP address
Block Type: Web Scraping
Configuration:
-
URL:
https://securityheaders.com/?q=https://${domain}&hide=on&followRedirects=on - Capture Page Content As: Text content only
- Content Summarization: Enabled
-
Result Variable:
security_headers
Purpose: Analyze security posture via HTTP headers
Block Type: Web Scraping
Configuration:
-
URL:
https://www.whois.com/whois/${domain} - Capture Page Content As: Text content only
- Content Summarization: Enabled
-
Result Variable:
whois_data
Purpose: Gather domain registration information
Alternative (API): If you have WhoisXML API key:
- Method: GET
-
URL:
https://www.whoisxmlapi.com/whoisserver/WhoisService?apiKey=YOUR_KEY&domainName=${domain}&outputFormat=JSON
Block Type: LLM Instruction
Instruction:
Analyze comprehensive domain reconnaissance for ${domain}:
Certificate Transparency Data: ${cert_data}
Reverse IP Data: ${subdomain_data}
Security Headers: ${security_headers}
WHOIS Information: ${whois_data}
Extract and organize:
## Subdomains Discovered
List all discovered subdomains with categorization:
- Production subdomains
- Development/staging environments (dev, test, staging, uat)
- Administrative interfaces (admin, panel, dashboard)
- API endpoints
- Mail servers
- Other interesting targets
## IP Addresses & Hosting
- Primary IP addresses
- Hosting provider identification
- Geographic location
- Shared hosting information
- CDN usage
## Security Posture
- Security headers present/missing
- SSL/TLS configuration quality
- Certificate authorities used
- Expired or wildcard certificates
- HSTS, CSP, X-Frame-Options analysis
## Domain Registration
- Registrar information
- Registration and expiration dates
- Nameservers
- Registrant details (if public)
- Privacy protection status
## Attack Surface Assessment
- High-priority targets (admin panels, dev sites)
- Potential information disclosure
- Misconfigured services
- Outdated or vulnerable technologies
## Recommendations
- Prioritized list of targets for further testing
- Suggested reconnaissance tools
- Next steps in assessment
Format as professional reconnaissance report.
Result Variable: recon_report
Purpose: Synthesize all reconnaissance data into actionable intelligence
Block Type: Flow Complete
Configuration:
- Flow will end here and return results
@agent use DomainRecon flow
domain: target.com
@agent use DomainRecon flow
domain: example.com
Note: Do NOT include "www." or "https://" - just the domain name
The flow will return recon_report containing:
- Complete list of discovered subdomains
- IP addresses and hosting information
- Security posture assessment
- Domain registration details
- Prioritized attack surface mapping
- Recommended next steps
Typical Workflow:
- CompanyOSINT - Gather company intelligence
- DomainRecon (this flow) - Map technical infrastructure
- ThreatIntelCheck - Verify discovered IPs
- NmapAnalyzer - Scan discovered subdomains
- CVELookup - Research vulnerabilities in discovered services
-
https://crt.sh/?q=%.${domain}&output=json(JSON format) -
https://transparencyreport.google.com/https/certificates(manual lookup)
-
https://api.hackertarget.com/hostsearch/?q=${domain}(API, free tier) -
- discontinued: Rapid7 revoked public access to the underlying dataset and the omnisint API was shut down; usehttps://sonar.omnisint.io/subdomains/${domain}(Project Sonar)crt.shor the HackerTarget API above instead
- Manual check:
curl -I https://${domain} -
https://observatory.mozilla.org/analyze/${domain}(Mozilla Observatory)
โ ๏ธ Reconnaissance must be authorized- Certificate transparency logs are public data
- Respect rate limits on free services
- Some WHOIS data may be privacy-protected
- Rate Limiting: Free services may throttle requests
-
Variable Syntax: Use
${domain}not{{domain}} - Content Size: Certificate logs can be large; summarization recommended
- Timeout: Allow 30-60 seconds per web scraping block
- Best Results: Well-established domains with history
- Limited Results: New domains or privacy-focused organizations
- False Positives: Certificate logs may show expired/unused domains
-
Combine Multiple Sources:
- crt.sh for certificate-based discovery
- ViewDNS for reverse IP lookup
- HackerTarget API for DNS enumeration
-
Follow Up with Active Scanning:
# After flow completes, scan discovered subdomains for subdomain in $(cat discovered-subdomains.txt); do nmap -sV $subdomain done
-
Check for Wildcard DNS:
- Test random subdomains to detect wildcards
- Filter out false positives
-
Prioritize Development Environments:
- dev., staging., test., uat.
- Often less secured than production
-
Focus on Administrative Interfaces:
- admin., panel., dashboard.*
- cpanel., webmail.
- Higher value targets
-
Identify Technology Stack:
- Look for technology-specific subdomains
- jenkins., gitlab., jira.*
| Issue | Solution |
|---|---|
| No subdomains found | Domain may be new; try alternative sources |
| crt.sh returns too much data | Enable summarization; filter by recent certs |
| WHOIS data redacted | Expected for privacy-protected domains |
| Security headers fail | Domain may not exist; check manually first |
| Variable not substituting | Verify syntax: ${domain} in URL field |
| Web scraping timeout | Increase timeout or try API alternatives |
If you have API keys, replace web scraping blocks:
SecurityTrails API (Subdomain Discovery):
Block Type: API Call
Method: GET
URL: https://api.securitytrails.com/v1/domain/${domain}/subdomains
Headers: {
"APIKEY": "YOUR_SECURITYTRAILS_KEY"
}
Result Variable: subdomain_data
WhoisXML API (Better WHOIS Data):
Block Type: API Call
Method: GET
URL: https://www.whoisxmlapi.com/whoisserver/WhoisService?apiKey=YOUR_KEY&domainName=${domain}&outputFormat=JSON
Result Variable: whois_data
After running DomainRecon:
- Export discovered subdomains to file for further scanning
- Run ThreatIntelCheck on discovered IP addresses
- Scan high-priority targets with Nmap
- Check development environments for exposed information
- Document findings for client report
- v1.0 - Initial flow creation with web scraping
- v1.1 - Added security headers analysis (recommended)
- Purpose: Attack surface mapping and subdomain discovery
- Last Updated: November 2025
- CompanyOSINT - Company intelligence gathering
- ThreatIntelCheck - IP reputation checking
- NmapAnalyzer - Port scanning discovered assets
- GitHubSecrets - Code repository investigation
- README.md - AnythingLLM AgentFlow index
- flow-company_osint.md - Company-level context for discovered domains
- flow-email_osint.md - Email OSINT on contacts from this domain
- anything_llm_agentflows.md - DomainRecon is the standard first step in the recon chain
๐ Source: AI/AnythingLLM/flow-domain_recon.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Artificial Intelligence
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics