556 means the recipient’s domain says it accepts no mail at all — it publishes a null MX (“0 .”). The sender’s server knows this without connecting anywhere, so the failure is reported at once instead of days later.
| Code | 556 |
| Meaning | Domain does not accept mail |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | RCPT |
| What the sender does | Returns the message at once |
| Defined in | RFC 7504; RFC 7505 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What causes it
- A typo in the domain — alice@www.example.com instead of alice@example.com.
- Sending to a domain that is only a website, or parked.
What to do
- Check the recipient’s address; the domain does not receive mail.
What each provider means by it
| Who | What they say |
|---|---|
| Postfix | Answers 556 for a recipient whose domain has a null MX (reject_unknown_recipient_domain), and 550 for such a sender. |
| Yahoo | Lists a null MX among its reasons for a permanent policy rejection. |
Worth knowing
The enhanced code that goes with it is 5.1.10. For a sender whose own domain has a null MX, the reply is 550 5.7.27.
Sources
Checked on 27 September 2026 against these official sources:
- RFC 7504: SMTP 521 and 556 Reply Codes — rfc-editor.org
- RFC 7505: A “Null MX” No Service Resource Record for Domains That Accept No Mail — rfc-editor.org
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Postfix Configuration Parameters — postfix.org
- SMTP Error Codes — senders.yahooinc.com