Skip to content

DNS TTL Calculator

Convert TTL seconds to human-readable format. Look up TTL values for all DNS records of any domain.

TL;DR:

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.

TTL Converter

Enter seconds or use presets to convert TTL to days/hours/minutes

1 hour
Presets:

Common TTL Values

Seconds Duration Use case
601 minuteDNS migration / temporary
3005 minutesFrequently updated records
90015 minutesDynamic IP / load balancing
36001 hourStandard for most records
144004 hoursStable records (MX, NS)
864001 dayVery stable, rarely changed
6048001 weekNS / SOA serial records

Domain DNS TTL Lookup

Enter a domain to see TTL values for all its DNS records

TTL in sec/min/hrTTL conversion and calculation
Propagation TimeWhen DNS changes will take effect
DNS CacheHow long records are cached
RecommendationsOptimal TTL values for different scenarios

Why teams trust us

TTL
instant conversion
48h
max propagation time
300
TTL for migration
Free
no signup

How it works

1

Enter TTL in seconds

2

Convert to h/min/days

3

Calculate propagation window

What is TTL and why does it matter?

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.

TTL Calculator

Convert seconds to readable format and back: 86400 = 1 day.

Propagation Window

Estimate when a DNS record change will be visible to all users worldwide.

Migration Scenarios

TTL recommendations before server migration: when to lower, when to restore.

Common Values

Reference for standard TTLs: 300, 3600, 86400 — which to use for which records.

Who uses this

DevOps

DNS migration planning

Sysadmins

TTL record optimization

DNS admins

cache time calculation

Developers

TTL understanding for APIs

Common Mistakes

Migration with high TTLWith 86400s TTL, some users will see the old IP for a day after the change.
TTL = 0 alwaysZero TTL increases NS server load and slows resolution for users.
Not pre-lowering TTLTTL reduction only takes effect after the current TTL expires. Lower 24–48 hours before migration.
Same TTL for everythingMX and NS are better with high TTL (86400), A records with moderate (3600).

Best Practices

Lower TTL to 300 48 hours before migrationThis ensures fast switching after the IP change.
Use 3600 for A recordsOne hour is a balance between propagation speed and server load.
86400 for stable NS/MXName servers change rarely — high TTL reduces load.
Restore TTL after migrationReturn to standard TTL after successful migration.

Monitor DNS records automatically

DNS monitor notifies you when A, MX, or TXT records change.

Sign up free

What is DNS TTL and How Does Caching Work?

TTL (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.

Save & track URLs you check Free account · 24/7 checks · alerts via Telegram, email, Slack — sign up to monitor any URL you test here.
Free Sign Up

Learn more

Frequently Asked Questions

What is TTL?

TTL (Time To Live) is how long a DNS record stays cached. Determines how long resolvers keep the record without re-querying.

What TTL should I set?

300 sec (5 min) for frequently changing records. 3600 (1 hour) for stable ones. 86400 (1 day) for rarely changing MX/NS.

Related guides

Longer-form reading on this topic from the knowledge base.

Automate this check

Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.