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
40 / 100
Evaluates lookup speed vs cache efficiency
Shortest TTL
1 minute (60s)
Fastest record expiration duration
Longest TTL
1 day (86400s)
Maximum cached retention duration
Records Inspected
16
A, AAAA, CNAME, MX, TXT, NS, SOA
1. Everyday Load Performance
Sub-optimal Latency
Sub-optimal DNS Caching (High Lookup Latency)
Your DNS records have short TTL values. Browsers and ISPs are forced to re-query your DNS frequently, adding unneeded connection latency for visitors unless you are actively migrating servers.
2. Server Migration Agility
Short Prep Needed
Requires Short Pre-Migration Lowering (2–4 Hours)
Your web records have moderate TTLs. Lower your A and CNAME TTLs to 300 seconds 4 hours before switching servers to guarantee smooth cutover.

DNS Record TTL Inventory (webstix.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
webstix.com A
192.168.1.164
19.8 hours (71392s) Optimal Speed 24h Prep Needed
webstix.com NS
jean.ns.cloudflare.com
20 hours (72131s) Optimal Speed 24h Prep Needed
webstix.com NS
jack.ns.cloudflare.com
20 hours (72131s) Optimal Speed 24h Prep Needed
webstix.com SOA
Primary NS: jack.ns.cloudflare.com (Admin: dns.cloudflare.com)
30 minutes (1800s) Optimal Speed 2h Prep Needed
webstix.com MX
[Priority 10] alt3.aspmx.l.google.com
19.2 hours (68960s) Optimal Speed 24h Prep Needed
webstix.com MX
[Priority 10] alt4.aspmx.l.google.com
19.2 hours (68960s) Optimal Speed 24h Prep Needed
webstix.com MX
[Priority 1] aspmx.l.google.com
19.2 hours (68960s) Optimal Speed 24h Prep Needed
webstix.com MX
[Priority 5] alt1.aspmx.l.google.com
19.2 hours (68960s) Optimal Speed 24h Prep Needed
webstix.com MX
[Priority 5] alt2.aspmx.l.google.com
19.2 hours (68960s) Optimal Speed 24h Prep Needed
webstix.com TXT
v=spf1 mx a include:_spf.getresponse.com a:67.192.29.167 ip4:72.32.156.240 include:_spf.google.com ~all
1 minute (60s) Lookup Overhead Instant Propagation
webstix.com TXT
google-site-verification=b0jJYo_s-udhpsqMZsggV3crzeo-RlbYXLTlHyE93wI
1 minute (60s) Lookup Overhead Instant Propagation
webstix.com A
192.168.1.164
19.5 hours (70160s) Optimal Speed 24h Prep Needed
webstix.com MX
[Priority 1] aspmx.l.google.com
15.3 hours (55217s) Optimal Speed 24h Prep Needed
webstix.com NS
jack.ns.cloudflare.com
20 hours (72103s) Optimal Speed 24h Prep Needed
webstix.com A
192.168.1.164
20.3 hours (73201s) Optimal Speed 24h Prep Needed
www.webstix.com CNAME
webstix.com
1 day (86400s) Optimal Speed 24h Prep Needed
Actionable Recommendations & Best Practices
[Performance] Increase TTL for Everyday Traffic

If you are not currently migrating servers, increase your A, AAAA, and CNAME TTL values to at least 3,600s (1 hour) or 86,400s (24 hours). This allows ISPs and browsers to cache your DNS response, cutting initial page connection time.

[Performance] Eliminate Ultra-Low TTLs (< 300s)

Ultra-low TTLs cause excessive DNS query traffic and can bottleneck user connection times. Unless backed by a high-frequency global DNS edge/anycast provider (like Cloudflare or Route53), raise these TTLs.

[Migration Prep] Pre-Migration TTL Reduction Checklist

Planning a server move? 24 hours BEFORE updating your A/CNAME record IP addresses, reduce their TTL setting in your DNS portal to 300 seconds (5 minutes). This ensures fast propagation during the cutover.

[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.