IBRAVRA Media Network
Website & Hosting • 12 min read

Cloudflare DNS vs Route 53 vs Google Cloud DNS: The Pricing Playbook

Cloudflare folds DNS into a per-zone plan starting at $0, Route 53 charges $0.50 a zone plus $0.40 per million standard queries, and Google Cloud DNS charges $0.20 a zone plus the same $0.40 per million. This playbook runs all three price lists against identical zone and query profiles, with every figure taken from the vendors own pricing pages on 7 November 2026.

By Enow A. Jovial • Published 2026-11-07

What managed DNS costs

Every domain needs an authoritative DNS service: the system that answers where example.com lives. Cloudflare sells a plan per zone and folds DNS into it: zero on Free, flat on Pro and Business. Route 53 sells a hosted zone plus a meter on every query. Google Cloud DNS sells a managed zone plus a meter on every query, at lower zone rates and identical query rates. The same traffic can cost $0, $0.90, or $612.50 a month depending on which vendor holds the zone.

The cheapest DNS vendor is decided by the shape of the traffic, not the size of it. Cloudflare wins wherever a flat plan is allowed, Google wins on zone count between the two metered vendors, and Route 53 wins only where alias queries to AWS services erase the query meter entirely.

The three vendors

Cloudflare DNS is the DNS that comes with a Cloudflare account. Free costs $0 per month per zone and includes authoritative DNS, DDoS protection, a Universal SSL certificate, and the CDN. Pro costs $20 a month per zone billed annually ($25 monthly); Business costs $200 ($250 monthly). No per-query DNS charge is printed on any self-serve plan.

Amazon Route 53 is the metered incumbent. A hosted zone costs $0.50 a month for each of the first 25 zones and $0.10 after that, charged in full for the month. Standard queries cost $0.40 per million for the first 1 billion a month and $0.20 above that. Routing costs more: latency-based $0.60, geolocation and geoproximity $0.70, and IP-based routing $0.80 per million. Two carve-outs matter: alias queries to AWS services and queries on private zones cost nothing.

Google Cloud DNS is the metered challenger with the lower zone ladder. A managed zone costs about $0.20 a month for each of the first 25 zones, about $0.10 for zones 25 to 10,000, and about $0.03 above 10,000, billed hourly and prorated. Regular queries cost $0.40 per million for the first 1 billion a month and $0.20 above that, identical to Route 53. Routing policy queries cost $0.70 per million for the first 1 billion and $0.35 above it. The pricing page states there is no free tier for Cloud DNS.

The rate card

Cloudflare plans page: Free $0, Pro $20 a month, Business $200 a month
Cloudflare plans page: Free $0, Pro $20 a month, Business $200 a month
ItemCloudflare DNSAmazon Route 53Google Cloud DNSAuthority
Zone, first 25$0 Free; $20 Pro; $200 Business per zone per month$0.50 per hosted zone per month$0.20 per managed zone per monthVendor pricing pages
Zone, beyond 25Same plan fee$0.10 per hosted zone per month$0.10 per zone per month to 10,000; $0.03 aboveRoute 53 and Google pricing pages
Standard queries, first 1B per monthNo query charge$0.40 per million$0.40 per millionVendor pricing pages
Standard queries, over 1B per monthNo query charge$0.20 per million$0.20 per millionRoute 53 and Google pricing pages
Latency or routing-policy queriesGeo routing add-on $10 per month flat$0.60 per million latency-based$0.70 per million routing policyVendor pricing pages
Free tierFree plan $0 per zone, DNS includedNo free zone or query allowanceNone stated; page says no free tierVendor pricing pages

The query rates on Route 53 and Google Cloud DNS match to the cent at every tier, so any gap between their bills comes from the zone ladder and the extras. Cloudflare has no row for queries at all, because there is no query meter on self-serve DNS: a vendor that does not meter queries cannot be beaten on query cost, and can only lose on the plan fee.

Free-tier ceilings

Cloudflare has the only real free tier here. Free costs $0 per zone and includes the DNS, the CDN, unmetered DDoS protection, and a Universal SSL certificate. The ceiling is a set of plan gates: Free allows only the full setup, where Cloudflare is the primary DNS provider, while the partial CNAME setup, zone transfers, and subdomain setups sit on Business and Enterprise. The vercel-vs-netlify-vs-cloudflare-pages-frontend-hosting-pricing comparison shows the same plan-gate pattern on the hosting side.

Route 53 has no free tier for hosted zones or standard queries: the pricing page charges from the first zone and the first query. What is free is narrow: alias queries to AWS services, queries on private hosted zones, the first 50 AWS-endpoint health checks, and a zone deleted within 12 hours of creation. A site that points its apex at CloudFront or an Elastic Load Balancer through an alias record pays $0.50 a month, $0 for queries.

