Microsoft 365, AD and Windows · #24

Online SMTP Error Code Lookup

Decodes the SMTP code in a bounced email into class, subject and detail and tells you whether the error is permanent or temporary.

  • Data is processed in your browser and not sent to a server

Tool

E.g. 550 5.1.1 User unknown

What does this tool do?

In a bounce (NDR) the important part is not the whole text but two codes: the three-digit basic SMTP code (550, 451) and the dotted enhanced status code (5.1.1, 4.7.0). The first digit says permanent (5) or temporary (4), the middle the subject, the last the detail. The tool finds these codes in the text and explains them per RFC 3463 and related RFCs.

How to use it

  1. Paste the error line or SMTP response from the NDR; pasting the whole text also works.
  2. Press Calculate.

Fields

SMTP response or NDR text
E.g. 550 5.1.1 User unknown

Worked example

InputValue
SMTP response or NDR text
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'

Expected result: 550 – permanent error; 5.1.1 – address status: destination mailbox does not exist.

The recipient address was not found on the receiving server. Check the spelling first; if it appears after a migration within Microsoft 365, the old LegacyExchangeDN may need to be added as an x500 proxy address.

Second scenario

InputValue
SMTP response or NDR text
451 4.7.0 Temporary server error. Please try again later. PRX4

Expected result: 451 – temporary error; 4.7.0 – security/policy status: other. The sending server will retry.

Method and assumptions

The text is searched for NNN X.Y.Z, otherwise for X.Y.Z alone. The first digit of the basic code gives the class: 2 (success), 4 (temporary) or 5 (permanent).

The enhanced status code is decoded per RFC 3463: class (X), subject (Y: address, mailbox, system, network, protocol, content, security) and detail (Z). Codes such as 5.7.23–5.7.27 come from RFC 7372 and RFC 7505.

Using the result and troubleshooting

For 4.x.x errors the sending server retries for a while; no action is needed unless it keeps happening, then check greylisting or rate limits on the receiving side.

For 5.7.x (security) errors check your SPF, DKIM and DMARC records with the related tools; the receiver usually rejected for authentication or reputation reasons.

Limits and common mistakes

  • Vendor-specific text (Microsoft RESOLVER.ADR…, Google 'gsmtp' notes) is not interpreted; only standard codes are explained.
  • No definite root cause is produced; the same code can have different causes.

Frequently asked questions

Why do 550 and 5.7.1 appear together?

550 is the older basic SMTP code, 5.7.1 the more detailed enhanced status code. Read them together: permanent rejection for a security/policy reason.

Related tools and service

  • Email Header AnalyzerOrders the Received chain of an email header and shows delays between hops and authentication results.
  • MX Record LookupShows which servers receive mail for a domain, in which order, and their addresses.

Related service: Microsoft 365, Azure, AWS and Google Cloud Services

Systems online tools · See all online tools