If your team, your community or your side-project group lives in Discord, that is where domain alerts should land. This guide connects Domainyze to a Discord channel in about five minutes.
You need Manage Webhooks permission on the Discord server, and a paid Domainyze plan.
What a Discord alert looks like
Each alert posts as a single embed:
- The title is the alert's name, and it links to that domain's page in Domainyze.
- The colour is set by severity, so you can triage the channel at a glance without reading a word: blue for informational, amber for medium, orange for high, red for critical. A domain becoming available or a certificate going invalid is red.
- The fields are the facts for that alert type: the domain, the status transition, days until expiry, the specific DNS records added and removed.
A short plain-text line accompanies the embed so the alert is readable in Discord's notification popups and mobile previews.
Step 1: Create a Discord webhook
- In Discord, right-click the channel you want alerts in and choose Edit Channel. (On mobile, tap the channel, then the settings gear.)
- Open Integrations.
- Click Webhooks, then New Webhook.
- Give it a name, for example
Domainyze, and optionally an avatar. This is the name messages will post under. - Confirm the Channel selector points at the right channel.
- Click Copy Webhook URL. It looks like this:
https://discord.com/api/webhooks/000000000000000000/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- Click Save Changes.
Treat this URL as a password. The token in its path is the entire authentication, so anyone holding the URL can post into that channel. Domainyze stores it as a secret and shows it masked after you save it. If it ever leaks, delete the webhook in Discord and create a new one; there is no way to rotate the token in place.
Posting to more than one channel
A Discord webhook is bound to one channel. Create a second webhook in the second channel and add both to Domainyze as separate destinations, each with its own alert-type filter. That gives you a busy #domain-log channel and a quiet #alerts channel that only fires for things that need a human.
Step 2: Add the webhook to Domainyze
- In Domainyze, open Settings, then the Alerts tab.
- Under "Add a channel", choose Discord.
- Paste the webhook URL into the Discord Webhook URL field.
- Add a description such as
#alerts on the team server. The URL is masked once saved, and every Discord webhook URL looks alike. - Choose your alert types, or leave it on all types.
- Save.
Domainyze validates that the URL starts with https://discord.com/api/webhooks/, so a Slack URL or a generic endpoint pasted here fails as a form error rather than as a stream of failed deliveries.
Note on
discordapp.com: older webhook URLs used thediscord.comdomain's former name. Use the currenthttps://discord.com/api/webhooks/...form. If Discord gave you a legacy URL, replacing the hostname withdiscord.comand leaving the rest of the path untouched works.
Step 3: Send a test message
Open the destination's Manage panel and press Send test. A real alert is delivered through the real path and the outcome is written to the delivery log.
If the embed shows up in Discord, you are finished.
Choosing which alerts go to Discord
Discord channels scroll fast, and an alert that scrolls past unread did not do its job. Use the alert-type filter rather than sending everything:
- Good fit for Discord: domain became available, domain status changed, SSL certificate invalid, monitoring auto-paused. Short, urgent, and colour-coded so the channel is scannable.
- Better left on email: long-horizon expiry reminders and routine DNS diffs, which are reference material rather than interruptions.
If you run a domain-investing community, one useful pattern is a dedicated Discord destination filtered to availability alerts only, pointed at a channel the group watches during drop windows.
Troubleshooting
Nothing arrives, and the delivery log shows 404 with Unknown Webhook.
The webhook was deleted in Discord, or the channel it pointed at was deleted. Create a new webhook and update the destination.
The delivery log shows 401.
The token part of the URL is wrong or truncated. Re-copy the full URL with Discord's Copy Webhook URL button rather than selecting it by hand.
The delivery log shows 429.
Discord is rate-limiting. Domainyze throttles Discord destinations to roughly one message per second and honours the retry_after value Discord returns, so bursts drain on their own. Persistent 429s usually mean many alerts fired in one sweep.
Messages arrive with no fields, or an embed looks empty. Discord rejects embeds containing an empty field value, so Domainyze substitutes a dash for any fact that is genuinely absent, for example a domain with no known expiry date. A dash means "we do not have this value", not "the delivery is broken".
The destination shows as disabled. Twenty consecutive failures disable a destination automatically. Fix the webhook, then re-enable it from the Alerts tab.