TTL calculator

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from TTL calculator

TTL calculator helps you translate a time-to-live value into a readable duration. TTL commonly expresses how long cached information may be reused, and the unit in many network settings is seconds. Time-related results are easiest to interpret when the input meaning is explicit: a calendar date, a local clock reading, an exact instant, and an elapsed duration are different kinds of information. Confirm whether the service expects seconds, milliseconds, or a duration string before copying a value. Use the worked example to establish the expected behavior before entering a more complicated case. A TTL is a cache-lifetime setting, not a guarantee that every observer will update at exactly that moment. Cache state and implementation behavior matter. Keep the original date or duration alongside the result when sharing it, and include a time zone whenever the result refers to an actual moment. That context makes the result easier to check and prevents another reader from silently assuming a different clock or calendar convention.

Guide updated October 13, 2026

How to use this tool

1. For duration-to-TTL conversion, set Days, Hours, Minutes, and Seconds. One hour with the other fields zero corresponds to 3,600 seconds.
2. For the reverse direction, enter 3600 in the TTL input and inspect the human-readable time result.
3. Confirm that the application using the value expects seconds. Do not paste it into a milliseconds field without converting the scale.
4. Keep the source system and cache context with the duration. This page converts values and does not inspect or change live cache state.

SEE IT IN PRACTICE

A worked example

TTL 3600 seconds

1 hour

There are sixty seconds in a minute and sixty minutes in an hour, so 3,600 seconds equals one hour.

Convert seconds into an understandable interval

A TTL of 3,600 seconds is one hour, while 86,400 seconds is twenty-four hours. These conversions help review cache settings and explain numeric values in configuration. Keep the unit explicit because other applications may express a lifetime in milliseconds or another scale. A duration conversion does not inspect the current state of any cache or change a server setting.

Read the value at the right point in the lifecycle

An authoritative record’s configured TTL and a recursive resolver’s remaining TTL answer different questions. Lowering a configured value does not retroactively replace answers already cached under an earlier lifetime. Use the converted duration to understand the number, then inspect authoritative and cached responses separately when investigating behavior. Avoid treating a convenient duration label as an exact global propagation deadline.

A duration does not describe cache state

The same TTL value can be seen at different points in a cache lifecycle. An authoritative setting describes an intended lifetime, while a cached response may show the remaining lifetime. Neither is a schedule for every client to refresh simultaneously. Use the converted duration to understand the number, then inspect the actual cache or DNS behavior separately if propagation is the concern.

When this tool is useful

• Read DNS TTL values with the relevant clock and calendar assumptions made explicit.
• Compare cache lifetimes using a simple, reproducible example.
• Prepare a duration setting while keeping the original input available for comparison.

Tips for a better result

• A TTL is a cache-lifetime setting, not a guarantee that every observer will update at exactly that moment. Cache state and implementation behavior matter.
• Confirm whether the service expects seconds, milliseconds, or a duration string before copying a value.
• Keep dates unambiguous when sharing results. A year-month-day date is easier to interpret internationally than a numeric date whose month and day order is unclear.

Frequently asked questions