On this page
Incidents & alerts
Notification channels
Choose how you want to be told when something goes wrong.
Overview
When DomainDash confirms a problem with one of your sites, it reaches you the way you actually want to hear it. Depending on your plan, that can be email, SMS, Slack, a webhook, or any combination, so the news lands where you'll see it, not buried in an inbox you're not watching. Email is available on every plan, including Free. Slack is available on Starter plans and above. SMS and webhooks are available on Pro and Business.
For setting up Slack, see Slack integration. For SMS, see SMS notifications. The rest of this page covers how each notification works and what to expect.
| Channel | Available on | What it's for |
|---|---|---|
| All plans | Every notification, with per-member category control | |
| Slack | Starter, Pro, Business | Incidents, billing, and team activity routed to channels |
| SMS | Pro, Business | Incident alerts and their recovery, per member with plan SMS seats |
| Webhooks | Pro, Business | Signed JSON sent to your own endpoints |
DomainDash sends four kinds of notification:
| Notification | When it's sent | Channels |
|---|---|---|
| Urgent alert | A P0 (Urgent) incident is confirmed: your site is Down, or a page failed its content check | Email (all plans), SMS (Pro and Business), Slack (Starter and above), webhooks for site-down incidents (Pro and Business) |
| Ongoing updates | Periodically during an active P0 incident, so your team knows DomainDash is still tracking the problem | |
| Daily digest | Every morning, if you have open non-urgent incidents | |
| Resolved | A P0 incident has been resolved and your site is back to normal | Email, SMS (Pro and Business), Slack (Starter and above), webhooks (Pro and Business) |
Urgent alerts go to every member of your team who hasn't opted out, so nobody misses a P0 incident — there's no single point of failure waiting to be on holiday. The daily digest gathers lower-severity problems into one email, so you stay informed without your phone buzzing all day over things that can wait.
Setting up email notifications
Email notifications work out of the box. As soon as you create an account and add a site, alerts land at the email address you signed up with: no setup, nothing extra to switch on. You're covered from your very first site.
- Verify your email address
Make sure you've verified your email address during sign-up. DomainDash can't send notifications to an unverified address.
- Choose your categories
You pick your own categories on the Your notifications page (avatar → Profile → Your notifications): choose which categories you receive (Incidents, Billing, and Team activity) within the categories a team owner or admin has switched on for the team. The email panel on Settings → Notifications is the team-wide matrix that owners and admins use to set each member's ceiling, not where an ordinary member self-selects.
- Check your spam folder
If you're not receiving notifications, check your spam or junk folder. Adding
inbox@domaindash.ioto your contacts can help ensure delivery.
The other channels
- Slack posts rich messages into the channels you choose, with per-category routing. See Slack integration.
- SMS texts the urgent stuff to members who've verified their own mobile number. SMS is per-user, and the team has a set number of SMS seats from its plan. See SMS notifications.
- Webhooks send a signed JSON payload to an endpoint you control, so you can wire incidents into your own tools. Available on Pro and Business.
How each notification works
Urgent alerts
When a P0 (Urgent) incident is confirmed, DomainDash sends an urgent alert to every member of your team who hasn't opted out, within about a minute, often before your visitors notice a thing. The email tells you exactly what's wrong, which site is affected, and links straight to your dashboard. If your plan includes SMS, members with a verified number and a seat get a text too, and for site-down incidents any configured webhooks fire. (Content-check failures reach you by email, SMS, and Slack, but don't currently fire a webhook.)
If multiple P0 incidents are confirmed around the same time, DomainDash batches them into a single notification rather than sending one per incident. This keeps things manageable if several sites go Down at once.
Ongoing updates
During an active P0 incident, DomainDash sends periodic email updates to your team so you know the problem is still being tracked. These start arriving shortly after the incident is confirmed and become less frequent over time: more often at first when you're likely actively investigating, then spacing out as the incident continues.
Each update includes how long the incident has lasted and how many checks have failed. They stop automatically when the incident is resolved.
Daily digest
Every morning (based on the team owner's timezone), DomainDash checks whether you have any open non-urgent incidents. If you do, it sends a summary email listing each incident, grouped by severity:
- Needs fixing: SSL certificate expired or invalid, DNS failing, domain name expired
- Needs a look: site responding slowly
- Worth knowing: SSL certificate or domain name expiring soon
Each item shows how long the incident has been open, so you can prioritise accordingly.
Resolved notifications
When a P0 incident is resolved, for example your site comes back up or a page starts passing its content check again, DomainDash sends a follow-up to let your team know. It tells you which site recovered, what the problem was, and how long it lasted.
Who gets notified?
Notifications are sent to the members of the team that owns the affected site. If you're part of multiple teams, you'll only receive notifications for sites belonging to the teams you're a member of.
Each member controls which email categories they receive, and SMS is opt-in per member. A team owner or admin sets the team-wide ceiling (for example, switching a whole category off for everyone) and each member chooses within that. So an urgent P0 alert reaches everyone by default, but a member who's turned off the Incidents category, or who hasn't set up SMS, won't get it on that channel.
Managing your notification settings
Your own preferences live on Your notifications (avatar → Profile → Your notifications); the team-wide configuration lives on Settings → Notifications (owners and admins only); and Slack has its own home on Settings → Integrations. Across these pages you can:
- On Your notifications: choose your own email categories, and opt yourself in or out of SMS (once an owner or admin has given you a seat)
- On Settings → Notifications: owners and admins set the team-wide email matrix (each member's category ceiling) and assign SMS seats
- On Integrations: connect Slack and route each category (Incidents, Billing, Team activity) to a specific channel
- Verify or change your own mobile number (on your profile)
Team owners and admins manage the team-wide configuration: connecting Slack, assigning SMS seats, and the category ceilings. Everyone else manages their own preferences within those limits on Your notifications.
Related
- SMS notifications for a step-by-step SMS setup guide
- Slack integration to post alerts into your team's Slack channels
- How incidents work for how DomainDash detects and confirms problems
- Site settings to customise how DomainDash checks each site
Start checking your sites for free
DomainDash keeps an eye on your uptime, SSL, DNS, and domain registration so you don't have to — and tells you the moment something needs your attention. Set up in under a minute, no credit card.
Last updated: 19 June 2026