Domain Health · Alerts

Why did I get this alert?

You (or someone on your team) asked us to monitor a domain. We send an alert only when something changed or broke, and only after a second check confirmed it.

How we avoid false alarms

DNS answers can flicker during changes or provider hiccups. So when a check sees a difference from the last confirmed state, we don't alert yet. We check again at least 10 minutes later. Only if the second check sees the same new state do we alert you, and that state becomes the new baseline.

Alert types

DNS change confirmed

An SPF, DKIM, DMARC or MX record is different from before. The alert shows the old and new values. If you or a colleague made the change, no action is needed. If nobody did, check your DNS host's audit log and account access, since unexpected DNS changes can mean a compromised account or a tool that edited records on its own.

SPF now fails validation

Your record didn't change, but something it relies on did, for example a provider changed its include and pushed you over the 10-lookup limit. Run the SPF checker for the specific fix.

HTTPS stopped working

A trusted HTTPS connection couldn't be made twice in a row. Check the SSL checker for the cause.

Certificate or domain expires in N days

Sent at 30, 14, 7, 3 and 1 days. Each threshold is sent once. Renew, and the warnings stop once the new date shows up.

Managing alerts

Add or remove email addresses, Slack channels and webhooks on your account page. To stop all alerts for a domain, remove it from monitoring. Questions? Contact support.