Route 53 record points at a load balancer not in this account

Severity: Low
Service: Route 53
Type: Operations, not counted in the security score
Check ID: ROUTE53_DANGLING_ELB

What this check finds

A public DNS record points at a load balancer name that is not one of this account's load balancers in that region. Load balancer names carry an AWS-generated suffix and cannot be claimed by someone else, so this is a stale record rather than a takeover risk. A load balancer in another AWS account of yours also gives this result.

Passing looks like: No DNS record points at a load balancer that no longer exists.

How to fix it

Delete the record, or point it at the load balancer that replaced it.

AWS console

Route 53 → Hosted zones → select zone → select the record.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to Route 53 record points at a load balancer not in this account
Framework	Controls
NIST SP 800-53 Rev5 (Moderate)	CM-8 System Component Inventory
NIST Cybersecurity Framework 2.0	ID.AM-01 Asset Management — Inventories of assets are maintained
ISO/IEC 27001:2022 Annex A	A.5.9 Inventory of information and other associated assets

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More Route 53 checks

All Route 53 checks