Skip to content
Standard SMTP codes · permanent error

556: domain does not accept mail

A relay or sending server knows the recipient's domain does not accept mail, usually from its null MX record, and refused the address without trying to deliver.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
556
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
556 Domain does not accept mail

What it means

RFC 7504 added 556 for an intermediate server that can tell, without connecting, that the destination does not take mail. The standard way to tell is a null MX record (RFC 7505), and RFC 7505 pairs 556 with enhanced code 5.1.10. The client treats it like any permanent negative reply, so the message is returned at once instead of waiting in a queue. It nearly always means the address has the wrong domain.

Common causes

  • The recipient domain publishes a null MX record.
  • A typo or a wrong domain that happens to publish a null MX.

How to fix it

  1. 01Check the domain in the address.
  2. 02Run an MX lookup to confirm the domain publishes a null MX.
  3. 03Ask the recipient for an address that receives mail.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 556 5.1.10Recipient domain has a null MX.The recipient's domain publishes a null MX record, its formal statement that it never receives email, so the message was refused at once without any delivery attempt.StandardPermanent
  2. 521Host does not accept mail.The server answered the connection only to say that it never accepts mail, so delivery to this host cannot work.StandardPermanent
  3. 550 5.7.27Sender domain has a null MX.The domain in the sender address publishes a null MX record, which says it never receives mail, so the receiver refuses mail whose bounces could not be delivered.StandardPermanent

556 at other providers

  1. 556Recipient domain publishes a null MX.The domain you are writing to publishes a null MX record, which declares that it accepts no email, so the message cannot be delivered.GMX, WEB.DEPermanent
  2. 556Recipient domain publishes a null MX.The domain you are writing to has a No Service MX record (null MX), which means it can neither receive nor send email, so the message cannot be delivered.IONOSPermanent

Further reading

All 105 standard codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer