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
6 seconds
Fastest record expiration duration
Longest TTL
1 hour (3600s)
Maximum cached retention duration
Records Inspected
42
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 (chase.com)

Host / Record Type Target / Value TTL (Duration) Everyday Performance Lens Migration Lens
chase.com A
146.143.141.57
59.6 minutes (3575s) Optimal Speed 2h Prep Needed
chase.com A
146.143.13.57
59.6 minutes (3575s) Optimal Speed 2h Prep Needed
chase.com A
146.143.83.57
59.6 minutes (3575s) Optimal Speed 2h Prep Needed
chase.com NS
ns2.jpmorganchase.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com NS
ns05.jpmorganchase.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com NS
ns06.jpmorganchase.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com NS
ns0119.secondary.cloudflare.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com NS
ns0140.secondary.cloudflare.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com NS
ns1.jpmorganchase.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com SOA
Primary NS: ns1.jpmorganchase.com (Admin: hostmaster.jpmchase.com)
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com MX
[Priority 40] cluster14a.us.messagelabs.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com MX
[Priority 10] cluster14.us.messagelabs.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com MX
[Priority 20] cluster14.us.messagelabs.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com MX
[Priority 30] cluster14.us.messagelabs.com
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com TXT
v=spf1 include:tpo.chase.com exists:%{i}.spf.chase.com exists:%{i}.spf.hc4673-96.iphmx.com exists:%{i}.spf.hc4698-8.iphmx.com -all
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
_m47rp0d9u3ci4ycif1echp310q0yy09
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
docusign=500adee6-4cca-451d-bcd8-2813346419c8
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
docusign=b04ddbec-21ac-4d6b-bb8b-3f1a3bca079f
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
airtable-verification=1d59ed5062280d21aeef0c14aaf4f950
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
smartsheet-site-validation=JdBS3Kn_332V6dI9U0iq0TV3RZZXTUhL
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
DirectFedAuthUrl=https://idauatg2.jpmorganchase.com/adfs/ls/
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
onetrust-domain-verification=ccee45576c1e4fbfaa4014725a73344f
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
pendo-domain-verification=1f6e5677-d405-438e-88ba-141766793ce8
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
sinch-domain-verification=6848bb42-da6f-49cf-8974-920af9cf1806
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
google-site-verification=PfSAyrffyVUKXLc1Ew8C2IFPWkjufFSsbboFz_24Qt4
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
google-site-verification=iZwZzo1YPl0G29U136Suzn4c1VptcA_LkvvdWOYC6B0
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
google-site-verification=w00TwyVREI5RpqAT9hqSLZVvZcZi46578G57D1aMGeE
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
wiz-domain-verification=66aa74155d5e84d10ed4b5a786a66f94063cff3b4c7e11d09fb46f027736dbf0
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
wiz-domain-verification=68c6d9fa0c4bdd60150d3df50635cd0fcf4af6af079771d90239d10add2c2967
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
wiz-domain-verification=a0d8d067bcb1cdd44255d0633a31df3ba13c82e30f27c080519b0b85ba734d32
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
wiz-domain-verification=ccd3ec907fff510311f6a14b2a659fcb83adea2818bb6e78503239d2877e8657?
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
atlassian-domain-verification=PZApk1vJjd7scChzBMQy2d4NEwk4Bt26obCVACc7vWiOBVCOxTOV4/EB9LMexMnl
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
atlassian-domain-verification=Ua2Fovb97Ak39kxh4koulfhVlpieV1PLhaMkdZpzINDMQGlcvLV+ORgL2QmOryw+
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
atlassian-domain-verification=wUjrfh2T73RznZOKmEZfc0mRF92bjC7JyjSgRXg9Yt2e9ZMRZwafUO6GPJaecYOh
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
atlassian-domain-verification\u003dpD6ozLCGDinP/R+vd5R9hpoPCSOmTFTHfWPK633PXEtELa5KlVDw4w1Pnn02aTdC
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com CAA
Direct IP
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com CAA
Direct IP
1 hour (3600s) Optimal Speed 2h Prep Needed
chase.com A
146.143.13.57
59.8 minutes (3588s) Optimal Speed 2h Prep Needed
chase.com TXT
atlassian-domain-verification=Ua2Fovb97Ak39kxh4koulfhVlpieV1PLhaMkdZpzINDMQGlcvLV+ORgL2QmOryw+
1 hour (3600s) Optimal Speed 2h Prep Needed
e129412.a.akamaiedge.net A
23.219.89.146
6 seconds Lookup Overhead Instant Propagation
e129412.a.akamaiedge.net A
23.219.89.145
6 seconds Lookup Overhead Instant Propagation
www.chase.com CNAME
gtm.www.chase.com.akadns.net
59.8 minutes (3588s) 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.