The Right Alert, To The Right Team, Once
Domain alerts are sent by email, Slack, Discord or signed webhook, and each destination picks the events it receives.
- Email, Slack, Discord and signed webhooks
- An event filter on every destination
- One event is one alert, never a repeat
End Alert Fatigue Across Your Organization
Not every domain event has the same urgency. A renewal due in 60 days is an administrative task; a nameserver change nobody planned is a security incident.
Each destination you add has its own list of event types, so the same event can reach the people who need it and skip the ones who do not.
- Finance and founders: renewal and certificate reminders, collected into daily digests.
- DevOps and security: DNS, delegation and registration changes in a dedicated Slack channel.
- Your own systems: every event as signed JSON, to a webhook your incident tooling already reads.
Integrations for Every Workflow
Email is on every plan. Slack, Discord and webhooks are on Pro and Business, and you can send each one a sample alert to prove it works.
Every alert goes to your account address by default, on every plan. Reminders arrive as one daily digest instead of an email per domain, and a weekly summary covers the rest.
Slack
Paste an incoming-webhook URL and alerts post straight into that channel, so the on-call engineer sees a DNS or status change where they already work.
Webhooks
A structured JSON payload for each event, signed with HMAC-SHA256, for scripts, internal dashboards or an incident platform.
Discord
Point a Discord webhook at a private server channel and alerts arrive as formatted messages your team can discuss in place.
Setup, message format and payloads for each: Slack, Discord and webhooks.
Fewer Alerts, Each One Worth Reading
An alert channel people mute is worse than none. These are the rules that keep it quiet until something actually happened.
One Event, One Alert
Every alert is tied to the transition that caused it. The same event can never be sent twice, however many checks see it, while a genuinely new episode of it is never silenced.
Event Filters per Destination
Choose which event types each destination receives. Send DNS changes to engineering, renewals to finance, and availability alerts only to the person who registers names.
Daily Reminder Digests
Renewal reminders due on the same day are combined into one daily message with one line per domain, and certificate reminders into another, instead of one email each.
A Severity Floor for DNS
Each domain can set the lowest DNS severity worth an alert, so a TXT record tweak stays in the change log while a delegation change still reaches you. See DNS change detection.
Retries and a Delivery Log
A failed delivery is retried with backoff and recorded against its destination. A destination that keeps failing is disabled and you are told, rather than alerts vanishing into a dead endpoint.
Signed Webhooks
Every webhook carries an HMAC-SHA256 signature in the X-Webhook-Signature header, and you can rotate the signing secret at any time.
What Every Plan Gets, and What Paid Adds
Every alert you are entitled to is delivered on every plan. What paid adds is where it can go.
Every alert, by email
- Availability and lifecycle-stage alerts to your account email.
- The same one-event-one-alert rule as every plan.
- A weekly summary of what changed across your domains.
Delivered where your team works
- Slack, Discord and signed webhook destinations, as many as you need.
- An event filter on each destination.
- Renewal and certificate reminder digests for your portfolio.
- DNS change alerts with a per-domain severity floor.
Developer-Ready Webhooks
A webhook turns a domain event into something your own systems can act on.
Each payload is structured JSON that names the domain, the event and what changed, so it can be forwarded into an incident platform such as PagerDuty, Datadog or Opsgenie through their own webhook intake. When a core domain changes registrar or nameservers, or its certificate stops being valid, your existing response workflow can take over.
See which status changes are alerted"event": "domain.status_escalation",
"domain": "production-app.io",
"timestamp": "2023-11-24T14:30:00Z",
"data": {
"previous_status": "ok",
"new_status": "clientHold",
"days_to_expiry": -1
},
"tags": ["core-infrastructure", "critical"]
}
Who Routes Their Alerts
The same event matters to different people. Each of these links to the page for a team that splits its alerts by who has to act.
Digital Agencies
Send renewal reminders to billing and DNS changes to the developers, with each destination filtered to the alert types it should see.
Domain monitoring for agencies Use CaseIT Teams & MSPs
Point a signed webhook at your ticketing system so a domain event opens a ticket instead of waiting in someone’s inbox.
Domain monitoring for IT teams and MSPs Use CaseEnterprise Portfolios
Give security, legal and each brand team their own channel, so every alert lands with the team that owns the domain.
Domain monitoring for enterprise portfoliosDomainyze vs. the alternatives
How routed domain alerts compare to registrar emails and a generic uptime monitor.
| Capability | Domainyze Domainyze | Manual checks | Generic uptime monitors |
|---|---|---|---|
| Where alerts go | Email on free; Slack, Discord and webhooks on paid | The registrar account email | Many channels, but only for downtime |
| Repeat alerts | One alert per event, by design | A reminder per domain per notice | Repeats while the check fails |
| Filtering | Event types chosen per destination | None | Per monitor |
| Renewal reminders | One daily digest across registrars | One per registrar, per domain | No |
| Failed delivery | Retried, logged, and you are told | Lost in spam | Varies |
| Payload verification | HMAC-SHA256 signature | n/a | Varies |
A registrar only emails about the domains it holds, so a portfolio spread across three registrars means three inboxes and three reminder schedules. Domainyze reads every domain from its registry and routes the result from one place.
This is one capability of Domain monitoring, the lane it runs in. That page covers everything else the lane watches and what each plan includes.
Start Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 5 domains are free.
No credit card required • Cancel anytime
Frequently Asked Questions
Channels, filters, and how duplicate alerts are prevented.
How do I get domain alerts in Slack?
On a Pro or Business plan, create an incoming webhook in your Slack workspace, then add it as a Slack destination in Domainyze. Send it a sample alert to confirm the URL works. Choose which event types it receives, and alerts post into that channel as they happen.
Which notification channels are available?
Email on every plan, plus Slack, Discord and signed JSON webhooks on Pro and Business. Email goes to your account address. The paid channels are destinations you add, each with its own event filter, so one account can feed several channels at once. The events themselves are covered on domain registration alerts.
Can I choose which events each channel receives?
Yes. Each destination has a list of event types, such as availability, lifecycle stage, status change, registration change, DNS change and certificate problems. A destination with no filter receives everything. DNS alerts also respect a per-domain severity floor, so minor record changes can stay out of every channel.
Will I get the same alert more than once?
No. Each alert is tied to the specific transition that caused it and recorded once, so repeated checks that see the same state send nothing new. If the same thing happens again later, such as a domain dropping a second time, that is a new event and you are alerted again.
Do you support webhooks?
Yes, on Pro and Business. Each event is sent as structured JSON and signed with HMAC-SHA256 in the X-Webhook-Signature header, so your endpoint can verify it came from Domainyze. You can rotate the signing secret at any time, and every delivery attempt is logged against the destination.
What happens if a delivery fails?
It is retried with increasing delays and each attempt is written to the destination’s delivery log. A destination that keeps failing is disabled automatically and you are notified by email, so alerts are never silently sent to an endpoint that no longer works.
How are renewal reminders delivered?
As a daily digest. Renewal reminders due on the same day are combined into one message with one line per domain, and certificate reminders into a second one, instead of a separate email for each. Reminders cover the domains in your portfolio, which is a paid feature. See domain expiry monitoring for the reminder schedule.
Is there a limit on how many alerts I receive?
No. Alerts are not metered or charged per message. How many you receive depends on how many real events happen across the domains you monitor, and the one-event-one-alert rule keeps that number close to the number of things that actually changed.