What Is Null MX?

An explicit no-mail declaration

A domain can exist for a website or another service without accepting email. A null MX expresses that choice directly: the MX preference is zero and the exchange is a single dot. This is not a placeholder for a provider hostname. Publishing it on a domain that needs to receive replies would declare the opposite of the intended email configuration.

Missing MX data means something different. SMTP routing can fall back to address records in circumstances defined by the protocol. A null MX removes ambiguity by announcing that there is no incoming mail service for that domain. It should not be combined with ordinary MX records as though it were an additional backup destination.

What it means for prospect data

If a contact address uses a domain with a confirmed null MX, the evidence concerns the domain's receiving configuration. It is not merely a low engagement score or a temporary full mailbox. Keep the result distinct from catch-all behavior, a timeout and a failed network request in the verification provider's own system. Those outcomes require different follow-up decisions.

Check before changing or sending

Record the exact domain queried, authoritative response, lookup time and verification result. If the address was collected from an old source, investigate whether the organization's real contact domain changed. Do not invent a different mailbox or retry the same address indefinitely because the company website still loads. Website availability and email acceptance are separate services.

For your own domains, make the receiving requirement explicit before publishing DNS. A domain used in human correspondence may need working reply and operational addresses even when another service handles outbound submission. Review null MX as an intentional service declaration, rather than as a generic security record to copy into every new domain.