How to fix: Dangling CNAME (SaaS Takeover)
A CNAME points to a SaaS provider (Zendesk, HelpScout, Intercom, Drift, statuspage.io, Pingdom, Pantheon, Acquia, WP Engine) and the target no longer resolves. Attackers can claim the namespace on your subdomain.
Why it matters
SaaS subdomain takeover enables phishing and impersonation of your support and help-center pages (help.example.com, status.example.com), eroding customer trust and enabling credential theft.
SaaS subdomain takeover follows the same pattern as CDN takeover: a CNAME points to a provider-hosted namespace that was previously claimed by your account but is now unclaimed. Attackers register a new account at the provider and claim that namespace.
How to fix it
- 1Audit all CNAMEs targeting customer-support SaaS providers.
- 2Remove dangling entries or re-register the integration if still needed.
- 3Set up automated monitoring with subjack, nuclei, or can-i-take-over-xyz.
Code examples
Check for dangling CNAME
# Check if target resolves
target=$(dig +short CNAME help.example.com)
echo "CNAME target: $target"
dig +short A $target || echo "Target does not resolve: possible takeover"References
Detected automatically by VulnRadar. The check id is dns-dangling-cname-saas, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is Dangling CNAME (SaaS Takeover)?
- VulnRadar rates this high severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dns-dangling-cname-saas, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Dangling CNAME (SaaS Takeover) map to?
- It maps to CWE-350. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.