hunt-subdomain

Analyze DNS records and HTTP responses to identify subdomain takeover vulnerabilities.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Skobyn/talon --skill hunt-subdomain-skobyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-subdomain
Source: https://github.com/Skobyn/talon/tree/main/skills/hunt-subdomain
Command: npx skills add https://github.com/Skobyn/talon --skill hunt-subdomain-skobyn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires subfinder, amass, assetfinder, nuclei, subjack, dnsx, crt.sh, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill assists in identifying and reporting subdomain takeover vulnerabilities, helping to maintain domain integrity and trust.

Core Features & Use Cases

  • Subdomain Enumeration: Detects and enumerates all subdomains of a target domain.
  • Provider Fingerprints: Identifies modern provider fingerprints, such as Azure, Vercel, and Zendesk.
  • Attack Surface Signals: Monitors DNS and HTTP signals indicating potential subdomain takeover vulnerabilities.
  • Hunting Methodology: Provides step-by-step instructions for manual verification and documentation of subdomain takeover findings.
  • Impact Assessment: Assesses the potential impact and severity of subdomain takeovers.
  • Real Impact Examples: Offers real-world examples of successful subdomain takeovers and their consequences.
  • Chain & Compositions: Discusses various chaining techniques and compositions related to subdomain takeovers.

Quick Start

Run the skill with the target domain to enumerate subdomains and identify potential takeover vulnerabilities.

Frequently Asked Questions about hunt-subdomain

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

FAQPage Schema
How do I find subdomain takeover vulnerabilities for a target domain?

To find subdomain takeover vulnerabilities, this skill analyzes DNS records, HTTP responses, and cloud provider fingerprints. It enumerates subdomains using tools like subfinder and amass, then checks for dangling DNS entries indicating potential takeover points.

What are modern provider fingerprints for subdomain takeover detection?

Modern provider fingerprints for subdomain takeover detection include signatures for cloud services like Azure, Vercel, and Zendesk. The skill matches these fingerprints against HTTP responses and DNS records to identify unclaimed subdomains vulnerable to takeover.

How do I manually verify a potential subdomain takeover finding?

Manual verification of a subdomain takeover involves analyzing technical indicators from DNS and HTTP signals, then following the provided hunting methodology. The skill supplies step-by-step instructions for validating technical signals and assessing the potential impact and severity.

Does subdomain takeover hunting work with subfinder and nuclei?

Yes, subdomain takeover hunting works directly with subfinder and nuclei. The skill integrates these tools alongside amass, dnsx, and subjack to enumerate subdomains, analyze DNS records, and detect vulnerable technical signals across the target domain.

What DNS and HTTP signals indicate a vulnerable subdomain takeover?

DNS and HTTP signals indicating a subdomain takeover include dangling CNAME records pointing to unprovisioned cloud resources and specific HTTP error responses. The skill monitors these attack surface signals to detect potential vulnerabilities.

How do I assess the impact of a successful subdomain takeover?

To assess the impact of a subdomain takeover, the skill evaluates chain and composition techniques alongside real-world impact examples. It helps determine the consequences of domain integrity and trust loss resulting from the vulnerability.