Help center
Alerts and notifications
The alert feed, every notification switch and what reads it, push and quiet hours, email alerts, provider status monitoring and custom endpoint checks.
Updated · 5 articles
An alert in DomainGuard is a record: what happened, on which domain, when, how it was delivered, and what to do next. The feed is the same on the web and in the app. Delivery is push to the iOS app on every plan, and email on paid plans.
Articles
- The alerts feed - Open and Done, swipe actions, Mute 7 d, the badge, alert detail, and the History ledger.
- Notification settings - every switch, its default, which plan it needs, and what actually reads it.
- Push notifications and quiet hours - the four server-side senders, local notifications, time-sensitive delivery, and the quiet window.
- Provider status monitoring - live status of the DNS host, mail provider, registrar and other vendors your domains use.
- Custom endpoint checks - saved URL checks with their own history, and the one-off probe.
Where
- Web: Dashboard, Monitor; Settings, Alerts for the switches.
- iOS: the Alerts tab (badge = open count); Account, Notifications for the switches.
- API/MCP:
GET /api/notifications,GET /api/notifications/activity,POST /api/notifications/read; toolslist_alerts,get_alert_activity,mark_alerts_read,get_account_settings,update_account_settings.
Three facts to keep straight
- The feed is the record; push and email are copies. An alert is in the feed whether or not the push or the email was delivered, and the alert's detail shows every delivery attempt.
- Push is on every plan; email is Starter and up. A Free account gets every alert on the phone and nothing by email, which is why the setup guide's "Alerts reach you" step is satisfied by a registered device on Free.
- Time-sensitive means it breaks through. High-severity findings and your own site being down are delivered as time-sensitive notifications; they ignore quiet hours and Focus modes that allow time-sensitive alerts. Everything else waits.
What is an alert and what is not
An alert is an event the account was told about: a finding raised, a change detected, a site down or recovered, a provider incident, a breach hit, a DMARC sender, a KEV match, a scan finished. A finding on a domain page is not an alert until it is raised; a change event is both a card in the feed and an entry in the domain's history. The account History ledger under the Alerts tab merges all of it, plus scans, credit spends and sign-ins, into one timeline.
Common questions
Can I get alerts by SMS or Slack? Not today. Push to the app and email are the two channels; the alert feed is readable over the API and MCP if you want to route it yourself.
Why did I get one push and not ten when a domain had ten findings? Findings are grouped per domain per scan, and change events are deduplicated for 30 days. One event, one alert.
In reading order
Articles in Alerts
- The alerts feedHow alerts are listed, what Open and Done mean, swipe to Done or Mute 7 d, the alert detail page, and the account History ledger.Updated
- Notification settingsEvery alert switch, its default, the plan it needs, and what reads it. Push goes to the app on every plan; email needs Starter or higher.Updated
- Push notifications and quiet hoursThe four server-side push senders, the local notifications the app raises itself, time-sensitive delivery, threads per domain, and the quiet-hours window.Updated
- Provider status monitoringLive status for the DNS host, mail provider, registrar and other vendors your domains depend on, from a catalogue of over 900 status pages.Updated
- Custom endpoint checksSaved URL checks that poll a specific page or API on a schedule with their own run history, plus the one-off probe. Limits: 30 checks, 60 probe runs an hour.Updated
Still stuck?
Ask the people who run the scanner.
Send the domain and what you expected to see. We look at the same scan you are looking at and write back with what it means and what to change.