hunt-subdomain

Analyze DNS records and HTTP fingerprints to detect subdomain takeover vulnerabilities.

13|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/pdparchitect/rook --skill hunt-subdomain-pdparchitect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-subdomain
Source: https://github.com/pdparchitect/rook/tree/main/skills/hunt-subdomain
Command: npx skills add https://github.com/pdparchitect/rook --skill hunt-subdomain-pdparchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the discovery of dangling DNS records and unclaimed third-party services, preventing attackers from hijacking trusted domains to serve malicious content or perform authentication attacks.

Core Features & Use Cases

  • Vulnerability Discovery: Automatically identifies CNAME records pointing to deprovisioned services like GitHub Pages, S3, or Fastly.
  • Impact Assessment: Evaluates potential for OAuth hijacking, cookie-domain session fixation, and CSP bypasses.
  • Use Case: Use this skill to audit an organization's external attack surface for abandoned subdomains that could be claimed to bypass browser security trust and facilitate phishing or credential theft.

Quick Start

Use the hunt-subdomain skill to enumerate all subdomains for example.com and flag any that point to unclaimed third-party infrastructure.

Frequently Asked Questions about hunt-subdomain

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

FAQPage Schema
How do I detect subdomain takeover vulnerabilities in DNS records?

Subdomain takeover vulnerabilities are detected by analyzing DNS records and HTTP response fingerprints against known provider patterns to identify dangling CNAMEs pointing to deprovisioned services. This process validates whether abandoned third-party namespaces can be claimed.

What is a dangling CNAME and how does it enable subdomain takeover?

A dangling CNAME is a DNS record pointing to a deprovisioned third-party service like GitHub Pages or S3. It enables subdomain takeover when attackers claim the abandoned service namespace to serve malicious content or perform authentication attacks.

How do I audit my external attack surface for abandoned subdomains?

Auditing an external attack surface for abandoned subdomains requires enumerating all DNS records and flagging any CNAMEs pointing to unclaimed third-party infrastructure. This identifies potential OAuth hijacking, session fixation, and CSP bypass risks.

Can I assess the security impact of a dangling DNS record beyond basic hijacking?

Assessing the security impact of a dangling DNS record involves evaluating potential for OAuth hijacking, cookie-domain session fixation, and CSP bypasses. This determines how attackers could bypass browser security trust to facilitate phishing or credential theft.

Does subdomain takeover detection work across diverse cloud and SaaS environments?

Subdomain takeover detection operates across diverse cloud and SaaS environments by matching HTTP response fingerprints against provider-specific fingerprint databases. This confirms claimability across various deprovisioned services.

Do I need DNS enumeration tools to find unclaimed third-party infrastructure?

DNS enumeration tools are required to identify and validate subdomain takeover vulnerabilities. Integration with these tools and provider-specific fingerprint databases is necessary to confirm claimability across cloud and SaaS environments.