Domainyze sends alerts on events, not on a timer. There is no "notify me every N hours" setting, because there is nothing to send on a schedule: you hear from us when something actually changed.
Alerts are immediate
When a monitored domain changes in a way you have asked about, the alert is dispatched as soon as the check that spotted it completes. How quickly that happens depends on how often the domain is being checked, which adapts to how urgent its state is and tightens sharply as a drop approaches. See How fast are availability checks?.
You never get the same alert twice
Every alert is recorded against the specific occurrence that caused it, not against the domain. A status change is tied to the moment the status moved; an expiry reminder to that reminder window on that expiry date.
This gives two behaviours worth knowing:
- A condition that persists does not re-alert. A domain sitting in redemption for weeks alerts you once, when it enters. It does not remind you daily that it is still there.
- A condition that genuinely recurs does alert again. Renew a domain and next year's reminders fire normally. A name that drops, is registered, and drops again alerts you both times.
There is no cooldown to wait out and no suppression window to configure. If an alert fires, something new happened.
Several changes at once
A domain can move through more than one state between checks — grace to redemption, for instance. Each genuine change is its own alert, but a repeated observation of the same state is not, so a busy domain produces one alert per real event rather than one per check.
Getting less mail
If the volume is more than you want, the answer is which events you subscribe to and where they are delivered, not a frequency dial. Every control is listed in How to customize alert frequency, and How to pause alerts temporarily covers stopping delivery without losing monitoring.