Free DNS Time-to-Live Diagnostic Tool

DNS TTL & Caching Health Checker

Analyze your domain's DNS TTL settings under two key lenses: Everyday Page Load Latency vs. Server Migration Readiness.

Caching Performance Score
70 / 100
Evaluates lookup speed vs cache efficiency
Shortest TTL
9.5 minutes (571s)
Fastest record expiration duration
Longest TTL
6 hours (21600s)
Maximum cached retention duration
Records Inspected
41
A, AAAA, CNAME, MX, TXT, NS, SOA
1. Everyday Load Performance
Optimal Caching
Optimal DNS Caching Balance
Your DNS TTL settings strike a healthy balance between fast initial DNS connection speeds and reasonable infrastructure agility.
2. Server Migration Agility
Migration Ready
Ready for Fast Server Migration
Your primary web resolution records (A/CNAME) have low TTLs. If you switch web hosts or server IPs today, DNS updates will propagate globally within minutes with minimal downtime.

DNS Record TTL Inventory (brewers.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
brewers.com A
34.117.109.43
59.6 minutes (3577s) Optimal Speed 2h Prep Needed
brewers.com NS
ns-cloud-b2.googledomains.com
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-cloud-b3.googledomains.com
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-cloud-b4.googledomains.com
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-204.awsdns-25.com
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-976.awsdns-58.net
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-1370.awsdns-43.org
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-1997.awsdns-57.co.uk
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com NS
ns-cloud-b1.googledomains.com
6 hours (21571s) Optimal Speed 24h Prep Needed
brewers.com SOA
Primary NS: ns-1370.awsdns-43.org (Admin: awsdns-hostmaster.amazon.com)
15 minutes (900s) Lookup Overhead Instant Propagation
brewers.com MX
[Priority 10] us-smtp-inbound-1.mimecast.com
10 minutes (600s) Lookup Overhead Instant Propagation
brewers.com MX
[Priority 10] us-smtp-inbound-2.mimecast.com
10 minutes (600s) Lookup Overhead Instant Propagation
brewers.com TXT
adobe-idp-site-verification=f6fee7cc-ad9d-41d2-94c6-16c5585bcab4
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
google-site-verification=9DG5ADkNy4mOvMyx6uVMNOWLpdHklFYNpJRdQEpIM80
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
google-site-verification=RDBaskhJV0RcFIubEXUWnR2HqxJzpwz3RTpyHx4xlWA
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
google-site-verification=qtKe_URPlmOxMMRvuj2vm0ehmNWXjw5klKOYvRKdqSU
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
google-site-verification=r1ZIgcLxBeZUXsntD9Ppy8wEzbPTuRXssndp05w4gUA
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
atlassian-sending-domain-verification=7fcf1d24-750c-4969-acaa-8d10a14625d1
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
CisionOne SAML=12e06eaa9bdcb554acbea38519c6a5d62121b1c7119029892fde2819e492a532
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
y0Iksl9beiFMYORN+SuiM2FOyye3KE52n8pmdqGL0Es0r+dLSj3r7lXp4qN+UQrNVzjxjNZPTpREgkPxJRjExg==
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
atlassian-domain-verification=xNJBUApXN7hpR4oT70VLfd/zzIN45ndbWHbardzEkHxOnAjpy0u5eJof+pyRACYw
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
hpe-greenlake-domain-verification=7567324662756d354f4a6f706764306d56383666496f3948556e2d4f7830456a
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
92njtaqeahc22miis2m2t5nfo0
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
cd1nsnrpj0p8elqjt5otohv9ge
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
j511td0jl0m90kpr7o2ent06f4
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
ljroek00q5389372jb7uv8peft
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
vpmsijjnh2u0u4on1i8lsmfn8k
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
00D46000000ZDRK=1TBQQ00000000cj
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
ZOOM_verify_jBApIZU9sr4lwMllsnjWKo
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
apple-domain-verification=HcLQcgAXFVSisOyB
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
MS=6A031B130D1C5A5F1A6C56F03E8A495EE63469A4
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
docusign=1df3a5f5-60ca-45b9-9a06-60e0d671dcdc
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
openai-domain-verification=dv-UHsgn2Ust4UhV8AewA4pMF5R
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
twilio-domain-verification=ffe0f14b844e94e6a73360c8516fb18a
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
onetrust-domain-verification=c7dea830bd554caea75702ca4a6c500e
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
anthropic-domain-verification-cyk8wq=u1jIl17DejLlobkn5TFK4LtCv
59.5 minutes (3571s) Optimal Speed 2h Prep Needed
brewers.com TXT
atlassian-domain-verification=xNJBUApXN7hpR4oT70VLfd/zzIN45ndbWHbardzEkHxOnAjpy0u5eJof+pyRACYw
60 minutes (3599s) Optimal Speed 2h Prep Needed
brewers.com NS
ns-204.awsdns-25.com
6 hours (21600s) Optimal Speed 24h Prep Needed
redirector-east.brewers.com A
34.117.109.43
1 hour (3600s) Optimal Speed 2h Prep Needed
www.brewers.com CNAME
redirector-east.brewers.com
9.5 minutes (571s) Lookup Overhead Instant Propagation

Note: This may not be all your DNS records — only the records we were able to find.

Actionable Recommendations & Best Practices
[Best Practice] Post-Migration TTL Restoration

Once your server migration is complete and verified stable for 24 hours, remember to raise your TTL values back to 3,600s or 86,400s to regain optimal DNS caching performance.

Understanding DNS TTL: Performance vs. Agility

DNS Time-to-Live (TTL) is a numerical setting (measured in seconds) attached to every DNS record. It dictates how long recursive DNS resolvers, ISPs, and web browsers are permitted to cache your server's IP address before requesting a fresh update.

Why Low TTL Hurts Everyday Speed

When you set a low TTL (e.g. 300s / 5 minutes) on a domain that is not migrating, every returning visitor's browser or local ISP must continuously send fresh DNS queries to resolve your server IP. This adds an extra 20ms to 150ms round-trip latency to page load times. For everyday stability, TTLs should be set to 3,600s (1 hour) or 86,400s (24 hours).

How to Manage TTL for Zero-Downtime Migration

If you are planning to switch web hosts or move to a new server IP, follow this two-step process:
1. 24 hours BEFORE migration: Reduce your A and CNAME TTL values to 300s (5 minutes).
2. 24 hours AFTER migration: Once the new IP is verified stable, raise your TTL back to 3,600s or 86,400s to regain maximum DNS caching speed.