Google Cloud DNS has no free tier either, and its pricing page says so in one sentence: there is no free tier for Cloud DNS. The meter starts at the first zone and the first query, and all zone types are aggregated together. The cheapest Google bill is $0.20 a month for one zone, and $0.60 a month at 1 million queries.

The formula

Route 53 Monthly=Zones×Zone Rate+Standard Queries1,000,000×$0.40\text{Route 53 Monthly} = \text{Zones} \times \text{Zone Rate} + \frac{\text{Standard Queries}}{1{,}000{,}000} \times \$0.40
Google Cloud DNS Monthly=Zones×Zone Rate+Regular Queries1,000,000×$0.40\text{Google Cloud DNS Monthly} = \text{Zones} \times \text{Zone Rate} + \frac{\text{Regular Queries}}{1{,}000{,}000} \times \$0.40

Cloudflare needs no formula: the DNS charge is zero on Free and the plan fee on Pro and Business, $0, $20, or $200 a month per zone on annual billing. Both metered vendors prorate queries: 100,000 standard queries cost $0.04 on either.

The profiles

ProfileCloudflare FreeCloudflare Pro (annual)Route 53Google Cloud DNSAuthority
A: 1 zone, 1M queries per month$0.00$20.00$0.90$0.60Vendor pricing pages
B: 10 zones, 50M queries per month$0.00$200.00$25.00$22.00Vendor pricing pages
C: 100 zones, 500M queries per month$0.00$2,000.00$220.00$212.50Vendor pricing pages

Profile B is the small-business case: 10 zones and 50 million standard queries a month. Route 53 charges 10 times $0.50 for zones ($5.00) plus 50 times $0.40 for queries ($20.00), for $25.00 a month. Google charges 10 times $0.20 for zones ($2.00) plus the same $20.00 for queries, for $22.00 a month. Cloudflare Pro charges 10 times $20, which is $200.00 a month. Run it through the Break-Even Analysis Calculator before signing.

Profile C is the agency case: 100 zones and 500 million standard queries a month. Route 53 charges 25 times $0.50 plus 75 times $0.10 for zones ($20.00) plus 500 times $0.40 for queries ($200.00), for $220.00 a month. Google charges 25 times $0.20 plus 75 times $0.10 for zones ($12.50) plus the same $200.00 for queries, for $212.50 a month. Cloudflare Pro charges 100 times $20, which is $2,000.00 a month; Business is $20,000.00 a month.

Worked example

Worked example: Northwind Media is a fictional 10-site publisher with 10 zones, 50 million standard queries a month, and 10 non-AWS endpoints under basic health checks. Cloudflare Free covers the DNS at $0. Route 53 charges $5.00 for zones plus $20.00 for queries plus 10 times $0.75 for the checks: $32.50 a month. Google charges $2.00 for zones plus $20.00 for queries plus 10 times $2.00 for the checks: $42.00 a month. The checks flip the ranking.

The zone fee is charged in full even when the zone exists for part of a month. Delete test zones the same day you create them: Route 53 waives the fee only for a zone deleted within 12 hours.

What counts as a query

Route 53 charges for every query its service answers on a public hosted zone, including queries for record types that do not exist and queries for a name with the wrong type. A browser sending both an A and an AAAA query for the same name generates two billable queries. The only public-zone queries that escape the meter are alias queries to AWS services, free at any volume.

Google counts queries the same way: every query against a zone is charged at the regular or routing-policy rate, and all zone types are aggregated. One detail differs: when a forwarding zone resolves a forwarding target, that resolving query is charged in addition to the standard query charge. A forwarding setup therefore pays twice for the same lookup.

Cloudflare counts nothing on self-serve DNS: no query meter on the plans page, no per-million rate. The only Cloudflare product here with a query meter is Load Balancing: the first 500,000 DNS requests a month are free across the account, and each further block of 500,000 costs $0.50. A load balancer serving 2 million DNS requests a month costs $5.00 plus 3 times $0.50, which is $6.50 a month.

Route 53 pricing page: hosted zones $0.50 per month, standard queries $0.40 per million
Route 53 pricing page: hosted zones $0.50 per month, standard queries $0.40 per million

Health checks and routing

Route 53 gives the first 50 AWS-endpoint health checks free, then charges $0.50 per AWS-endpoint check and $0.75 per non-AWS check per month. Optional features (HTTPS, string matching, fast interval, latency measurement) add $1.00 per feature per month on AWS endpoints, $2.00 on non-AWS endpoints. A single non-AWS check with string matching and a fast interval costs $0.75 plus 2 times $2.00, which is $4.75 a month.

