Subdomain Takeover
Claiming a dangling DNS record that points to an unclaimed resource.
What it is
An attack where a DNS record still points to a third-party service or host that has been deprovisioned, letting the attacker register that resource and serve content under the victim's trusted subdomain.
Why it matters
Controlling a real subdomain lends huge credibility to phishing and can capture cookies or traffic, so dangling DNS entries are a high-value thing to inventory and clean up.
In practice
Registering an abandoned cloud bucket a forgotten DNS alias still references, then hosting a phishing page there.
What to look for
- CNAMEs pointing to cloud resources that no longer exist.
- Error pages from hosting providers on your subdomains.
- DNS records left behind after a project ended.
Common mistake
Deleting the resource before the DNS record. Remove the record first.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Nmap Open source
Scans hosts for open ports and services, the same view an attacker gets.
-
Shodan Commercial
A search engine for internet facing devices, useful for seeing what you expose.
-
Nuclei Open source
Runs template based checks for exposures and misconfigurations across many targets.
Read next
- Lookalike Domain: A near-identical domain used to impersonate a legitimate one.
- Credential Harvesting Page: A counterfeit login page built to capture entered credentials.
- Web Shell: A malicious script on a web server giving remote command access.