• Infrastructure
Subdomain Takeover
Subdomain takeover happens when DNS still points at a cloud or SaaS endpoint you abandoned — and an attacker claims that endpoint to serve content under your hostname.
How attackers abuse it
Engineering deletes a Heroku app, GitHub Pages site, Azure website, or S3/CloudFront origin but leaves the CNAME. The name resolves to an unclaimed resource fingerprint.
Attackers register the same resource name, inherit cookies scoped to parent domains, break OAuth redirect allowlists, and host phishing with a legitimate subdomain.
Brand and trust damage is immediate; technical impact includes session fixation and bypass of domain-based security controls.
What proof looks like
Proof documents the dangling DNS record, the provider fingerprint showing the resource is unclaimed (or claimed in a controlled test), and the takeover path — without hijacking customer production brands outside authorized rules of engagement.
In PandaONE, this class maps to the Infrastructure finding category. Alerts ship only with evidence — never as unverified scanner noise.
How to prevent it
- Inventory all DNS records; remove CNAMEs when decommissioning services.
- Monitor for NXDOMAIN / provider “claim this” responses on branded hosts.
- Prefer automated teardown checklists that delete DNS with the resource.
- Limit broad cookie Domain attributes that amplify takeover impact.
- Include takeover checks in attack-surface reviews before launches.
Hunt this class with proof
Or scan your domain.