Check ID: route53_dangling_ip_subdomain_takeover
Provider: AWS
Service: route53
Severity: HIGH
Categories: internet-exposed
Resource type: AwsRoute53HostedZone

What this check verifies

Route 53 A records (non-alias) that use literal IPs are evaluated for public AWS addresses not currently assigned to resources in the account. Entries that match AWS ranges yet lack ownership are identified as potential dangling IP targets.

Risk

Dangling DNS A records pointing to released AWS IPs enable subdomain takeover. An attacker who later obtains that IP can:
  • Redirect or alter content (integrity)
  • Capture credentials/cookies (confidentiality)
  • Disrupt or impersonate services (availability)

Recommendation

Remove or update any record that points to an unassigned IP. Avoid hard-coding AWS public IPs in A records; use aliases/CNAMEs to managed endpoints. Enforce asset lifecycle decommissioning, routine DNS-asset reconciliation, and change control with monitoring to prevent and detect drift.

Remediation

aws route53 change-resource-record-sets --hosted-zone-id <example_resource_id> --change-batch '{"Changes":[{"Action":"UPSERT","ResourceRecordSet":{"Name":"<example_resource_name>","Type":"A","AliasTarget":{"HostedZoneId":"<ALIAS_TARGET_HOSTED_ZONE_ID>","DNSName":"<ALIAS_TARGET_DNS_NAME>","EvaluateTargetHealth":false}}}]}'

References

Where this check fires

This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable by Check ID = route53_dangling_ip_subdomain_takeover. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks