An absent MX record can leave SMTP address fallback in play. Learn how null MX differs, and what to check before declaring an acquired domain unused for email.
No MX record does not, by itself, mean that a domain rejects email. SMTP has a fallback: when no MX record is found, a sending mail system can look for the domain's A or AAAA address records instead. A domain that deliberately accepts no mail has a different signal available: a null MX record.
For someone buying an expired domain, holding a name for a future project, or preparing a post-auction launch, this distinction belongs in the handoff checklist. A working website, an empty MX search, and a deliberate no-mail declaration are three different pieces of evidence.
Why an empty MX result is not a no-mail declaration RFC 7505 section 1 describes the mail-routing sequence: the sending system first looks for an MX record and, if none is found, falls back to an A or AAAA record. That can lead it to an address intended for a website rather than a mail server. The fallback does not prove that a mailbox exists or that delivery will succeed.
If no SMTP service accepts the connection there, a sender may keep retrying before reporting failure. The important point is narrower: removing MX records is not the explicit statement that a domain accepts no mail. Also distinguish a successful lookup with no MX records from a failed lookup. A timeout, DNS error, or incomplete dashboard scan is not evidence that the authoritative DNS has no MX records.
Record the exact name, record type, response and time checked before drawing a conclusion. What a null MX actually says RFC 7505 section 3 defines a null MX as a single MX record with preference 0 and exchange . , a dot representing the DNS root. It explicitly indicates that there is no mail exchanger for that domain. This is not an instruction to send mail to a server named dot.
The same section says a domain advertising a null MX must not advertise any other MX record. Null MX is therefore not a backup entry to add beside a normal mail provider's MX records. No MX records found: SMTP's address-record fallback may apply. This is not an explicit no-mail declaration. Ordinary MX records: DNS identifies mail exchangers.
Their presence alone does not prove that a particular mailbox works. A single null MX: DNS explicitly declares that this domain accepts no mail. A compliant sending system can reject delivery without trying a fallback mail destination. Read those as different states, not a progression every domain should follow. A business domain that needs email and a name deliberately kept out of email have different requirements.
Check outgoing mail and recovery dependencies too Do not choose a no-mail declaration only because nobody expects to read an inbox. RFC 7505 section 4.2 says null MX is primarily intended for domains that neither send nor receive mail. It advises against publishing null MX for a domain used in the SMTP MailFrom return address or the message From address, because that mail risks being rejected.