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
5 minutes (300s)
Fastest record expiration duration
Longest TTL
1 day (86400s)
Maximum cached retention duration
Records Inspected
17
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
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 (ssvcs.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
ssvcs.com A
104.21.18.151
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com A
172.67.182.159
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com NS
nola.ns.cloudflare.com
1 day (86400s) Optimal Speed 24h Prep Needed
ssvcs.com NS
odin.ns.cloudflare.com
1 day (86400s) Optimal Speed 24h Prep Needed
ssvcs.com SOA
Primary NS: nola.ns.cloudflare.com (Admin: dns.cloudflare.com)
30 minutes (1800s) Optimal Speed 2h Prep Needed
ssvcs.com MX
[Priority 40] ssvcs-com-tls40.mxthunder.com
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com MX
[Priority 10] ssvcs-com-tls10.mxthunder.com
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com MX
[Priority 20] ssvcs-com-tls20.mxthunder.com
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com MX
[Priority 30] ssvcs-com-tls30.mxthunder.com
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com TXT
v=spf1 mx a:mail.ssvcs.com include:spf.spamhero.com include:spf.protection.outlook.com include:_netblocks.accellion.com -all
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com AAAA
2606:4700:3037::ac43:b69f
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com AAAA
2606:4700:3032::6815:1297
5 minutes (300s) Lookup Overhead Instant Propagation
ssvcs.com NS
odin.ns.cloudflare.com
18.8 hours (67570s) Optimal Speed 24h Prep Needed
www.ssvcs.com A
172.67.182.159
5 minutes (300s) Lookup Overhead Instant Propagation
www.ssvcs.com A
104.21.18.151
5 minutes (300s) Lookup Overhead Instant Propagation
www.ssvcs.com AAAA
2606:4700:3032::6815:1297
5 minutes (300s) Lookup Overhead Instant Propagation
www.ssvcs.com AAAA
2606:4700:3037::ac43:b69f
5 minutes (300s) 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
[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.

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