DNSVerdictAll toolsGuidesHow it works

554 SMTP bounce: transaction failed

Permanent failure (554): the receiving system will not accept this message as sent, so resending it unchanged will not help. Fix the cause first.

What 554 means

The server refuses the transaction. In a greeting, it means the host provides no SMTP service at that address. Permanent for this attempt.

Message text

Transaction failed (Or, in the case of a connection-opening response, "No SMTP service here")

Common causes of 554

How to fix 554

  1. Check MX records with MX lookup; the MX host must run SMTP.
  2. Check your sending IP with blocklist check.
  3. Verify SPF and DMARC with SPF checker and DMARC checker.

Check your domain

Check the SPF record of your sending domainRuns in your browser; nothing is uploaded.

Have the full bounce message? Paste it into the bounce code lookup and it will match the code and the provider for you. Open the bounce code lookup.

How to read 554

The first part, 554, is the SMTP reply code. Transaction failed: a general permanent failure, often a policy or reputation block. Replies that start with 4 are temporary and replies that start with 5 are permanent (RFC 5321 §4.2.1).

This reply carries no enhanced status code. The three-digit reply code is the only machine-readable signal, so read the text that follows it to learn the reason.

Do not keep resending the same message: a permanent failure repeats until the cause is fixed. Correct the cause, then send a new message.

Official source: www.rfc-editor.org. Last verified 2026-10-20.

Related guides

Related codes

FAQ

What does 554 mean?

The server refuses the transaction. In a greeting, it means the host provides no SMTP service at that address. Permanent for this attempt. This is a permanent failure.

How do I fix 554?

Check MX records with MX lookup; the MX host must run SMTP. Check your sending IP with blocklist check. Verify SPF and DMARC with SPF checker and DMARC checker.

Is 554 permanent, and should I retry?

554 is a permanent failure, so retrying the same message will fail again. Fix the cause first, then send a new message.

All bounce codes