A drop forecast tells you roughly when a watched name will be released. A drop-imminent alert turns that into action: it reaches out to you as the window arrives, so you do not have to keep watching the forecast yourself. This is a paid feature.
The lead times
When Domainyze has directly observed a watched name enter its final pending-delete stage, it schedules a warning at each of your plan's lead times before the projected drop:
- Pro: 1 day ahead, and 1 hour ahead.
- Business: 1 day ahead, 1 hour ahead, and a final 10 minutes ahead.
Each lead time fires once per drop. If the same name is registered again later and eventually drops a second time, that is a new cycle and the alerts arm themselves again.
A drop-imminent alert can go to any channel you have configured: email, webhook, Slack or Discord. Its webhook event is watchlist.drop_imminent, so you can route on it in code.
Burst cadence: catching the actual release
Knowing a drop is coming is only half the job. In the final approach to an observed drop, Domainyze also tightens how often it checks the name, from its normal routine cadence down to sub-two-minute bursts. This is what lets it catch the release close to the moment it happens rather than noticing it on the next scheduled sweep.
Those burst checks run on a dedicated fast lane with their own budget, so a cluster of names dropping at the same time cannot crowd out the rest of your monitoring.
Why paid only, and why observation matters
Both the drop-imminent alerts and the burst cadence require a directly observed drop, not merely an estimated one. Anchoring on a real observation is what keeps the alerts honest: you are warned about a release Domainyze has actually seen coming, at a time it is confident in, rather than being pinged every time an estimate shifts.
Free plans see the coarse runway and are told after the fact if a name they were watching was taken (see the missed-drop surface), but they do not burst and do not receive imminent alerts.