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
30 / 100
Evaluates lookup speed vs cache efficiency
Shortest TTL
7 seconds
Fastest record expiration duration
Longest TTL
1 day (86400s)
Maximum cached retention duration
Records Inspected
47
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 (digitas.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
digitas.com A
13.248.188.215
24 hours (86351s) Optimal Speed 24h Prep Needed
digitas.com A
76.223.58.27
24 hours (86351s) Optimal Speed 24h Prep Needed
digitas.com NS
ns1.publicisgroupe.com
1 day (86400s) Optimal Speed 24h Prep Needed
digitas.com NS
ns3.publicisgroupe.com
1 day (86400s) Optimal Speed 24h Prep Needed
digitas.com NS
ns5.publicisgroupe.com
1 day (86400s) Optimal Speed 24h Prep Needed
digitas.com SOA
Primary NS: ns1.publicisgroupe.com (Admin: hostmaster.digitas.com)
1 day (86400s) Optimal Speed 24h Prep Needed
digitas.com MX
[Priority 0] digitas-com.mail.protection.outlook.com
59.6 minutes (3577s) Optimal Speed 2h Prep Needed
digitas.com TXT
_globalsign-domain-verification=5HjBn96y9s2DypAMUGfqSRIp7dPODcfi8sq9MuRjbp
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
_globalsign-domain-verification=8sxDUbngKQpauz4ygSRfx55o_51IqOFx17mcUEPL4c
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
_globalsign-domain-verification=D6g48un2uUfkr7wT2SOpTEneh-kQtKG-X8f6luuZhq
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
_globalsign-domain-verification=DXI3-_vNtjUJxCr95qr3hNCoK6wJkjes5C2HeXUvnl
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
_globalsign-domain-verification=FRcLSyJUsN3uyIErLUJ6X4ms55snBSdZbprK0-Km5F
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
_globalsign-domain-verification=s9W2smTWer-SJ5S76NxtMql3JJeBvYJGvgFowFHknh
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
_globalsign-domain-verification=vu7fCg73IhW49lvkmRQgHlqf5WsM9Imw9M1lXF46vu
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
SbWQEXGxa8BmF8S8MSXCgJYU6gtmarlP/ScQewo2Ub51TDq98rh/ljuHgK0SS/I7GPHStjH3wEpUmPj+eSKtDw==
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
adYXkeYwLlR8/HYSbiRzkMZyglAAYNTe2mSWwBdZdwzY57Hq+mMDZPxWlp/TDShORWagsP6VlsYbFC0PRB7nXQ==
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
adobe-idp-site-verification=87f5e0928a736cbc8208794658d0974e68d7fda56cdc6388eb44e4a7a2468d66
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
adobe-idp-site-verification=eec18b8e33118b9c9e86f55e5f921d48d53f1d7088746d1a69d1b19691e60dde
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
cisco-ci-domain-verification=30d78b8aceb7bcbb35dc57673cf0f42666f65f1dbb36e27ff663c810686fe65b
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
atlassian-domain-verification=FKlLMZ26G9OdKvxTlp/r4AYZfTOACJ/G/gJtgaJ9FaaYxZHWfyr8eWdFOGpOOHaj
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
atlassian-domain-verification=OW1vzpM/T4RVvS6/18JpwjVUKQtg3oUi1rgalKPiOtKNPi3D4c3p7k9InDAQH6aW
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
atlassian-domain-verification=cnk50g55zo3w9khIXKZ8UqHvNv3oFO6bTASbQOTepy0sKDCeVzPVYQYqjA3VZkSH
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
figma-domain-verification=883b1e259a15c4ffa043ff1c2c8428a53234fbc1f00e72b746f4f5295a531f6a-1743087814
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
v=spf1 include:publicis.com include:sendgrid.net include:139642454.spf07.hubspotemail.net include:aspmx.pardot.com ~all
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
asv=70db6303c26e04a5cb49372ce2145a6d
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
MS=1B72C289E846A0FAFE02F645FE6F0FFCFB541F39
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
brevo-code:e74e057263770cde2847265dc46a48a8
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
docusign=bdba0d01-f107-4571-a3f6-caa8ae69adb1
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
airtable-verification=caf5dbe3c361c37fe7d0de354d9d909c
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
openai-domain-verification=dv-KgwFHXoZJIv5ZodWEK4kbreR
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
rovag_verification_token=A3C780BA0E094B498C86A604E6624624
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
cursor-domain-verification-d10qer=t2JKrquqGKXxJYRn3WPM1KODN
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
smartsheet-site-validation=H2YC8dgOVYTtOCnKcXZMVlfKdInV1NJP
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
cnk50g55zo3w9khIXKZ8UqHvNv3oFO6bTASbQOTepy0sKDCeVzPVYQYqjA3VZkSH
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
extensis-domain-verification=efbcb3b3-8921-4174-9da6-f39deec9c0e2
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
google-site-verification=0I5gwBs_PeDk-t3eZHfMmPbl8MgYwYHtOcGdFy4YudM
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
google-site-verification=5WY7l-kECZ9Ncp6Qgq9g-PLaIbBxPrAm21X-PKZePdQ
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
google-site-verification=OOSqdqee6mWAJJmh5yrwx3b_vn2lIM3WgNVjEdfxj1o
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com TXT
google-site-verification=rOPg2a3PrFKHSy5QZEJXSjwm34CHmzPT1McGZg4Gh4Y
24 hours (86365s) Optimal Speed 24h Prep Needed
digitas.com A
13.248.188.215
24 hours (86346s) Optimal Speed 24h Prep Needed
digitas.com MX
[Priority 0] digitas-com.mail.protection.outlook.com
1 hour (3600s) Optimal Speed 2h Prep Needed
digitas.com TXT
rovag_verification_token=A3C780BA0E094B498C86A604E6624624
1 day (86400s) Optimal Speed 24h Prep Needed
duw94ip4l1ua5.cloudfront.net A
13.224.187.8
7 seconds Lookup Overhead Instant Propagation
duw94ip4l1ua5.cloudfront.net A
13.224.187.31
7 seconds Lookup Overhead Instant Propagation
duw94ip4l1ua5.cloudfront.net A
13.224.187.55
7 seconds Lookup Overhead Instant Propagation
duw94ip4l1ua5.cloudfront.net A
13.224.187.90
7 seconds Lookup Overhead Instant Propagation
www.digitas.com CNAME
web.digitas.msvc.cloud
2 hours (7151s) 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
[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.

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