DNS Propagation Time Calculator
Estimate how long DNS changes may take to fully reach users worldwide.
Use this to estimate the total wait time after changing DNS records. It gives a realistic number based on TTL, cache refresh, and registrar propagation.
Your details
Look at the record’s TTL in your DNS panel.
Typical extra time some resolvers may keep the old answer.
Result
Conservative estimate in hours.
- TTL component (hours)How long caches may legally hold the old record.
- 1
- Extra propagation window (hours)Resolver cache plus change-type delay.
- 2.5
About this tool
How DNS propagation time is estimatedLearn what DNS propagation time really means, how to estimate it from TTL and cache windows, and what the calculator can’t know.
Free download
DNS Change Timing SheetFill this in before publishing a DNS change so you know when old caches should be gone.
Free, no email required — print it or save it as a PDF.
Share it
DNS Propagation Time Calculator infographicThe key numbers as one image — free to save, share, or embed on your own site with credit.
How this is calculated
DNS changes do not update everywhere at once. The main number here is a conservative estimate of how long users may keep seeing the old record after you publish a change. The maths uses your current TTL plus a short propagation window for recursive resolvers and registrar/authoritative updates. The 2-hour record-update and 24-hour nameserver-change constants are planning buffers chosen for this calculator rather than measured figures. TTL is the standard checkable constant that controls how long caches may hold old data. This tool assumes a normal public DNS change on an existing zone. It does not model DNSSEC issues, nameserver outages, or manual registrar delays beyond the basic propagation window.
Common questions
- How long does DNS propagation usually take?
- For a simple record change, often a few hours; for nameserver changes, it can take up to 24-48 hours or more depending on caches.
- Can I speed it up?
- You can lower TTL before the change, but existing caches may still honor the old TTL until they refresh.
- Why do some people see the new record sooner?
- Different resolvers refresh at different times, so users can switch over gradually instead of all at once.
Take it further with AI
Copy this into ChatGPT or Claude with your own numbers filled in. It hands over the figures this calculator worked out, so the answer is built on real arithmetic instead of a guess.
I used the DNS Propagation Time Calculator at https://www.bfcbrilliance.com/tools/dns-propagation-time-calculator.
What I entered:
- Current TTL (hours): ___
- Change type: ___
- Resolver cache window (hours): ___
What it calculated:
- Estimated full propagation time: ___
- TTL component (hours): ___
- Extra propagation window (hours): ___
Use those figures as given — they are already worked out, so please don't recalculate or estimate your own. Help me turn them into a plan: what to buy or do, in what order, roughly what it should cost, and the mistakes people most often make with this job.Last updated
Get the next tool.
New tools and guides straight to your inbox. No spam, ever.