Back to Skills

find-hidden-subdomains

Enumerate an organisation's subdomains and sibling domains from Certificate Transparency logs and passive DNS, without sending traffic to the target. Covers crt.sh and CT log queries, certificate SAN fields, subfinder and amass, and newly issued TLS certificates. Use when looking for staging, dev, admin or VPN hosts, mapping the full hostname footprint of a domain, or spotting infrastructure a company forgot it had. Applies to attack-surface mapping, vendor and supply-chain security review, bran

13stars1forksUpdated 8/14/2026

Security Assessment

Medium Risk(65/100)

Detected risks:

Attack-surface reconnaissance automation(The skill automates passive enumeration of an organization's subdomains, sibling domains, and internal infrastructure from certificate transparency logs and passive DNS, which is the reconnaissance phase common to both defensive audits and attacks., Its bundled triage guidance profiles discovered hostnames to identify high-value targets such as VPN gateways, admin panels, databases, backups, and CI systems, which is dual-use even though the skill restricts follow-up to passive methods and reporting.)
Security Score65/100

About find-hidden-subdomains

find-hidden-subdomains is an OSINT tradecraft skill for enumerating an organization's subdomains and sibling domains passively — primarily from Certificate Transparency (CT) logs and passive DNS — without sending traffic to the target. It addresses attack-surface discovery: the forgotten staging, dev, admin, VPN, and internal hosts that announced themselves the moment someone requested a public TLS certificate, plus domains an organization did not know it owned.

The skill explains how CT works (append-only public logs, precertificates versus certificates, blindness to private/self-signed certs), how to query crt.sh via its JSON API and its read-only guest Postgres endpoint, how to mine certificate SAN fields and do identity searches on an organization name, and how to bring in tooling like subfinder and amass. Bundled references cover additional CT front-ends and a detailed name-pattern triage matrix that reads a hostname's label to infer its likely purpose (environments, remote-access appliances, mail, admin panels, CI/registries, identity providers, APIs, storage, backups) and prioritize passive follow-up. It repeatedly frames results as historical evidence — most CT hits do not resolve — and treats DNS resolution as the liveness oracle.

It targets security professionals doing authorized attack-surface mapping, vendor and supply-chain review, brand-infringement discovery, and M&A technical diligence. This is dual-use reconnaissance tradecraft — the same enumeration underpins both defensive asset inventory and the first phase of an attack. Its guidance is notably restrained (passive-only, explicit instructions never to attempt credentials and to report exposed management/backup hosts through abuse contacts), but subdomain and infrastructure enumeration automation is inherently reconnaissance capability, which lowers its security rating relative to a purely benign skill.

FAQ

What sources does it use to find subdomains?

Certificate Transparency logs (via crt.sh's JSON API and a read-only guest Postgres endpoint), certificate SAN fields, passive DNS, and tools such as subfinder and amass — all without sending traffic to the target.

Why do many discovered hosts not resolve?

CT logs are append-only and historical, so a hostname from a cert issued years ago remains listed after the host is gone. The skill treats DNS resolution as the test for whether a host is currently live.

What are its blind spots?

CT only covers publicly-trusted certificates. Private/internal CA certs, self-signed certs, and Cloudflare origin certificates never reach the logs, so those hosts are invisible to this method.

Is it intended for offensive use?

It is framed for authorized defensive work — attack-surface mapping, supply-chain review, brand-infringement, and M&A diligence — and explicitly instructs never to attempt credentials and to report exposed sensitive hosts. The enumeration techniques are nonetheless dual-use reconnaissance.

Does it exploit anything it finds?

No. It is passive discovery and triage only; the name-pattern triage output is a priority order for further passive research and reporting, not a licence to connect to any host.

All Files

3 files
reference/name-pattern-triage.md8.2 KB
View
reference/subdomain-sources.md7.5 KB
View
SKILL.md12.5 KB
View

Install find-hidden-subdomains

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill