Ensure Route 53 hosted zones are not publicly queryable
Private hosted zones should only be queryable from associated VPCs. Public zones should have appropriate record controls to prevent information disclosure.
Security Impact
Publicly queryable internal DNS information aids attackers in reconnaissance and infrastructure mapping.
How to Remediate
Use private hosted zones for internal resources. Ensure public zones don't expose sensitive infrastructure information in DNS records.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon Route 53 resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for NIST 800-53, Defense in Depth compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-route53-8
- Service
- Amazon Route 53
- Category
- Access Control
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Route 53 Checks
View all checksEnsure Route 53 hosted zones have query logging enabled
Ensure DNSSEC is enabled for Route 53 domains
Ensure Route 53 domains have auto-renewal enabled
Ensure Route 53 domains have transfer lock enabled
Ensure Route 53 domains have privacy protection enabled