# 556 5.1.10: recipient address has null MX

URL: https://iblockspam.com/smtp-errors/556-5-1-10
Last updated: 2026-10-09

Code: 556 5.1.10 (permanent failure, the message bounced)
Provider: Standard (RFC)

The recipient's domain says, in DNS, that it accepts no email at all (a null MX record). The message can't be delivered to any address at that domain.

RFC 7505 defines the "null MX": a single MX record with preference 0 and a host of "." that a domain publishes to say it doesn't accept email. A domain with a null MX must not publish any other MX record.

When a sending or relay server finds a null MX for the recipient's domain, RFC 7505 says it should reject the recipient with reply code 556 and enhanced code 5.1.10, "Recipient address has null MX". The 556 reply code itself comes from RFC 7504: an intermediate system that can tell a destination won't accept mail, without trying to connect, returns 556. The IANA registry lists X.1.10 with 556 as its basic code.

Often this comes from your own provider's servers, before your message leaves. It's a clear answer, not an error to work around: the domain owner has deliberately said it doesn't take mail. The address is probably a typo, an old company domain, or a web-only domain. Microsoft 365 also uses the number 5.1.10 for a different reason, "Recipient not found"; see the Microsoft entry for that.

## Common causes

- The domain doesn't use email and publishes a null MX to say so.
- A typo turned the address into a different, mail-less domain.
- The organization moved to another domain and retired email on the old one.

## How to fix it (sender)

- Check the domain spelling and ask the recipient for their current address.
- Remove the address from mailing lists; it will never accept mail.

## How to fix it (recipient or admin)

- If your domain should receive email, replace the null MX with MX records for your mail provider or filtering service.

**Q: What does a null MX record look like?**
It is a single MX record with preference 0 and a host of "." (a dot), defined in RFC 7505. An MX lookup on the domain shows it. A domain with a null MX must not publish any other MX record.

**Q: Should I publish a null MX on my unused domains?**
If a domain never receives email, yes: senders then fail immediately with a clear reason. Pair it with SPF "v=spf1 -all" and a DMARC reject policy so the domain can't be used for spoofing either.

Sources:
- RFC 7505: A "Null MX" No Service Resource Record for Domains That Accept No Mail: https://www.rfc-editor.org/rfc/rfc7505
- RFC 7504: SMTP 521 and 556 Reply Codes: https://www.rfc-editor.org/rfc/rfc7504
- IANA: SMTP Enhanced Status Codes registry: https://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xhtml

---

Source: iBlockSpam, https://iblockspam.com/smtp-errors/556-5-1-10 (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt