Domainyze has no "send me alerts every N hours" setting, and that is deliberate. Alerts are driven by events, not by a timer: you hear from us when something actually changed, once per change. This page explains what governs the timing, and lists every control you have over how much you receive.
Two different things people mean by "frequency"
How often we check decides how quickly you learn about a change. It is set automatically.
How often we alert decides how much mail you get. That is what you control.
How often we check
Check frequency is calculated per domain from two inputs, and is not a setting you edit directly.
The domain's urgency. A domain sitting quietly registered for three more years is checked infrequently. A domain in redemption or pending delete, days away from dropping, is checked far more often, because that is where minutes matter. Urgency is recalculated after every check, so a domain accelerates on its own as it moves toward the drop and slows down again after a renewal.
Your plan. Paid plans check every domain more often at every urgency level, and the gap is widest exactly where it counts, on domains about to become available. Every interval, for every state and plan, is in How fast are availability checks?.
When several people monitor the same domain, it is checked at the rate of the best plan among them.
SSL and DNS work differently, for portfolio domains on paid plans. SSL runs as a daily sweep, since a certificate does not change often enough to justify more. DNS is checked on a tiered schedule: Business checks the full zone every six hours and Pro daily, and on both plans your nameservers get their own faster lane — hourly on Business, every six hours on Pro — because a nameserver change is the most urgent DNS event to catch.
Why you do not 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; a DNS alert to the individual check that spotted the diff.
Two consequences worth knowing:
- A condition that persists does not re-alert. A domain sitting in
redemption_periodfor 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 domain that drops, is registered by someone else, and drops again alerts you both times. Fix a certificate and let it lapse again and you hear about it again.
There is no cooldown to wait out and no suppression window to configure. If it fires, something new happened.
Turning the volume down
Every control below lives in one of two places: the domain's own page, reached by clicking its name in your Watchlist or Portfolio, or Settings. Per-domain changes save as you make them and take effect on the next monitoring cycle.
1. Choose which stages alert you, per domain
The first control, and the one that decides everything else, is which lifecycle stages are worth hearing about for that particular name.
Open the domain and use the Stage Alerts picker. You will see the stages you can act on: Available, Grace, Redemption, Pending delete, and the watch-ended stages Reclaimed and Taken, among others. Select the ones you want. Stages that need a higher plan are shown but greyed out, so you can see what an upgrade would add.
The defaults. A new Watchlist domain alerts on Available only, so you are told the moment the name becomes registrable and nothing else. A new Portfolio domain also gets expiry reminders and SSL alerts. Change any of it at any time.
Selecting no stages at all is a valid choice and means exactly what it says: no stage alerts for this domain. It is not the same as leaving the setting alone.
2. Choose your expiry reminder windows
Expiry reminders are the most predictable source of alerts, and they are also the most compact: they arrive as one daily digest that lists every domain reaching a reminder window that day, so a portfolio of fifty renewals due together is one email, not fifty. You still choose exactly which windows you get: 90, 30, 7 or 1 day before expiry. New accounts default to 30, 7 and 3 days.
- Account-wide default, applied to newly added domains: Settings → Portfolio → Default Expiry Alert Days.
- Per domain, overriding the default: open the domain and edit its monitoring settings.
If your domains renew automatically, a single 7-day reminder is usually enough, and it still catches the case that matters, which is auto-renew silently failing on an expired card.
3. Filter alert types per destination
This is the most powerful control and the most underused. Every delivery destination has its own alert-type filter, so you route by severity instead of reducing coverage.
A pattern that works well:
- Slack or Discord: availability, status changes, invalid SSL, monitoring auto-paused. Things somebody should look at today.
- Email: expiry reminders, SSL expiry reminders, DNS changes. Things somebody should look at this week.
You keep every alert, but the interruptive channel only carries the interruptive ones. Set this in Settings → Alerts, via Manage on the destination.
4. Filter DNS record types per domain
DNS change alerts are the noisiest type for anyone running active infrastructure, because a deploy that moves an A record is a real DNS change and we will tell you about it.
Per domain, you can exclude the record types you edit routinely. Excluding A and TXT on an actively developed site, while keeping NS, MX, SPF, DKIM and DMARC, removes nearly all of the noise and keeps every record type a hijack would touch.
5. Turn off a check type for a domain
If a domain does not serve a website, its SSL monitoring is only ever going to produce noise. Turn SSL or DNS monitoring off for that domain individually rather than living with alerts you have already decided to ignore.
6. Turn a destination off
Every destination, email included, has an on/off toggle in Settings → Alerts. Turning one off stops delivery to it while monitoring continues normally, so your dashboard, history and other channels are unaffected. See how to pause alerts temporarily.
What we deliberately do not do
We do not batch critical alerts. A domain becoming available is worth nothing an hour later, so it is never held back to be bundled with anything else. Only the non-urgent daily reminders (domain and certificate expiry) are bundled, into the one daily digest described above.
We do not retry an alert you ignored. An unread alert is an answered question as far as we are concerned. Alerting you repeatedly about a condition you have already seen is how people learn to filter a sender to the archive, and after that the important one does not get read either.