Google prices health checks by the hour. An external fast check costs $0.002739726 an hour ($2.00 a month over 730 hours), and an external premium check costs $0.005479452 an hour ($4.00 a month). Internal fast checks cost $0.50 a month, internal premium $2.00. Ten external premium checks cost $40.00 a month on Google, against $7.50 for ten basic non-AWS checks on Route 53.

Routing policy is the second extra: Route 53 latency-based routing costs $0.60 per million, geolocation and geoproximity $0.70, and IP-based routing $0.80, each for the first 1 billion a month. Google routing policy queries cost $0.70 per million for the first 1 billion and $0.35 above it. At 100 million routing queries a month, Route 53 latency-based routing costs $60.00, Google routing policy $70.00. Cloudflare charges $10.00 a month flat for geo-based routing, undercutting both metered vendors above about 17 million latency-based queries a month on Route 53.

Google Cloud DNS pricing page: queries $0.40 per million, zones $0.000273973 per hour
Google Cloud DNS pricing page: queries $0.40 per million, zones $0.000273973 per hour

High volume

Profile D is 25 zones with 2 billion standard queries a month. Route 53 charges 25 times $0.50 for zones ($12.50) plus 1,000 times $0.40 for the first billion queries ($400.00) plus 1,000 times $0.20 for the second billion ($200.00), for $612.50 a month. Google charges 25 times $0.20 for zones ($5.00) plus the same $600.00 for queries, for $605.00 a month; Cloudflare Free charges $0.

One Cloudflare Pro zone costs $20.00 a month billed annually. One Route 53 zone costs $0.50 a month plus $0.40 per million standard queries. Setting them equal gives $19.50 divided by $0.40, times 1 million: 48.75 million standard queries a month. Below that volume Route 53 is cheaper; above it, Pro is cheaper. Against Google the break-even is 49.5 million queries a month.

The traps

Four traps turn a cheap DNS bill expensive. The first is the plan gate. Cloudflare Free is $0, but it allows only the full setup, and the partial CNAME setup needs Business while zone transfers and secondary DNS need Enterprise. Needing another provider as primary means Business at $200 a month per zone. The second trap is zone sprawl: Route 53 charges $0.50 a month for each of the first 25 hosted zones and $0.10 after that, so one hundred unused zones cost $20.00 a month on Route 53 and $12.50 on Google.

The third trap is the TTL habit. A short TTL means resolvers re-query often, and every re-query is a billable query on the metered vendors. Doubling a TTL from 300 to 600 seconds roughly halves cached query volume. The fourth trap is the alias blind spot in reverse. Route 53 alias queries to AWS services are free, which makes Route 53 the cheapest metered option for a site that lives entirely on AWS. Measure the alias share first. The cloudflare-r2-vs-aws-s3-vs-backblaze-b2-object-storage-pricing comparison applies the same alias discipline to object storage, and the cloudflare-vs-fastly-vs-aws-cloudfront-cdn-pricing-latency-playbook comparison prices the delivery layer that sits behind the DNS.

Price the DNS decision with the same three profiles used here: 1 zone with 1 million queries, 10 zones with 50 million, 100 zones with 500 million. If the ranking changes between profiles, the decision is volume-dependent, and the contract should be re-priced every year as volume moves.

The 30-day decision checklist

  1. Count the zones, including the dead ones. List every zone, then delete the ones with no traffic.
  1. Measure the monthly query volume per zone. Read it from the current provider before comparing.
  1. Split the queries by type. Count standard, latency-based, geolocation, and alias queries separately.
  1. Price the health checks. List every endpoint, mark AWS against non-AWS, and add the features.
  1. Check the setup the architecture needs. Confirm whether the plan allows a full, partial, or secondary setup.
  1. Run the break-even. Compare one Pro zone at $20 against the metered bill.
  1. Test the TTL. Raise the TTL on stable records and watch the query volume fall.
  1. Confirm the alias share. Measure what fraction of queries resolve to AWS services.
  1. Re-price yearly. Re-run the three profiles at the new volume.

Founder & CEO Insight — Enow A. Jovial

"DNS is the cheapest line on the infrastructure bill and the easiest one to get wrong, because the price is not in the zone fee. It is in the query meter, the health checks, and the plan gate you discover after the migration. Count the queries before you count the dollars."
— Enow A. Jovial, Founder & Chief Executive Officer

Who this is not for

This playbook is not for the team that has already committed to a single cloud and will not move: if every workload sits on AWS, Route 53 alias queries make the comparison academic, and if every workload sits on Google Cloud, the zone ladder makes Google the default. It is not for the operator who needs secondary DNS across two providers: that setup is Enterprise-gated on Cloudflare and priced as a negotiated contract. For everyone else, the profiles above are the decision: run the measured volume through the three price lists and let the arithmetic choose.