Convert DNS TTL seconds into human-readable time — or build a TTL from days, hours, and minutes. Enter your TTL in seconds to see the breakdown, or fill in Days, Hours, and Minutes to calculate the equivalent seconds. Outputs include Days, Hours, Minutes, Seconds, and the total TTL in seconds — useful for configuring DNS records without mentally converting large numbers.
TTL in Seconds
--
Days
--
Hours
--
Minutes
--
Remaining Seconds
--
TTL stands for Time to Live. In DNS, it is a value in seconds that tells resolvers (like your ISP or a corporate DNS server) how long to cache a DNS record before checking for updates. A higher TTL reduces DNS query load; a lower TTL allows faster propagation of record changes.
The DNS standard (RFC 1035) defines TTL as a 32-bit integer representing seconds. While this is precise and universally understood by machines, humans find it awkward to mentally convert values like 86400 or 172800 into days and hours — which is exactly what this calculator solves.
Common recommendations vary by record type and change frequency. 300 seconds (5 minutes) is used for records that may change soon, 3600 seconds (1 hour) is a general-purpose default, and 86400 seconds (1 day) suits stable records like MX or NS entries. Lower TTLs increase DNS query volume but speed up propagation.
You can enter a TTL value in seconds to instantly see it broken down into days, hours, minutes, and remaining seconds. Alternatively, fill in the Days, Hours, and Minutes fields to calculate the equivalent total TTL in seconds — useful when your DNS panel requires a seconds value but you think in human time.
A very high TTL (e.g. 604800 — one week) means DNS resolvers will cache your record for that entire duration. If you need to change the record (such as pointing a domain to a new server), clients will continue seeing the old value until the TTL expires. It is best practice to lower your TTL before making planned changes.
The DNS specification allows TTL values up to 2,147,483,647 seconds (a signed 32-bit integer), which is over 68 years. In practice, most DNS providers cap TTL at 86400 seconds (1 day) or lower for reliability and manageability.
TTL itself does not affect how fast your website loads, but it does affect how quickly DNS changes propagate globally. During the cached TTL window, users are directed to the previously resolved IP address. Lowering TTL before a migration ensures that fewer users experience downtime during the DNS cutover.
No — TTL is a broader networking concept. In IP packets, TTL is a hop counter that prevents packets from looping indefinitely across routers. In HTTP caching and CDN configurations, TTL (often called Cache-Control max-age) determines how long a cached resource is considered fresh. This calculator focuses on the DNS use case.