Convert TTL seconds to human-readable format. Look up TTL values for all DNS records of any domain.
TTL Calculator converts TTL seconds into human-readable format (1 hour / 24 hours / 7 days). Plus reverse — minutes/hours/days to seconds. Helps when configuring DNS and Cache-Control headers.
Enter seconds or use presets to convert TTL to days/hours/minutes
| Seconds | Duration | Use case |
|---|---|---|
| 60 | 1 minute | DNS migration / temporary |
| 300 | 5 minutes | Frequently updated records |
| 900 | 15 minutes | Dynamic IP / load balancing |
| 3600 | 1 hour | Standard for most records |
| 14400 | 4 hours | Stable records (MX, NS) |
| 86400 | 1 day | Very stable, rarely changed |
| 604800 | 1 week | NS / SOA serial records |
Enter a domain to see TTL values for all its DNS records
TTL (Time To Live) in DNS defines how long resolvers cache a record. Choosing the right TTL affects how fast DNS changes propagate and the load on the authoritative server.
Convert seconds to readable format and back: 86400 = 1 day.
Estimate when a DNS record change will be visible to all users worldwide.
TTL recommendations before server migration: when to lower, when to restore.
Reference for standard TTLs: 300, 3600, 86400 — which to use for which records.
DNS migration planning
TTL record optimization
cache time calculation
TTL understanding for APIs
DNS monitor notifies you when A, MX, or TXT records change.
Sign up freeTTL (Time To Live) is a DNS record parameter that specifies how many seconds a resolver can cache the record before requesting a fresh copy from the authoritative nameserver. A low TTL (60–300 s) means changes propagate quickly but increases load on DNS servers. A high TTL (3600–86400 s) reduces lookup latency and server load but delays propagation after a record change. Use this calculator to convert between seconds and human-readable formats before updating your DNS records.
TTL (Time To Live) is how long a DNS record stays cached. Determines how long resolvers keep the record without re-querying.
300 sec (5 min) for frequently changing records. 3600 (1 hour) for stable ones. 86400 (1 day) for rarely changing MX/NS.
Longer-form reading on this topic from the knowledge base.
Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.