To reduce Amazon Route 53 cost, delete dead hosted zones, raise TTLs on stable records, and right-size health checks. Route 53 bills $0.50 per hosted zone per month for the first 25 zones and $0.40 per million standard queries, with alias queries to AWS resources free. Remove zones for domains you no longer own, increase TTLs so resolvers cache longer and send fewer queries, keep only the health checks you act on, and use simple routing instead of premium latency or geo policies where they are not needed. These small recurring lines are part of the waste we clear in the 31% average bill reduction.
Last updated: June 2026 · Written by Morten Andersen and reviewed by Fredrik Filipsson · See, Cut, Lock, Run method
Amazon Route 53 is the AWS DNS service, and DNS is the kind of cost no one looks at because it is small per item. The trouble is the count: a hosted zone for every domain and subdomain a team ever registered, health checks left running for endpoints that are gone, low TTLs that make resolvers re-query constantly, and premium routing policies enabled where simple routing would do. None of it is large alone, but across a large account it adds a steady recurring line. This guide is part of our complete guide to AWS cost optimization, the cluster pillar it links up to.
How much does Amazon Route 53 cost?
Amazon Route 53 costs $0.50 per hosted zone per month for the first 25 zones and $0.40 per million standard queries for the first billion queries each month. Per the Amazon Route 53 pricing page, hosted zones beyond the first 25 are $0.10 each per month, standard queries fall to $0.20 per million above one billion, and specialized routing costs more: latency-based queries are $0.60 per million, geo DNS $0.70 per million, in both cases for the first billion. Queries to a private hosted zone are billed, while alias queries that resolve to AWS resources such as an ELB, CloudFront distribution, or S3 website are free. Health checks carry a separate monthly fee per check, higher for endpoints outside AWS and for optional features. Verify current rates before modeling, since pricing changes by region and query type.
How do I reduce Route 53 cost step by step?
Reduce Route 53 cost by clearing dead zones, caching longer, and trimming health checks. Work through these steps:
- Inventory hosted zones across accounts. List every public and private hosted zone with the Route 53 console and AWS Cost Explorer, since each zone bills $0.50 per month whether or not it serves live traffic.
- Delete dead and duplicate zones. Remove hosted zones for domains you no longer own or that duplicate another zone, after confirming no records are in active use.
- Raise TTLs on stable records. Increase the TTL on records that rarely change so resolvers cache answers longer and send fewer queries, which bill at $0.40 per million standard.
- Right-size or remove health checks. Keep only the health checks you act on, and prefer basic endpoint checks over more expensive string-matching or external options where they are not needed.
- Avoid premium query types where standard routing works. Use simple routing at $0.40 per million instead of latency, geo, or geoproximity routing where the application does not require it.
This is the same waste-elimination work in our AWS cost optimization service. The orchestration-and-messaging counterpart, where workflow type and message volume drive cost, is covered in the sibling guide how to reduce AWS Step Functions and SQS costs.
When a record resolves to an AWS resource, use an alias record instead of a CNAME. Route 53 does not charge for queries to alias records that point at AWS resources like an Application Load Balancer, CloudFront distribution, or S3 static site. On a high-traffic apex domain that one change moves the busiest record off the $0.40 per million query line entirely.
How do I lower DNS query charges with TTLs?
Lower DNS query charges by raising the TTL on records that do not change often, so resolvers cache the answer longer and send fewer queries to Route 53. TTL, or time to live, is the number of seconds a resolver may cache a DNS answer before asking again, and Route 53 bills per query it receives. A record with a 60-second TTL can be queried up to 60 times more often than the same record at a one-hour TTL, because every cache expiry triggers a fresh lookup. For records that point at stable infrastructure, such as a mail server or a fixed apex, a longer TTL of an hour or more dramatically cuts query volume with no functional downside. Keep short TTLs only where you need fast failover or frequent record changes, such as blue-green deployments. Combining longer TTLs on stable records with alias records for AWS resources removes most of the query charge on a typical estate.
How many hosted zones are you paying for that serve nothing?
Our AWS cost audit inventories every hosted zone and health check, removes the dead ones, tunes TTLs, and proves the saving against a clean baseline. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →The AWS Cost Optimization Field Guide includes the networking checklist we run across hosted zones, query volume, and health checks.
Frequently asked questions
How much does Amazon Route 53 cost?
Amazon Route 53 costs $0.50 per hosted zone per month for the first 25 zones and $0.10 for additional zones, plus $0.40 per million standard queries for the first billion per month. Latency, geo, and geoproximity queries cost more. Queries to private hosted zones are billed, while alias queries to AWS resources are free.
How do I reduce Route 53 query costs?
Raise the TTL on records that rarely change so resolvers cache answers longer and send fewer queries, and use alias records to AWS resources, which are not charged for queries. Standard queries bill $0.40 per million, so longer caching on high-volume records is the main query saving.
Are Route 53 health checks expensive?
Health checks carry a monthly fee per check, higher for checks on endpoints outside AWS and for optional features like string matching and HTTPS. They are small individually but add up across many endpoints, so removing checks you do not act on and keeping basic checks where possible reduces the cost.
What is the biggest hidden Route 53 cost?
Dead hosted zones and premium routing policies. Every hosted zone bills $0.50 per month even with no live traffic, and latency, geo, and geoproximity queries cost more than the $0.40 per million standard rate, so abandoned zones and unnecessary routing policies quietly inflate the bill.
The short version
Route 53 bills $0.50 per hosted zone per month and $0.40 per million standard queries, with alias queries to AWS resources free. Delete dead zones, raise TTLs on stable records, use alias records, keep only the health checks you act on, and avoid premium routing where simple routing works. When you want every zone and check reviewed and the saving proven down, that is part of what our AWS cost optimization service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: AWS pricing ↗, AWS documentation ↗ and FinOps Foundation Framework ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.