Topic · Threats
Subdomain takeover
Subdomain takeover is the unauthorized control of a subdomain, often through an abandoned external hosting or SaaS mapping.
How it works
Attackers look for DNS records referencing unclaimed resources and register the corresponding service tenancy when the provider allows it.
What can go wrong
A compromised branded subdomain can be used for phishing pages, malware distribution or reputation abuse.
What to check or do
Remove stale DNS mappings and implement continuous resource-ownership checks for delegated subdomains.
How to investigate Subdomain takeover
- Signal to investigate
- An unused app subdomain still CNAMEs to an unclaimed SaaS hosting account.
- Evidence to collect
- Inventory DNS targets, vendor resource state, takeover proof requirements and exposure logs.
- Common wrong conclusion
- Deleting the CNAME without verifying active traffic can break legitimate applications.
How to interpret the evidence
The risk arises when a domain points at infrastructure an attacker can newly claim. Whether takeover is possible depends on the service and resource-claim rules.
What to change and how to verify it
Remove stale aliases or reclaim the resource through the provider, then verify resolution and HTTP ownership on all hostnames.
Put this into practice
Run a focused check, then explore protection if your domain needs it.