Domain alerts where your team already works
Every Domainyze alert can post to Slack, Discord or your own endpoint, as well as email.
- Slack messages and Discord embeds
- HMAC-SHA256 signed JSON webhooks
- A per-destination filter on alert types
Domainyze delivers alerts over four channels. Email goes to your account address on every plan. The other three are integrations you add yourself: a Slack Incoming Webhook, a Discord channel webhook, or a generic HTTPS webhook that receives signed JSON. Each destination you add gets its own list of alert types, so one event can reach the people who need it and skip everyone else. There is no public API or Zapier app; the webhook is the integration point for your own systems.
Slack
Alerts post into a Slack channel as Block Kit messages: the alert as a header, its facts as fields, and a button to the domain.
See this integrationDiscord
Alerts arrive in a Discord channel as embeds coloured by severity, titled with the alert and linked to the domain.
See this integrationWebhooks
Every alert as a signed JSON POST to your own HTTPS endpoint, with a stable event name and a documented payload per type.
See this integrationIntegrations deliver what the monitoring finds. See how alerts are routed and deduplicated, everything Domainyze monitors, or 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
What the three integrations have in common.
Which integrations does Domainyze support?
Slack, Discord and generic HTTPS webhooks, alongside email. There is no public API and no Zapier app today. A webhook can feed any system that accepts an HTTP POST, including automation tools that expose a catch-hook URL.
Are the integrations included on the free plan?
No. Email alerts are free on every plan; Slack, Discord and webhook delivery are part of the paid plans. Each integration page names the plans that include it.
Can I send different alerts to different places?
Yes. Every destination carries its own alert-type filter. You can send DNS and nameserver changes to an engineering Slack channel, renewals to email, and everything to a webhook that writes to your own database.
Will one event arrive more than once?
No. An alert is claimed once per event before any channel delivers it, so a repeated check cannot send it again. A failed delivery is retried, which is the only way the same alert reaches one destination twice, and each attempt is recorded in the delivery log.
How do I know a destination works?
Every destination has a Send test button. It sends a sample alert down the real delivery path, and the result appears in that destination's delivery log.