subdomain-takeover

Detects and exploits dangling DNS records enabling subdomain takeover across cloud providers.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill subdomain-takeover-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subdomain-takeover
Source: https://github.com/lNwNl/Praxis/tree/main/skills/_disabled/subdomain-takeover
Command: npx skills add https://github.com/lNwNl/Praxis --skill subdomain-takeover-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Subdomains with dangling CNAME, NS, or MX records pointing to deprovisioned cloud resources can be claimed by attackers, enabling cookie theft, phishing under trusted domains, and email interception. This Skill provides a systematic playbook to identify, verify, and demonstrate these vulnerabilities during authorized security assessments. ## Core Features & Use Cases - Provider Fingerprint Matching: Match HTTP error responses against a fingerprint table covering AWS S3, GitHub Pages, Heroku, Azure, Shopify, Fastly, and more to confirm claimability. - CNAME, NS, and MX Takeover Workflows: Step-by-step claim procedures for common providers, plus high-severity NS zone takeover and MX email interception scenarios. - Decision Tree & Impact Assessment: A structured decision tree guides detection through exploitation, including post-takeover impact analysis for cookies, CORS, CSP, and OAuth redirect abuse. - Use Case: During a bug bounty recon phase, you enumerate subdomains with subfinder, resolve their CNAMEs, and use this playbook to confirm a NoSuchBucket S3 response is claimable, then document the takeover proof-of-concept. ## Quick Start Ask the agent to check whether any of the target's subdomains have dangling CNAME records vulnerable to takeover using the subdomain-takeover playbook.

Frequently Asked Questions about subdomain-takeover

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

FAQPage Schema
How do I detect subdomain takeover vulnerabilities?▼

Enumerate subdomains with tools like subfinder or amass, resolve CNAME records with dig, then match HTTP error responses against provider fingerprints such as NoSuchBucket for S3 or 'No such app' for Heroku. Automated scanners like subjack, nuclei takeover templates, and subzy speed up verification.

What tools check for dangling CNAME records automatically?▼

subjack, nuclei with takeover templates, dnsreaper, and subzy automate CNAME takeover checking across multiple providers. The can-i-take-over-xyz GitHub repository documents which services are claimable and their verification fingerprints.

Does a CNAME pointing to S3 always mean takeover is possible?▼

No. A CNAME to S3 returning 403 means the bucket exists and is private, so it is not vulnerable. Only a 404 NoSuchBucket response indicates the bucket was deleted and the name can be re-registered by an attacker.

Why is NS takeover more severe than CNAME takeover?▼

NS takeover gives the attacker control of all DNS resolution for the zone, not just one subdomain. If a nameserver domain expires and gets re-registered, the attacker can serve arbitrary A, MX, and TXT records, intercept email, and issue TLS certificates via DNS-01 challenges.

Can GitHub Pages subdomains still be claimed for takeover?▼

Only if the target organization has not enabled GitHub's domain verification. Verified domains cannot be claimed by other accounts, so check whether the target uses this feature before attempting the standard repo-plus-CNAME-file claim procedure.