Consider a proposed page during an e-commerce mail-provider cutover: the sending domain's published records and the mail service's domain status disagree. The on-call sees both observations, their timestamps, and the intended provider. That is a useful page; “domain missing” without lifecycle context is a much weaker one. This is a design example, not a reported incident.
Short answer: read sending-domain status and published DNS records on a schedule, emit both as metrics, and alert when they disagree for an active domain. A daily check fits stable configuration. During an MX cutover, choose a separate observation interval and propagation allowance that match the change window; a daily check cannot support a minutes-long decision.
How should records and mail status expose sending domain health before cutover?
Start with the desired state.…