Skip to content
Standard SMTP codes · permanent error

550 5.7.27: sender 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.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
550 5.7.27
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
550 5.7.27 Sender address has null MX

What it means

A null MX (RFC 7505) is a single MX record pointing to a dot, declaring that a domain receives no mail. Mail from such a domain cannot get bounces or replies, and an unusable return address often signals spam, so receivers may refuse it; RFC 7505 says they should use 550 5.7.27 when they do. It is permanent. RFC 7505 also advises domain owners not to publish a null MX on any domain they use as a sender, so the fix is to replace it with real MX records or to send from another domain.

Common causes

  • A domain that publishes a null MX is also used in the From or envelope sender address.
  • A sending subdomain set up with a null MX by mistake.

How to fix it

  1. 01Run an MX lookup on your sender domain.
  2. 02If it shows a single MX record of a bare dot, replace it with MX records for a server that receives your bounces and replies.
  3. 03Or send from a domain 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. 5.1.8Sender domain cannot receive mail.The domain in the sender address does not exist or cannot accept mail, so the receiving server refuses a message whose bounces could never be returned.StandardPermanent
  3. 556Domain 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.StandardPermanent

5.7.27 at other providers

  1. 550 5.7.27SPF did not pass, blocked.Gmail rejected the message because it failed SPF, which Gmail requires of bulk senders along with DKIM.GmailPermanent

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