DNS & domain lookup

DNS TTL Planner

Convert a DNS TTL to plain-English time and get a safe TTL-lowering schedule before a planned change or migration. Free, runs in your browser.

Plan your TTL

Set a TTL to see it in plain English and get change-timing advice.

1 hour

3600s
TTL
1 hour
Max cache time
Moderate
Propagation
A moderate TTL — a good everyday default that balances speed and DNS load.
Planning a change? Lower this record's TTL to 300 (5 min) at least 1 hour before the change, so old cached values expire first. Make the change, verify it, then raise the TTL back.

What this TTL planner does

Converts any TTL to plain-English time
Rates propagation speed (fast, moderate, slow)
Advises a safe TTL-lowering schedule before changes
Presets for common TTL values
Shows the maximum time a record stays cached
Runs entirely in your browser

Common use cases

  1. 1Preparing a record for a planned migration
  2. 2Choosing a sensible everyday TTL
  3. 3Understanding how long a change will take
  4. 4Timing a nameserver or IP cutover
  5. 5Reducing downtime risk during DNS edits
  6. 6Explaining TTL to a client or teammate

Related tools

DNS Propagation CheckerDNS Record LookupDNS Health CheckerDNS diff toolNameserver migration checkerDNS zone file validator

About DNS TTL

TTL (Time To Live) is how long, in seconds, resolvers may cache a DNS record before checking again. A low TTL means changes propagate quickly but resolvers query more often; a high TTL reduces load but makes changes slow to take effect.

The key trick for safe changes: lower the TTL ahead of time. Because caches hold the old value for up to the current TTL, drop it to 5 minutes at least one old-TTL period before your change, switch the record, then restore a higher TTL once everything is confirmed.

More Free Tools Where This Came From

This utility is one of dozens of free, no-login tools for DNS, email, SEO and developers — all instant and private.

See All ToolsTalk to Our Team

HostCloud.in  ·  Pune, India  ·  Serving 34,987+ Websites Since 2020

FREQUENTLY ASKED QUESTIONS

Got Questions? We Have Answers.

What is a DNS TTL?

TTL (Time To Live) is how long, in seconds, resolvers may cache a DNS record before checking again. It controls how quickly a change takes effect.

What TTL should I use?

An hour (3600s) is a sensible everyday default. Lower it to 5 minutes (300s) before a planned change so old values expire faster.

How do I plan a DNS change safely?

Lower the TTL to 300 at least one current-TTL period before the change, make the change, verify it, then raise the TTL back to a higher value.

Why does a high TTL slow down changes?

Resolvers keep serving the cached old value until the TTL expires, so a one-day TTL can mean up to a day before everyone sees the new record.

Does a lower TTL have downsides?

Yes — resolvers query more often, slightly increasing DNS load and lookup latency. It is a trade-off between agility and efficiency.

Is anything sent to a server?

No. The planner is pure client-side math and runs entirely in your browser.