A Route 53 record still points at a bucket, distribution, environment or address that your account deleted or released. The attacker creates a resource with the same name or receives the same address in their own account, and serves content, collects cookies or requests certificates under your subdomain. Capture what the name serves now, then reclaim the target or delete the record.
Look here
Log
Search for
Route 53 record sets
Records whose targets may be gone. List zones with aws route53 list-hosted-zones. Flag targets containing s3-website, cloudfront.net or elasticbeanstalk.com, alias targets, A records with public IPs, and NS delegations: aws route53 list-resource-record-sets --hosted-zone-id <zone>
S3 website targets
Whether anyone owns the bucket name, which equals the host name. A 404 means nobody owns the name, and a 403 means another account may own it now: aws s3api head-bucket --bucket <hostname>
Elastic Beanstalk targets
Whether the environment name is free. "Available": true means the record points at a free name: aws elasticbeanstalk check-dns-availability --cname-prefix <prefix> --region <region>
CloudFront aliases
Your distributions and their alternate domain names: aws cloudfront list-distributions --query "DistributionList.Items[].[Id,DomainName,Aliases.Items]"
CloudFront conflicts
Other accounts that own the name, shown with partly hidden account IDs: aws cloudfront list-conflicting-aliases --distribution-id <id> --alias <hostname>
Elastic IP targets
Released addresses. An A record value missing from every account and Region is released. Compare with: aws ec2 describe-addresses --region <region>
CloudTrail, us-east-1 for Route 53
Record changes and the deletions that orphaned records: ChangeResourceRecordSets, DeleteHostedZone, DeleteBucket, DeleteDistribution, TerminateEnvironment, ReleaseAddress
Route 53 public query logs
Queries for the dangling name and the resolvers asking. Needs a query logging configuration with a CloudWatch Logs group in us-east-1. CloudTrail records API calls and no DNS queries
Contain
#
Item
1
Capture what the name serves now: DNS answers, HTTP responses, TLS certificate and page content, with timestamps. See Evidence
2
Export the record set before you change it: aws route53 list-resource-record-sets --hosted-zone-id <zone> --output json > zone-<zone>.json
3
Reclaim a free S3 name by creating the bucket in your account in the same Region, with Block Public Access on
4
Try to recover a released address. The call fails once another account owns it: aws ec2 allocate-address --domain vpc --address <ip>
5
Delete the record destructive. The change batch has a DELETE action that repeats every value of the existing record: aws route53 change-resource-record-sets --hosted-zone-id <zone> --change-batch file://delete.json
6
Check the change until its status is INSYNC: aws route53 get-change --id <change-id>
Eradicate and recover
#
Item
1
Sweep every hosted zone in every account with the checks under Look here, and delete or repoint each dangling record
2
Invalidate sessions for users who visited the name while the attacker owned it, and rotate any cookie scoped to the parent domain
3
Search Certificate Transparency logs for certificates issued for the name, ask the issuing certificate authority (CA) to revoke them, and add CAA records that name your CAs
4
Make parent NS records match the delegation set of each Route 53 hosted zone, and remove delegations to zones you deleted
5
Change the decommission order: delete the DNS record, wait for its time to live (TTL), then delete the resource. Empty old S3 buckets and keep them so the name stays yours
6
Turn on DNSSEC signing for public hosted zones, and schedule the sweep to run after every deploy
Watch out
Resolvers keep serving a cached answer until its TTL expires, so traffic can reach the attacker after the delete shows INSYNC. Route 53 changes reach its own name servers within about 60 seconds.
General purpose bucket names share one global namespace. After you delete a bucket, any account can create that name and receive requests meant for it.
CloudFront accepts an alternate domain name only with a trusted certificate that covers it, and only on one distribution. A dangling CloudFront name is harder to claim than an S3 or Elastic Beanstalk name. Remove it anyway.
Route 53 withholds a deleted zone's name servers from new zones only while the parent still delegates to them. It gives no protection for a delegation to name servers of a zone you never created.
AWS documentation: Route 53 protection from dangling delegation records, routing to S3 website endpoints, public DNS query logging, CloudTrail logging, ChangeResourceRecordSets API; S3 deleting a bucket and website endpoints; Elastic Beanstalk environment domain names; CloudFront alternate domain names; EC2 releasing and recovering Elastic IP addresses; CLI reference for s3api head-bucket, elasticbeanstalk check-dns-availability, cloudfront list-conflicting-aliases and ec2 allocate-address. Checked September 2026.