DNS TTL Check - View Time To Live for All DNS Records
No logs stored • Results not cached on our servers
Check TTL values for 7 DNS record types in one lookup. Get a health score, see min/max/average statistics, and receive recommendations for optimal settings.
Free DNS TTL Checker Tool
Check DNS TTL Values
Enter a domain to see Time To Live values for all DNS records
What is DNS TTL and Why Does It Matter?
DNS TTL (Time To Live) is a value in seconds that tells DNS resolvers how long to cache a DNS record before requesting fresh data from authoritative nameservers. TTL directly affects how quickly DNS changes propagate across the internet—lower TTLs enable faster changes but increase DNS query load, while higher TTLs reduce queries but slow propagation.
What You'll Discover
Can Find
- TTL values for A, AAAA, MX, CNAME, TXT, NS, SOA records
- Health score (0-100) with Excellent/Good/Fair/Poor rating
- Summary statistics: min, max, average TTL
- Recommendations for suboptimal TTL configurations
- Human-readable format alongside raw seconds
Cannot Find
- Historical TTL values over time
- Real-time TTL monitoring or alerts
- TTL remaining vs. configured (sees cached TTL)
- CAA, SRV, or PTR record TTLs
How to Check DNS TTL Values
Analyze TTL settings for all major DNS record types with health scoring and recommendations.
Enter Domain Name
Type the domain you want to check (e.g., <code>google.com</code>, <code>example.org</code>). No need to include <code>http://</code> or <code>www.</code>
Check TTL Values
Click the 'Check TTL' button to query all 7 record types: A, AAAA, MX, CNAME, TXT, NS, and SOA. Each record's TTL is retrieved and analyzed.
Review Health Score
See your domain's overall TTL health score (0-100) with an Excellent, Good, Fair, or Poor rating. The breakdown shows how many records fall into each status category.
Check Individual TTLs
Review each record type's TTL with color-coded status indicators: green (good), blue (info), yellow (warning), or red (critical).
Read Recommendations
For any suboptimal TTL values, get specific, actionable recommendations with suggested values and explanations based on industry best practices.
Understanding Your DNS TTL Results
Each result shows TTL values with analysis, health scoring, and actionable recommendations.
Record Type
The DNS record type being analyzed: A (IPv4), AAAA (IPv6), MX (mail), CNAME (alias), TXT (text/SPF/DKIM), NS (nameservers), or SOA (zone authority).
A
TTL Value
The time-to-live in seconds, shown in both raw format (3600s) and human-readable format (1h). This is how long DNS resolvers will cache this record.
3600s (1h)
Status
Color-coded health indicator: Good (green, optimal range), Info (blue, higher than typical), Warning (yellow, too low/high), Critical (red, very low TTL).
✅ Good
Health Score
Overall score from 0-100 based on all record TTLs. Excellent (all optimal), Good (mostly optimal), Fair (some warnings), Poor (critical issues present).
85 - Good
Summary Statistics
Minimum, maximum, and average TTL across all found records. Shows which record types have the lowest and highest TTLs for quick identification.
Min: 300s (A), Max: 86400s (NS)
Recommendations
Specific suggestions for any TTL values outside optimal ranges. Includes current value, suggested value, severity level, and reasoning.
SOA: Increase to 86400s (1d)
Why Choose Our DNS TTL Checker
The most comprehensive TTL analysis tool with health scoring and actionable recommendations.
7 Record Types in One Lookup
Check TTL for A, AAAA, MX, CNAME, TXT, NS, and SOA records simultaneously. No need for separate lookups per record type.
Health Score (0-100)
Get an overall rating with Excellent, Good, Fair, or Poor classification. See breakdown showing how many records fall into each status category.
Smart Recommendations
Receive actionable suggestions for any suboptimal TTL values. Each recommendation includes current value, suggested value, and reasoning based on record type.
Human-Readable Format
TTL values displayed as both raw seconds (3600s) and readable format (1h, 5m, 2d). Easy to understand at a glance without mental math.
Summary Statistics
See minimum, maximum, and average TTL across all records. Quickly identify which record types have the most extreme values.
Export & Share
Download complete analysis in JSON, CSV, or plain text format. Share results via URL parameters for easy collaboration.
When You Need to Check DNS TTL
Essential scenarios where understanding TTL values helps optimize your DNS configuration.
Pre-Migration Planning
Before DNS changes, check current TTL values to understand propagation timing. Lower TTL 24-48 hours in advance so the change propagates faster when you make it.
DNS Optimization Audit
Identify TTL configurations that are too aggressive (causing excessive queries) or too conservative (slowing propagation). Get recommendations for optimal values.
Troubleshoot Slow Changes
When DNS changes take longer than expected to propagate, check TTL to understand why. High TTLs mean resolvers hold onto old data longer.
New Domain Setup
Verify TTLs are correctly configured from the start. Catch issues before they cause problems during future changes or migrations.
How DNS TTL Works and Best Practices
Understanding TTL is essential for DNS management, migrations, and troubleshooting propagation issues.
How DNS Caching and TTL Work
When a DNS resolver looks up a record, it receives a TTL value in seconds. The resolver caches the record for that duration, serving cached responses to subsequent queries. After TTL expires, the resolver must fetch fresh data from authoritative nameservers. This caching system reduces DNS traffic and improves response times, but means changes don't propagate instantly. The trade-off: lower TTLs enable faster changes but increase query load on your nameservers and DNS providers.
Recommended TTL Values by Record Type
Different record types serve different purposes and need different TTL strategies: <strong>A/AAAA records</strong> (300-3600s): Balance between quick changes and query efficiency. Use lower values during transitions. <strong>MX records</strong> (3600-14400s): Email needs stability; higher TTLs prevent mail delivery issues during brief outages. <strong>NS/SOA records</strong> (86400-172800s): Nameserver changes are rare; high TTLs reduce unnecessary queries. <strong>TXT records</strong> (300-3600s): SPF and DKIM may need updates; moderate TTLs provide flexibility. <strong>CNAME records</strong> (300-3600s): Similar to A records; balance flexibility with caching efficiency.
TTL Migration Strategy
For planned DNS changes, follow this strategy to minimize propagation time: <strong>Step 1:</strong> Use this tool to check current TTL values. <strong>Step 2:</strong> Lower TTL to 300s (5 minutes) 24-48 hours before the change—this gives time for the new, lower TTL to propagate. <strong>Step 3:</strong> Make your DNS change (IP, mail server, etc.). <strong>Step 4:</strong> Wait for propagation (now much faster due to low TTL). <strong>Step 5:</strong> After changes are confirmed, restore normal TTL values to reduce query load.
Common TTL Values Reference
Quick reference for typical TTL settings: <strong>30 seconds:</strong> Emergency failover only—extremely high query volume. <strong>300 seconds (5 min):</strong> Dynamic content, CDNs, pre-migration. <strong>900 seconds (15 min):</strong> Good balance for active domains. <strong>3600 seconds (1 hour):</strong> Standard A/AAAA record default. <strong>14400 seconds (4 hours):</strong> Stable MX records. <strong>86400 seconds (1 day):</strong> NS/SOA records, stable infrastructure. <strong>604800 seconds (1 week):</strong> Rarely changed records—use with caution.
DNS TTL Checker Specifications
- Record Types Checked
- A, AAAA, MX, CNAME, TXT, NS, SOA (7 types)
- Health Score Range
- 0-100 with status breakdown
- TTL Thresholds
- <60s critical, <300s warning, >604800s warning
- Format Display
- Human-readable (1h, 5m) + raw seconds
- Query Method
- Live DNS queries via dnspython
- Query Timeout
- 15 seconds overall
- Cache Duration
- 5 minutes
- Export Formats
- JSON, CSV, Plain Text
- API Access
- Free, no key required
Frequently Asked Questions
What is DNS TTL (Time To Live)?
DNS TTL is a value in seconds that tells DNS resolvers how long to cache a DNS record before requesting fresh data from authoritative nameservers. A TTL of 3600 means the record will be cached for 1 hour. TTL directly affects how quickly DNS changes propagate across the internet.
What is a good TTL value for DNS records?
Good TTL values depend on the record type: A/AAAA records typically use 300-3600 seconds (5 minutes to 1 hour), MX records use 3600-14400 seconds (1-4 hours) for stability, NS/SOA records use 86400-172800 seconds (1-2 days), and TXT records (SPF, DKIM) use 300-3600 seconds. Lower TTLs allow faster changes but increase DNS traffic.
How does TTL affect DNS propagation?
DNS propagation time depends largely on TTL values. When you change a DNS record, it takes up to the old TTL duration for all cached copies to expire. For example, if your A record had a 24-hour TTL, changes might take up to 24 hours to reach all users. Lowering TTL before changes speeds up propagation.
What is a TTL of 3600?
A TTL of 3600 means DNS resolvers will cache the record for 3600 seconds, which equals 1 hour. This is a common default TTL for A records—it balances quick changes with reasonable query efficiency. After 1 hour, resolvers will fetch fresh data from your nameservers.
Why is a very low TTL bad?
Very low TTLs (under 60 seconds) cause excessive DNS queries. Every resolver must fetch fresh data frequently, increasing load on your nameservers and DNS provider. This can slow resolution and potentially increase costs. Unless you need rapid failover, TTLs below 5 minutes are usually unnecessary.
Should I lower TTL before DNS changes?
Yes! This is a best practice. Lower your TTL 24-48 hours before planned DNS changes so that by the time you make the change, most resolvers have the lower TTL cached. This ensures faster propagation. After changes complete, restore normal TTL to reduce query load.
What happens if TTL is too high?
High TTLs (over 1 week) mean DNS changes propagate very slowly. If you need to change your IP address or mail server quickly, users will continue reaching the old destination until cached records expire. This can cause extended downtime during migrations or emergency changes.
What does the health score mean?
The health score (0-100) rates your domain's overall TTL configuration: Excellent means all records have optimal TTLs, Good means mostly optimal with some higher values, Fair means some warnings that need attention, and Poor means critical issues like very low TTLs that should be addressed.
Which record types do you check?
We check 7 DNS record types: A (IPv4 addresses), AAAA (IPv6 addresses), MX (mail servers), CNAME (aliases), TXT (text records including SPF and DKIM), NS (nameservers), and SOA (zone authority). Each has different recommended TTL ranges based on its purpose.
What is the SOA minimum TTL?
The SOA (Start of Authority) record contains a 'minimum' field that specifies the negative caching TTL—how long resolvers cache 'NXDOMAIN' (domain not found) responses. This affects how quickly new subdomains become visible and is analyzed separately from positive record TTLs.
Check Your Domain's TTL Values Now
Analyze DNS TTL configuration, get a health score, and receive recommendations for optimal settings. Enter any domain to get started.
Check DNS TTL