Dangling Records
Netlify Subdomain Takeover
Deleted Netlify sites can leave dangling DNS entries. If your CNAME still points there, someone else can register the same site name and take over your subdomain.
How it happens
- You create a subdomain pointing to
sitename.netlify.app. - You delete the Netlify site.
- The CNAME stays in DNS.
- An attacker creates a Netlify site with the same name.
- Your subdomain serves their site.
The fingerprint
Deleted targets often return Not Found - Request ID. If your subdomain resolves there, the CNAME is probably dangling.
How to check
Use DomainPreflight Dangling Records to scan all your hostnames and match Netlify-specific takeover fingerprints.
How to fix
Remove the dangling CNAME. If the subdomain is still needed, recreate and verify the Netlify site first.
Fix it step by step
*.netlify.app.Scan your domain for dangling provider records
Open Dangling Records Scanner →FAQ
What is a Netlify subdomain takeover?
When a CNAME points to a deleted Netlify site, someone else can create a site with the same name and serve content on your subdomain.
How do I know if my subdomain is vulnerable?
Run DomainPreflight Dangling Records. It checks your CNAMEs against known takeover fingerprints including Netlify.
What does the Netlify takeover page look like?
Look for Not Found - Request ID. If your subdomain shows that, the CNAME may be dangling and claimable.
How do I fix a Netlify dangling CNAME?
Delete the DNS CNAME record. If you need the subdomain, recreate the Netlify site first.
Can I prevent this from happening again?
Always delete DNS records when decommissioning services. Run Dangling Records scans quarterly.