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
100 / 100
Evaluates lookup speed vs cache efficiency
Shortest TTL
49.5 minutes (2967s)
Fastest record expiration duration
Longest TTL
1 hour (3600s)
Maximum cached retention duration
Records Inspected
17
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
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 (justintimehvac.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
justintimehvac.com A
34.48.55.64
49.5 minutes (2971s) Optimal Speed 2h Prep Needed
justintimehvac.com NS
ns29.domaincontrol.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com NS
ns30.domaincontrol.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com SOA
Primary NS: ns29.domaincontrol.com (Admin: dns.jomax.net)
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com MX
[Priority 10] alt4.aspmx.l.google.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com MX
[Priority 1] aspmx.l.google.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com MX
[Priority 5] alt1.aspmx.l.google.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com MX
[Priority 5] alt2.aspmx.l.google.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com MX
[Priority 10] alt3.aspmx.l.google.com
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com TXT
google-site-verification=tLlUi0j2YrQ6jvEr2rvqUYPHI0R4lhDV7cFqNtXYiX4
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com TXT
google-gws-recovery-domain-verification=75739613
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com TXT
v=spf1 include:dc-aa8e722993._spfm.justintimehvac.com ~all
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com TXT
google-site-verification=KdOLK0Dnx4Avb8LvL-V104Y8XV_5IbQD5_z5Et17gE0
1 hour (3600s) Optimal Speed 2h Prep Needed
justintimehvac.com A
34.48.55.64
49.5 minutes (2969s) Optimal Speed 2h Prep Needed
justintimehvac.com TXT
v=spf1 include:dc-aa8e722993._spfm.justintimehvac.com ~all
49.6 minutes (2978s) Optimal Speed 2h Prep Needed
justintimehvac.com A
34.48.55.64
49.5 minutes (2967s) Optimal Speed 2h Prep Needed
www.justintimehvac.com CNAME
justintimehvac.com
1 hour (3600s) Optimal Speed 2h Prep Needed

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

Actionable Recommendations & Best Practices
[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.