MX monitoring: watch inbound hosts before mail goes dark
MX monitoring is how you notice the inbound postal address drifted—deleted after a zone rebuild, swapped to a retired host, or never restored after a migration—before clients say “email bounced.” CrowWake’s check is a public MX resolve with priorities and hosts, not a live SMTP delivery test.
What MX monitoring means here
Operators searching for MX monitoring usually want an early rooster: are the mail exchangers still published, and do priorities still point at the real provider? CrowWake answers with live MX lookups, lists priority + host pairs, and flags zero MX as fail. It sits beside SPF, DKIM, and DMARC so “inbound went empty” shows up in the same flock as “the guest list broke.”
What CrowWake checks
We resolve MX for your domain and summarize priorities plus hosts. Healthy exchangers found → ok. Zero MX → fail (unless you intentionally receive no mail—CrowWake still flags empty so a silent wipe is visible). The free MX checker uses the same public lookup with no login—the same signal the hourly probe uses. CrowWake does not open an SMTP session or prove mailbox delivery in v1.
Monitoring vs “what is an MX record”
The MX guide explains postal routing, priorities, and provider hostnames in plain English. Monitoring is the repeat job: catch a deleted MX after a panel cleanup, leftover hosts from a retired ESP, or a migration that never put Google/Microsoft back. Both use the same free MX checker; CrowWake just repeats the pulse every hour. Pair with SPF/DKIM/DMARC monitoring so send and receive stay inventoriable together.
What “good enough” looks like
MX pointing at your real inbound provider. Priorities make sense (primary lower preference number, backups higher). No leftover MX from a host you retired. If the domain is send-only, decide consciously (null MX is a choice)—CrowWake still crows on empty so accidental wipes do not hide.
Quick triage when MX goes yellow or red
1) Re-run the free MX checker and read the live priority/host list (or “none”). 2) If missing, copy MX hostnames and priorities from your provider’s setup guide, publish them, then re-check. 3) If hosts look wrong, remove retired exchangers and keep only the current provider set. 4) Confirm MTA-STS mx: lines still match if you publish STS. 5) Add the domain so CrowWake crows on the next drift instead of waiting for a bounce ticket.
If CrowWake crows
Treat the failing check as source of truth: empty MX vs wrong leftover hosts are different jobs. Use the MX how-to for provider-shaped records, re-run the free MX checker, then keep watching. CrowWake monitors public MX DNS—it does not create mailboxes or rewrite your Google Workspace / Microsoft 365 setup for you.
Watch this on CrowWake
Add the domain, leave the boxes checked, and the flock will crow when this drifts.
Or try the free MX monitoring / inbound checker with no login.
Related: what is an MX record, email authentication monitoring, email authentication, SPF monitoring, DKIM monitoring, DMARC monitoring, and MTA-STS monitoring (policy mx: lines should match live hosts).