One-click install
npx skills add https://github.com/big4council-prog/b4c-agent --skill domain-intel-big4council-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-intel
Source: https://github.com/big4council-prog/b4c-agent/tree/main/optional-skills/research/domain-intel
Command: npx skills add https://github.com/big4council-prog/b4c-agent --skill domain-intel-big4council-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It eliminates the manual effort of gathering domain infrastructure signals (subdomains, DNS records, TLS certificate details, and WHOIS registration info) by providing structured, JSON output from passive and limited connectivity checks.

Core Features & Use Cases

  • Subdomain discovery: Retrieves subdomains from Certificate Transparency sources and returns them in a normalized JSON structure.
  • TLS certificate inspection: Connects to the target on port 443 to extract expiry, issuer/subject, SANs, TLS version, and cipher details.
  • WHOIS & DNS intelligence: Queries WHOIS servers for registration metadata and resolves DNS record types (A/AAAA/MX/NS/TXT/CNAME).
  • Availability heuristic: Estimates whether a domain may be available using DNS signals, WHOIS presence, and TLS reachability.
  • Bulk analysis: Runs multiple checks across multiple domains with parallel execution and consolidated results.

Use case example: Before registering or assessing a potential brand domain, run bulk checks to see active DNS records, TLS certificate status/expiry, and whether WHOIS indicates the domain is registered.

Quick Start

Ask to run domain-intel for subdomain discovery and TLS validation on example.com and return structured JSON.

Frequently Asked Questions about domain-intel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover subdomains and check DNS records for a domain?

Subdomain discovery and DNS record checks retrieve passive OSINT signals from Certificate Transparency logs and resolve A, AAAA, MX, NS, TXT, and CNAME records into normalized JSON output for security research and domain due diligence.

Can I perform bulk WHOIS lookup and TLS certificate inspection across multiple domains?

Bulk WHOIS lookup and TLS certificate inspection support parallel execution across multiple domains, querying TCP port 43 for registration metadata and TCP port 443 for SSL expiry, issuer, subject, SANs, TLS version, and cipher details.

What is passive OSINT domain reconnaissance and when do I need it?

Passive OSINT domain reconnaissance gathers infrastructure signals like subdomains, DNS records, WHOIS data, and TLS certificates without active scanning, needed for pre-registration checks, brand due diligence, and security investigation.

Do I need API keys to retrieve WHOIS registration metadata and TLS certificate attributes?

No API keys are required to retrieve WHOIS registration metadata or TLS certificate attributes, as the task uses Python stdlib for network resolution, direct TCP port 43 WHOIS lookups, and TCP port 443 SSL inspection.

How does a domain availability heuristic work using DNS and WHOIS signals?

A domain availability heuristic estimates registration status by combining DNS resolution results, WHOIS presence data, and TLS reachability on port 443 to determine if a domain is active or potentially unregistered.

What are the limitations of using Certificate Transparency logs for subdomain discovery?

Subdomain discovery via Certificate Transparency logs relies on crt.sh HTTPS queries, limiting results to subdomains with issued TLS certificates and missing subdomains that have never been part of a certificate request.