Subdomain Takeover Checks for Service Offboarding
Review dangling DNS before retiring a cloud resource or SaaS service
A retired help center, campaign site, or cloud application can leave a live DNS record pointing at a resource your team no longer controls. Add a focused DNS review to service retirement so the record and its owner are accounted for before the resource disappears.
Implementation example by the EdgeDNS team · Updated
The Offboarding Gap
Deleting a service does not delete the DNS records that point to it. A dangling alias can become a takeover risk when its target belongs to a service that allows another account to claim the abandoned resource. A failed lookup alone does not establish exploitability, and a broad portfolio scan may miss the exact names affected by a retirement ticket.
Review the Names in the Retirement Ticket
Start with the DNS inventory for resources your organization owns. Query the CNAME records for the specific hosts being retired, then run the subdomain takeover check against the corresponding labels. The takeover endpoint requires Pro and accepts up to 30 comma-separated labels such as blog, docs, or support under one base domain; it does not enumerate every subdomain. It follows CNAME chains and checks supported provider fingerprints, with additional checks for selected cloud address ranges. Review candidate status, evidence, and remediation guidance rather than treating vulnerable_count as an exploitation proof. Investigate error results separately. Coordinate DNS removal or reassignment with the service owner before deleting the provider resource, then recheck after DNS propagation and the relevant API cache window. Retain the ticket, record changes, and dated responses. EdgeDNS reports observations; it does not modify DNS or reclaim third-party resources. For a wider infrastructure review, use the DNS vulnerability assessment workflow.
Endpoints Used
Combine these EdgeDNS endpoints to build this solution.
/v1/dns/lookupAPI referenceDNS Lookup: Read CNAME records for the exact host names in the retirement scope.
/v1/domain/subdomain-takeoverAPI referenceSubdomain Takeover: Review selected labels, CNAME chains, provider fingerprints, and remediation evidence.
What this workflow helps you do
Use a defined scope
Start from the names attached to a retirement ticket rather than assuming an exhaustive subdomain inventory.
Review actionable evidence
Distinguish unclaimed-provider signals, safe observations, absent DNS, and inconclusive checks.
Close the DNS cleanup loop
Keep an owner and verification record for each DNS entry removed or reassigned during offboarding.
Code Example
Inspect the records and takeover findings for a retirement ticket
// Pro access is required for the takeover check. Use domains you own.
const domain = 'example.com';
const labels = ['blog', 'docs', 'support'];
const headers = { Authorization: 'Bearer YOUR_API_KEY' };
async function inspect(path, params) {
const url = new URL(path, 'https://api.edgedns.dev');
url.search = new URLSearchParams(params).toString();
const response = await fetch(url, { headers });
const result = await response.json();
if (!response.ok) throw new Error(result.error?.message ?? 'Check failed');
return result;
}
for (const label of labels) {
const records = await inspect('/v1/dns/lookup', {
domain: label + '.' + domain, type: 'CNAME'
});
console.log('Current DNS', label, records);
}
const findings = await inspect('/v1/domain/subdomain-takeover', {
domain, zones: labels.join(',')
});
console.log('Review provider evidence and any error results', findings);
// A human coordinates cleanup with the service owner.
// Re-run after the approved DNS change, propagation, and cache expiry.Learn More
Explore industry standards and best practices related to this use case.
Ready to build Subdomain Takeover Checks for Service Offboarding?
Get started with 200 free API requests per month. No credit card required.
Other Use Cases
Domain Portfolio Protection
Investigate lookalike domains and changes to domains you own
Cloud Architect / Infrastructure EngineerMulti-Cloud DNS Management
Review DNS answers across resolvers during infrastructure changes
Product Engineer / International Growth TeamIP Geolocation for Content Localization
Suggest a regional experience while keeping the visitor in control