How often a domain is checked is not one number. It depends on how urgent the domain's current state is, how close it is to dropping, and which plan you are on. This page is the reference for all three; other articles link here rather than restating the figures.
The cadence at rest
While nothing urgent is happening, checks run on a steady interval:
| Domain state | Free | Pro | Business |
|---|---|---|---|
| Active, well before expiry | every 12 hours | every 6 hours | every 6 hours |
| Expiring, or otherwise worth watching | every 12 hours | every 3 hours | every 3 hours |
| In a critical state, such as pending delete | every 6 hours | every hour | every hour |
| Confirmed available | every 24 hours | every 12 hours | every 12 hours |
A confirmed-available name is checked less often on purpose: the news has already been delivered, and what remains is noticing if somebody registers it.
The cadence in the drop window
The real work happens in the final approach. Once Domainyze has directly observed a name enter pending delete, paid plans tighten the interval sharply as the projected drop gets closer:
| Time until the projected drop | Free | Pro | Business |
|---|---|---|---|
| Within 6 days | every 6 hours | every hour | every hour |
| Within 24 hours | every 6 hours | every 15 minutes | every 10 minutes |
| Within 2 hours | every 6 hours | every 2 minutes | every minute |
Three things about this table are worth stating plainly:
- The free plan does not tighten. Six hours is its floor in every row. A free plan will usually learn about a drop, but not in time to win a contested name.
- Tightening requires an observation, not an estimate. Domainyze only enters this cadence for a name it watched arrive in pending delete. If the stage was inferred rather than witnessed, the forecast is marked lower confidence and the checks stay at the widest interval. Spending a minute-by-minute check budget on a guessed date is how you miss the drops you did guess right.
- Bursting checks run on their own queue. A cohort of names all dropping in the same hour cannot starve ordinary monitoring, because the burst lane has its own per-tick budget.
Why there is no exact drop time
The registry decides when its deletion batch runs, and it does not publish the second. Domainyze projects the day and tightens the cadence around it rather than claiming an hour it cannot observe. See How drop forecasting works.
Related
- Drop-imminent alerts and burst cadence — the alerts that fire ahead of a projected drop.
- What is domain availability monitoring? — how a check decides a name is free.
- Understanding plans and limits — everything else the plans differ on.