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
80 / 100
Evaluates lookup speed vs cache efficiency
Shortest TTL
5 minutes (300s)
Fastest record expiration duration
Longest TTL
5.8 days (499128s)
Maximum cached retention duration
Records Inspected
24
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 (fullcompass.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
fullcompass.com A
104.19.185.80
23.5 hours (84600s) Optimal Speed 24h Prep Needed
fullcompass.com A
104.19.186.80
23.5 hours (84600s) Optimal Speed 24h Prep Needed
fullcompass.com NS
ns1.dnsmadeeasy.com
19.7 hours (70900s) Optimal Speed 24h Prep Needed
fullcompass.com NS
ns2.dnsmadeeasy.com
19.7 hours (70900s) Optimal Speed 24h Prep Needed
fullcompass.com NS
ns3.dnsmadeeasy.com
19.7 hours (70900s) Optimal Speed 24h Prep Needed
fullcompass.com NS
ns4.dnsmadeeasy.com
19.7 hours (70900s) Optimal Speed 24h Prep Needed
fullcompass.com NS
ns0.dnsmadeeasy.com
19.7 hours (70900s) Optimal Speed 24h Prep Needed
fullcompass.com SOA
Primary NS: ns10.digicertdns.com (Admin: dns.digicertdns.com)
1 day (86400s) Optimal Speed 24h Prep Needed
fullcompass.com MX
[Priority 10] gw199095.fortimail.com
23.5 hours (84600s) Optimal Speed 24h Prep Needed
fullcompass.com TXT
_g8x8h37j837200tpxql17f88mtbazi8
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
klaviyo-site-verification=V4Cvyi
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
z3241vl2j6jk37mpqvwktv6ng492ryd1
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
apple-domain-verification=RHI4cLk7JYy0Zrid
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
SFMC-kc0GFEWeFFqySxQs6lbV7A_yFish7cKngGEnwQUo
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
google-site-verification=TVkWK97I1dk3fphQ-amiiYZiGKkMO04RRviH3lzssfc
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
sentinelone-domain-verification=grWlsejbMGN8gp1Hm0Mizmh22HrQzV7m2Xnqvt2aiTy
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
v=spf1 mx include:spf.myconnectwise.net include:amazonses.com include:spf.protection.outlook.com include:cust-spf.exacttarget.com include:_spf.salesforce.com ip4:216.165.134.192/27 ip4:96.61.37.8/32 ip4:82.98.199.95/32 ~all
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
MS=ms24303805
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
00D1U000000yDiF=1TBTN00000000xh
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com TXT
77zpjl5qnvdhyz05kvlbpy3fyv73zrlm
30 minutes (1800s) Optimal Speed 2h Prep Needed
fullcompass.com NS
ns1.dnsmadeeasy.com
19.7 hours (70901s) Optimal Speed 24h Prep Needed
www.fullcompass.com.cdn.cloudflare.net A
104.19.185.80
5 minutes (300s) Lookup Overhead Instant Propagation
www.fullcompass.com.cdn.cloudflare.net A
104.19.186.80
5 minutes (300s) Lookup Overhead Instant Propagation
www.fullcompass.com CNAME
www.fullcompass.com.cdn.cloudflare.net
5.8 days (499128s) High Retention 24h Prep Needed

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.