Subdomain Takeover

Check List

Methodology

Subdomain Takeover

1

Use the target subdomains command to collect URI and extract a list from the list of target subdomains

2

Separate the CNAME records by using the following commands that are executed on the target with dig and dns recone tools

3

Using the next command, we will check the list of subdomains that are CNAMEd to another domain, whether it will be taken over or not, and if it is among the lists, we can do the subdomain takeover


Dangling DNS

1

Identified unclaimed subdomains (e.g., via CNAME, A, MX, or NS records) pointing to deprovisioned services (e.g., AWS S3, Zendesk, CloudFront) use this Command for Subdomain takeover

2

Service Claiming Re-registered the external service (e.g., S3 bucket or SaaS trial) using the vulnerable subdomain

3

Gained control of the subdomain to serve malicious or spoofed content Exploited existing curl/wget/documentation links orCI/CD pipeline calls referencing the subdomain to deliver

  • Unsigned binaries

  • VM/container images

  • CloudFormation templates

  • SSLVPN configurations

4

Indirect compromise of downstream systems via trusted artifact delivery mechanisms Over 8M live requests to hijacked buckets across gov, Fortune 500, and OSS, enabling large-scale poisoning or exploitation


Cheat Sheet

Subdomain Fuzzing

DNS Recon

Recon Sub

Recon IP

Checklist Providers

Create Script

Run Script

Create Script

Script Run

Last updated