When you are waiting for a registered name to become available, the question that matters is not "has it dropped yet" but "when will it". Domainyze answers that automatically. Once a watched name starts expiring, it projects a drop forecast: the point at which the name is likely to be released back to the public pool.
Where the forecast comes from
Every top-level domain runs its expiry, redemption and pending-delete periods on its own timing. Domainyze holds a profile of those durations for the TLDs it can characterise. It combines that profile with the registry's own published expiry date and the lifecycle stage the name is in, and from those it projects the likely drop time.
Two things keep that projection honest. It is never later than the moment Domainyze first saw the name in its current stage, because a name cannot have entered a stage after it was observed sitting in one. And it is never earlier than the length of that stage ago, because the name is still in it. A registry that releases a name sooner than its published grace period allows, which is common, narrows the estimate rather than being ignored.
When Domainyze watches a name move into its final stage itself, that observation replaces the projection entirely and the forecast is labelled Observed. Finding a name already in that stage is not the same thing, and is not labelled as though it were.
The forecast only ever narrows. As the name moves closer to release and Domainyze observes more of its lifecycle, the estimate tightens toward the real moment. It never widens back out to a vaguer guess once it has been pinned down.
Coarse runway or projected date
What you see depends on your plan.
- Free plans see a coarse runway: a plain-language sentence like "May drop in about 5 days". It is enough to know roughly when to pay attention.
- Paid plans see the projected date: "May drop 3 June", once Domainyze has directly observed the name reach its final stage.
Both are the same underlying forecast, shown at the precision your plan entitles.
Why there is no clock time
Domainyze deliberately does not tell you a drop will happen at, say, "13:00 to 20:00 UTC", even though it holds the registry's published window for the TLDs it can characterise.
The reason is that the instant underneath such a range is arithmetic, not an observation. It is the moment the name entered its final stage plus a duration taken from a table of typical TLD timings. That is a sound way to project a day. It is not a measurement of when the registry actually ran its batch, and no amount of caveating changes what a reader takes from a number: quote 13:00 and you have anchored someone to a precision nobody has.
So the hour range is gone rather than disclaimed, and every forecast is phrased as "may drop" rather than "drops". What you are buying on a paid plan is not a more confident-looking sentence. It is the projected date, plus the two things that actually put you in the right place at the right moment: the drop-imminent alerts and the burst checks that fire as the moment arrives.
The confidence label
Alongside the forecast, Domainyze shows how sure it is:
- Observed: Domainyze has directly witnessed the name enter its pending-delete stage on a TLD whose drop timing it knows. This is the strongest signal, and it is the one that unlocks the drop-imminent alerts and the burst checks on paid plans.
- Estimated: the forecast is derived from the TLD's typical lifecycle timing and the stage the name is in, but the final drop has not yet been directly observed.
- Rough: Domainyze does not yet have enough of the name's lifecycle, or enough profile detail for its TLD, to be precise. Treat it as a ballpark.
A forecast that is merely estimated is never dressed up as observed. The label tells you exactly how much weight to put on the time you are seeing.
What to do with it
For a name you are serious about, the forecast tells you when to be ready. On a paid plan, you do not have to keep checking the forecast yourself: Domainyze will send you a drop-imminent alert as the window approaches and tighten its own checks to catch the release.