Why “no MX” does not always mean “no mail”

An MX record names the servers that accept incoming email for a domain. It is natural to assume that removing every MX record turns off email reception. That assumption can be misleading: when a sending mail server finds no MX records, it may try to deliver to an address associated with the domain itself. This is often called the implicit MX fallback.

For example, suppose example.test has no MX record but has an A record pointing to a web server. A sender may attempt to connect to that server for mail delivery. If the web server is not running a mail service, the attempt will fail, but the sender might retry before giving up. If the server does accept mail, messages could reach a destination the domain owner did not intend to use.

The important distinction is between a missing MX record and an explicit statement that the domain accepts no incoming mail. They are not interchangeable, particularly for domains that have address records because they host a website.

What a null MX record says

A null MX record is an MX record with preference 0 and a target consisting of a single dot. Written in a zone-file style, it looks like “example.test. IN MX 0 .”. The dot is the entire target; it is not an abbreviation for a mail server. This record signals that the domain does not accept incoming email.

Use a null MX only when no address at that domain should receive mail. That includes obvious addresses such as contact@example.test and less visible destinations used by forms, account notices, or external services. If the domain receives even a small amount of legitimate mail, it needs an appropriate mail setup rather than a null MX.

A null MX is a routing signal, not a way to erase messages already in transit or a guarantee that every system will behave perfectly. It also does not, by itself, prevent someone from forging the domain in an email’s From address. Incoming delivery and sender authentication are separate concerns.

Choose the right setup for the domain’s job

For a domain that receives email, publish the MX records supplied by its receiving mail provider and confirm that the named hosts resolve as expected. Do not add a null MX alongside ordinary MX records: the two declarations conflict in purpose. For a web-only domain that should never receive email, a null MX makes the intention clearer than simply omitting MX records.

A domain can also send mail without receiving mail at the same domain. For instance, an automated notification might use a sender address at a dedicated subdomain whose incoming mail is intentionally disabled. Before configuring that subdomain with a null MX, check how replies and delivery failures are meant to be handled. The visible From address, the address used for delivery failures, and any Reply-To address can have different roles. A null MX on one domain does not automatically describe the others.

If the domain is not meant to send mail either, consider an SPF policy that authorizes no senders, such as “v=spf1 -all”, as part of a broader configuration. SPF addresses a different question from MX: it describes which systems may send using the domain in the SMTP envelope. Neither record replaces a review of all services that use the domain for email.

A safe way to check before making a change

Start by listing the exact domain names involved. An MX lookup for example.test does not tell you what is configured at news.example.test; each name needs its own check. Look up the MX records for the name in question, then check its A and AAAA records. If there is no MX but there is an address record, consider whether senders might try the implicit fallback.

Next, inspect the domain’s actual uses rather than relying only on DNS. Check website contact details, forms, mailboxes, mailing lists, notification settings, and third-party services for addresses at that name. Ask whoever manages those services before replacing an uncertain configuration. A mistaken null MX can stop legitimate incoming mail from being delivered.

After a change, verify that the published MX answer matches the intended setup. DNS caches may continue to serve an earlier answer for a while, so allow for a transition period when testing. If the goal is to stop receiving email, a correctly published null MX states that intention plainly; if the goal is reliable delivery, configure and test the receiving service instead.

Back to category ↗