SMTP error 5.1.2 Bad destination system address

What SMTP error 5.1.2 means

The domain after the @ cannot receive mail. Either it does not exist in DNS, or it exists and publishes nothing that accepts email. No receiving server ever answered, so nobody has looked the recipient name up, and the bounce is written by your own platform rather than the far end. IANA registers no basic reply code here, so the three-digit number in front varies between systems.

Address status
Sent by Your own sending server, once it has finished trying to find the destination
Occasional

What SMTP error 5.1.2 Bad destination system address actually means

Everything hinges on the right-hand side of the address. Your mail platform queries DNS, looks for MX records, falls back to an A record if there are none, and comes up with nothing usable. The distinction from an unknown mailbox is why both codes exist: one means the destination answered and disowned the recipient, this one means there was never a destination to ask. The recipient organisation therefore cannot help you, because their logs hold nothing. RFC 3463 permits this only as a permanent failure, so a platform that thinks a domain might return holds the message under a 4.4.x code instead.

The destination system specified in the address does not exist or is incapable of accepting mail. For Internet mail names, this means the address portion to the right of the "@" is invalid for mail. This code is only useful for permanent failures.
— RFC 3463

How 5.1.2 appears in a bounce

The leading 5 is the server's verdict rather than part of the code's identity: it marks this as a permanent failure, which means the sending server has given up and returned the message.

RFC 3463 is explicit about which verdicts this code can carry: “This code is only useful for permanent failures.”

What causes SMTP error 5.1.2 on a business phone system

A misspelt domaingmial.com, hotmial.co.uk, a company name with the hyphen in the wrong place, .co.uk typed as .uk. Domain typos fail differently from mailbox typos precisely because nothing exists to answer.
The domain registration has lapsedA business that lets a domain expire loses its DNS entirely once the registrar pulls the zone, and every address on it dies at the same moment. Contacts who wrote to that firm last week now bounce.
The domain resolves but publishes no MX and no usable A recordCommon with parked domains, brand-protection registrations and domains used only for a website hosted elsewhere. The domain is real, the website may load fine, and nothing is configured to accept mail for it.
An internal-only or invented domain leaking into a real sendAddresses ending .local, a bare server hostname, or a test domain from a development environment. Line-of-business applications and copiers are the usual sources, writing to an address that only made sense inside the building.
MX records broken during a migration or DNS changeA cutover to Microsoft 365, or a zone rebuilt from scratch, can leave MX records pointing at a decommissioned host. During propagation some senders resolve the new records and some resolve nothing, so it looks intermittent.

How to fix SMTP error 5.1.2

Look the domain up yourself before anything elseRun nslookup -type=mx against the domain, or use a public MX lookup tool. NXDOMAIN means the domain does not exist. An answer with no MX records means it exists but is not set up for mail. Those lead in different directions.
Check the spelling against a source you trustTake the domain from the recipient's website or a previous message from them, not from a contact record typed by hand years ago. Correct the stored record as well as the message you are sending.
Check the registration if the domain has simply vanishedA WHOIS lookup shows whether it has expired or been transferred. If it has lapsed, nothing you change at your end will help and the recipient needs contacting another way.
Fix the address at source when an application generates itWhere the failing domain is internal or invented, the repair belongs in the copier, the accounts package or the monitoring tool. Give it a real address on a domain you own and relay it through a connector.
If the failing domain is your own, publish MX records and verify themPoint MX at your mail platform, wait for propagation, then confirm from outside your own network that the records resolve. Microsoft 365 lists the required records per domain and flags the domain as unhealthy until they match.

Fixing the underlying problem

This page explains the code. These guides walk through the fix in detail.

Questions about SMTP error 5.1.2

How do I tell this apart from an unknown mailbox?

Look at which side of the @ the problem sits on and who wrote the bounce. Here the domain has no mail service, so the message never reached the recipient's systems and your own platform generated the report. An unknown mailbox means their server answered and refused the name in front of the @.

The recipient's website works, so why can they not receive email?

Web and email are separate records in DNS. A domain can have a healthy A record serving a website while having no MX record and nothing listening for mail. It happens routinely with domains registered for a brochure site or held defensively.

Will it keep retrying, or is that bounce final?

Final. The specification limits this code to permanent failures, so the message is returned rather than queued. Where a mail system judges a DNS problem might be temporary it uses one of the 4.4.x network codes and holds the message, typically for a day or two.

Related SMTP status codes

Source. SMTP error 5.1.2 Bad destination system address is defined in RFC 3463 and registered in the IANA SMTP Enhanced Status Codes registry. The causes and fixes above are drawn from our own experience supporting UK business email systems.

All Email delivery & SMTP codes