Domain Intelligence — Passive OSINT
Passive domain reconnaissance using only Python stdlib.
Zero dependencies. Zero API keys. Works on Linux, macOS, and Windows.
Helper script
This skill includes scripts/domain_intel.py — a complete CLI tool for all domain intelligence operations.
# Subdomain discovery via Certificate Transparency logs
python3 SKILL_DIR/scripts/domain_intel.py subdomains example.com
# SSL certificate inspection (expiry, cipher, SANs, issuer)
python3 SKILL_DIR/scripts/domain_intel.py ssl example.com
# WHOIS lookup (registrar, dates, name servers — 100+ TLDs)
python3 SKILL_DIR/scripts/domain_intel.py whois example.com
# DNS records (A, AAAA, MX, NS, TXT, CNAME)
python3 SKILL_DIR/scripts/domain_intel.py dns example.com
# Domain availability check (passive: DNS + WHOIS + SSL signals)
python3 SKILL_DIR/scripts/domain_intel.py available coolstartup.io
# Bulk analysis — multiple domains, multiple checks in parallel
python3 SKILL_DIR/scripts/domain_intel.py bulk example.com github.com google.com
python3 SKILL_DIR/scripts/domain_intel.py bulk example.com github.com --checks ssl,dns
SKILL_DIR is the directory containing this SKILL.md file. All output is structured JSON.
Available commands
| Command |
What it does |
Data source |
subdomains |
Find subdomains from certificate logs |
crt.sh (HTTPS) |
ssl |
Inspect TLS certificate details |
Direct TCP:443 to target |
whois |
Registration info, registrar, dates |
WHOIS servers (TCP:43) |
dns |
A, AAAA, MX, NS, TXT, CNAME records |
System DNS + Google DoH |
available |
Check if domain is registered |
DNS + WHOIS + SSL signals |
bulk |
Run multiple checks on multiple domains |
All of the above |
When to use this vs built-in tools
- Use this skill for infrastructure questions: subdomains, SSL certs, WHOIS, DNS records, availability
- Use
WebSearch for general research about what a domain/company does
- Use
WebFetch to get the actual content of a webpage
- Use
Bash with curl -I for a simple "is this URL reachable" check
| Task |
Better tool |
Why |
| "What does example.com do?" |
WebFetch |
Gets page content, not DNS/WHOIS data |
| "Find info about a company" |
WebSearch |
General research, not domain-specific |
| "Is this website safe?" |
WebSearch |
Reputation checks need web context |
| "Check if a URL is reachable" |
Bash with curl -I |
Simple HTTP check |
| "Find subdomains of X" |
This skill |
Only passive source for this |
| "When does the SSL cert expire?" |
This skill |
Built-in tools can't inspect TLS |
| "Who registered this domain?" |
This skill |
WHOIS data not in web search |
| "Is coolstartup.io available?" |
This skill |
Passive availability via DNS+WHOIS+SSL |
Platform compatibility
Pure Python stdlib (socket, ssl, urllib, json, concurrent.futures).
Works identically on Linux, macOS, and Windows with no dependencies.
- crt.sh queries use HTTPS (port 443) — works behind most firewalls
- WHOIS queries use TCP port 43 — may be blocked on restrictive networks
- DNS queries use Google DoH (HTTPS) for MX/NS/TXT — firewall-friendly
- SSL checks connect to the target on port 443 — the only "active" operation
Data sources
All queries are passive — no port scanning, no vulnerability testing:
- crt.sh — Certificate Transparency logs (subdomain discovery, HTTPS only)
- WHOIS servers — Direct TCP to 100+ authoritative TLD registrars
- Google DNS-over-HTTPS — MX, NS, TXT, CNAME resolution (firewall-friendly)
- System DNS — A/AAAA record resolution
- SSL check is the only "active" operation (TCP connection to target:443)
Notes
- WHOIS queries use TCP port 43 — may be blocked on restrictive networks
- Some WHOIS servers redact registrant info (GDPR) — mention this to the user
- crt.sh can be slow for very popular domains (thousands of certs) — set reasonable expectations
- The availability check is heuristic-based (3 passive signals) — not authoritative like a registrar API
Contributed by @FurkanL0
1---2name: domain-intel3description: Passive domain reconnaissance using Python stdlib. Subdomain discovery, SSL certificate inspection, WHOIS lookups, DNS records, domain availability checks, and bulk multi-domain analysis. No API keys required.4---56# Domain Intelligence — Passive OSINT78Passive domain reconnaissance using only Python stdlib.9**Zero dependencies. Zero API keys. Works on Linux, macOS, and Windows.**1011## Helper script1213This skill includes `scripts/domain_intel.py` — a complete CLI tool for all domain intelligence operations.1415```bash16# Subdomain discovery via Certificate Transparency logs17python3 SKILL_DIR/scripts/domain_intel.py subdomains example.com1819# SSL certificate inspection (expiry, cipher, SANs, issuer)20python3 SKILL_DIR/scripts/domain_intel.py ssl example.com2122# WHOIS lookup (registrar, dates, name servers — 100+ TLDs)23python3 SKILL_DIR/scripts/domain_intel.py whois example.com2425# DNS records (A, AAAA, MX, NS, TXT, CNAME)26python3 SKILL_DIR/scripts/domain_intel.py dns example.com2728# Domain availability check (passive: DNS + WHOIS + SSL signals)29python3 SKILL_DIR/scripts/domain_intel.py available coolstartup.io3031# Bulk analysis — multiple domains, multiple checks in parallel32python3 SKILL_DIR/scripts/domain_intel.py bulk example.com github.com google.com33python3 SKILL_DIR/scripts/domain_intel.py bulk example.com github.com --checks ssl,dns34```3536`SKILL_DIR` is the directory containing this SKILL.md file. All output is structured JSON.3738## Available commands3940| Command | What it does | Data source |41|---------|-------------|-------------|42| `subdomains` | Find subdomains from certificate logs | crt.sh (HTTPS) |43| `ssl` | Inspect TLS certificate details | Direct TCP:443 to target |44| `whois` | Registration info, registrar, dates | WHOIS servers (TCP:43) |45| `dns` | A, AAAA, MX, NS, TXT, CNAME records | System DNS + Google DoH |46| `available` | Check if domain is registered | DNS + WHOIS + SSL signals |47| `bulk` | Run multiple checks on multiple domains | All of the above |4849## When to use this vs built-in tools5051- **Use this skill** for infrastructure questions: subdomains, SSL certs, WHOIS, DNS records, availability52- **Use `WebSearch`** for general research about what a domain/company does53- **Use `WebFetch`** to get the actual content of a webpage54- **Use `Bash` with `curl -I`** for a simple "is this URL reachable" check5556| Task | Better tool | Why |57|------|-------------|-----|58| "What does example.com do?" | `WebFetch` | Gets page content, not DNS/WHOIS data |59| "Find info about a company" | `WebSearch` | General research, not domain-specific |60| "Is this website safe?" | `WebSearch` | Reputation checks need web context |61| "Check if a URL is reachable" | `Bash` with `curl -I` | Simple HTTP check |62| "Find subdomains of X" | **This skill** | Only passive source for this |63| "When does the SSL cert expire?" | **This skill** | Built-in tools can't inspect TLS |64| "Who registered this domain?" | **This skill** | WHOIS data not in web search |65| "Is coolstartup.io available?" | **This skill** | Passive availability via DNS+WHOIS+SSL |6667## Platform compatibility6869Pure Python stdlib (`socket`, `ssl`, `urllib`, `json`, `concurrent.futures`).70Works identically on Linux, macOS, and Windows with no dependencies.7172- **crt.sh queries** use HTTPS (port 443) — works behind most firewalls73- **WHOIS queries** use TCP port 43 — may be blocked on restrictive networks74- **DNS queries** use Google DoH (HTTPS) for MX/NS/TXT — firewall-friendly75- **SSL checks** connect to the target on port 443 — the only "active" operation7677## Data sources7879All queries are **passive** — no port scanning, no vulnerability testing:8081- **crt.sh** — Certificate Transparency logs (subdomain discovery, HTTPS only)82- **WHOIS servers** — Direct TCP to 100+ authoritative TLD registrars83- **Google DNS-over-HTTPS** — MX, NS, TXT, CNAME resolution (firewall-friendly)84- **System DNS** — A/AAAA record resolution85- **SSL check** is the only "active" operation (TCP connection to target:443)8687## Notes8889- WHOIS queries use TCP port 43 — may be blocked on restrictive networks90- Some WHOIS servers redact registrant info (GDPR) — mention this to the user91- crt.sh can be slow for very popular domains (thousands of certs) — set reasonable expectations92- The availability check is heuristic-based (3 passive signals) — not authoritative like a registrar API9394---9596*Contributed by [@FurkanL0](https://github.com/FurkanL0)*
sairam0424