hunt-subdomain

Detect and verify subdomain takeover vulnerabilities across cloud and SaaS provider fingerprints.

Updated May 29, 2026
One-click install
npx skills add https://github.com/hhjkjkjk/Claude-skills --skill hunt-subdomain-hhjkjkjk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-subdomain
Source: https://github.com/hhjkjkjk/Claude-skills/tree/main/skills/hunt-subdomain
Command: npx skills add https://github.com/hhjkjkjk/Claude-skills --skill hunt-subdomain-hhjkjkjk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Subdomain takeover bugs are easy to miss and hard to prove: dangling CNAME records pointing to deprovisioned services (GitHub Pages, S3, Heroku, Zendesk, Vercel, Fastly) sit unnoticed in DNS, and even when found, hunters struggle to demonstrate real impact beyond a defacement-level Low. This Skill provides a complete methodology to enumerate, fingerprint, claim, and escalate subdomain takeovers into high-severity account-takeover chains. ## Core Features & Use Cases - Provider Fingerprint Library: Detection signatures for GitHub/GitLab Pages, S3, Heroku, Zendesk, UserVoice, Shopify, Fastly, Vercel, Azure cloudapp, and Netlify, including HTTP error strings, DNS signals, and response headers. - Step-by-Step Hunting Workflow: Enumeration with subfinder/amass/assetfinder, CNAME resolution with dnsx, automated scanning with subjack and nuclei, and manual claim verification per provider. - Five Escalation Chains: Maps every takeover to OAuth redirect_uri theft, cookie-domain session fixation, CSP script-src bypass, CORS credentialed reads, or DKIM/SPF email spoofing to justify High/Critical severity. - Use Case: You find assets.target.com returning "Fastly error: unknown domain". Follow the workflow to confirm the CNAME is unclaimed, attach the domain to a new Fastly service, publish a unique marker page, then check whether the parent app's CSP allowlists the host to escalate the report from Informational to Critical. ## Quick Start Enumerate subdomains for my target, check each CNAME against the takeover fingerprints, and tell me which ones are claimable and how to prove impact.

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 on a bug bounty target?▼

Enumerate subdomains with subfinder, amass, assetfinder, and crt.sh, then resolve CNAMEs with dnsx and scan with subjack or nuclei takeover templates. Manually verify each hit by confirming the CNAME target returns NXDOMAIN or a provider-specific 404 error string.

What DNS and HTTP signals indicate a subdomain is takeoverable?▼

Look for CNAMEs pointing to providers like github.io, herokudns.com, s3.amazonaws.com, or fastly.net where the target no longer resolves. HTTP signals include strings like "There isn't a GitHub Pages site here", "NoSuchBucket", "Fastly error: unknown domain", and "Sorry, this shop is currently unavailable".

How do I prove subdomain takeover impact for a higher bounty?▼

Claim the resource and publish a unique marker page with your username and timestamp, then check escalation chains: OAuth redirect_uri allowlists, parent-domain cookie scope (Domain=.target.com), CSP script-src entries, CORS regex matches, and DKIM/SPF email DNS. Demonstrating one chain typically justifies High or Critical severity.

Which providers are most commonly vulnerable to subdomain takeover?▼

Frequently cited providers include GitHub Pages, GitLab Pages, AWS S3, Heroku, Zendesk, UserVoice, WordPress.com, Shopify, Fastly, Vercel, Azure cloudapp.azure.com, and Netlify. Each has a distinct claim flow, such as registering an S3 bucket name or attaching a domain to a new Fastly service.

Why was my subdomain takeover report closed as informational?▼

Standalone takeovers without demonstrated downstream impact are usually rated Low or Informational. Triage teams expect proof the resource is currently claimable plus at least one escalation chain, such as session cookie theft, OAuth code interception, or CSP bypass, before accepting higher severity.

Can I detect subdomain takeovers without triggering rate limits or WAFs?▼

Yes, use passive-only sources like SecurityTrails, Shodan, crt.sh, and VirusTotal for enumeration since DNS resolution never touches the target's web servers. Reserve active probing with curl and nuclei for the shortlist of candidate subdomains.