Skip to content
iBlockSpam
Get started
Check your domain Get started Log in
How it works
Platforms
Microsoft 365 Google Workspace cPanel / WHM Exchange Server
Solutions
Small business MSPs Hosting providers Law firms Accounting firms Healthcare practices Real estate & title
Free tools Pricing
Blog
All guides
By topic
Email security basics Phishing & threats SPF, DKIM & DMARC Setup guides Running email day to day Switching & migration Choosing a filter
Reference
Glossary Research: top 1,000 sites
SMTP error code · Gmail / Google Workspace

553 5.1.2: we weren't able to find the recipient domain

553 5.1.2 Permanent failure (5xx): the message bounced
By iBlockSpam Team Checked against sources 3 sources How we check our content
What it means

The part of the recipient address after the @ isn't a domain that can receive mail, usually because of a typo, extra punctuation or a domain that has expired.

What the bounce says
553 5.1.2 We weren't able to find the recipient domain. Please check for any spelling errors and make sure you didn't enter any spaces, periods, or other punctuation after the recipient's email address.

Gmail's text for 553 5.1.2, as listed in Google's SMTP errors reference.

What 553 5.1.2 means

RFC 3463 defines X.1.2 as "Bad destination system address": the destination system in the address doesn't exist or can't accept mail, which for internet mail means the part to the right of the @ is invalid for mail. RFC 3463 says the code is only useful for permanent failures. RFC 5321 defines 553 as "Requested action not taken: mailbox name not allowed".

Gmail's text spells out the usual causes: a spelling error in the domain, or spaces, periods or other punctuation typed after the address. Google's bounce help gives examples such as john.doe@gmal.con and an address with dots at the end. A domain that has expired, or that never published mail records, fails the same way.

Fix the address and send again. If the domain looks right, look it up: a quick MX lookup shows whether it publishes mail servers. If the domain exists but has no MX record and no address record, or publishes a null MX, it doesn't accept mail, and you need another way to reach the person.

Likely causes

  • A typo in the domain, such as gmal.com, outlok.com or a wrong ending like .con.
  • Spaces, periods or other punctuation after the address, often from copy and paste.
  • The recipient's domain has expired or was never set up for email.
  • An old address saved in contacts or auto-complete for a company that changed domains.

How to fix it

If you sent the message

  1. Check the address character by character, especially the domain and its ending.
  2. Delete the saved contact or auto-complete entry and type the address again.
  3. Run an MX lookup on the domain to see whether it accepts mail.
  4. If the domain no longer exists, ask the person for a current address another way.

If you're the recipient or their admin

  1. If people report this error for your real domain, check that the domain hasn't expired and that its MX records are published.
MX Lookup Email Health Check

Frequently asked questions

What's the difference between 553 5.1.2 and 550 5.1.1?

550 5.1.1 means the domain is fine but the mailbox doesn't exist. 553 5.1.2 means the domain itself, the part after the @, can't be found or can't receive mail.

The domain is spelled right. Why does Gmail still say it can't find it?

The domain may have expired, or it may not publish mail records. Run an MX lookup: if it shows no mail servers or a null MX, the domain doesn't accept mail and only its owner can fix that.

Sources

  1. Gmail SMTP errors and codes (Google Workspace Admin Help)
  2. RFC 3463: Enhanced Mail System Status Codes
  3. Fix bounced or rejected emails (Gmail Help)

Provider messages are quoted as the provider publishes them. Servers can change their wording, so the bounce you received may differ slightly.

Related codes

Related guides

Email security basics

What is an MX record?

What an MX record is, how priority values pick the server that gets your mail, why backup MX can bypass a spam filter, and how to check your own records.

8 min read Setup guides

Null MX record: how to tell the world a domain receives no email

How to publish a null MX record (MX 0 .) for a domain that gets no email, what senders see (556 5.1.10), when not to use it, and how to check it worked.

9 min read Switching & migration

How to change MX records without losing email

A cutover checklist for MX changes: lower TTL, stage the new destination, keep the old server accepting mail, verify with headers and roll back cleanly.

11 min read