MailFixIt

Gmail destination-domain error

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

Gmail returns 553 5.1.2 when it cannot find the recipient domain. Check the characters after @ for spelling, spaces, or punctuation, then inspect that destination domain's registration and DNS.

Problem description

Gmail reports:

553 5.1.2 We weren't able to find the recipient domain.

Run this automated test on the recipient domain

Enter your domain. MailFixIt checks the relevant DNS records automatically and shows the evidence.
What MailFixIt can test: current public DNS, MX, and Null MX state for the destination domain entered. It cannot prove an individual mailbox exists or inspect private recipient routing.
Is this temporary or permanent?

The 553 result is permanent for the submitted address. Correct the address or wait for the domain owner to repair DNS before sending a new message.

Probable causes

How to resolve it

  1. Extract only the domain after @.
  2. Compare it with the recipient's official contact information.
  3. Check registration, nameserver delegation, and current MX intent.
  4. If you do not own it, send evidence to the recipient through another channel.
  5. Send a new message only after correction.

Frequently asked questions

What does Gmail 553 5.1.2 mean?

Gmail could not find the recipient domain.

Which domain should I check?

Enter the domain after the at-sign in the rejected recipient address, not your sending domain.

Can the sender fix the recipient's DNS?

The sender can correct a typo; only the recipient domain owner or provider can repair its registration, delegation, or mail routing.

Related email diagnostics

SMTP 550 5.1.2: Bad destination system addressFix SMTP 550 5.1.2 by checking the rejected recipient address and the recipient domain's DNS and mail route. Gmail 550 5.1.1: The email account that you tried to reach does not existResolve Gmail 550 5.1.1 by verifying the recipient address, account status, aliases, and recent mailbox changes. DNS record not detected after saving the provider-issued valueDiagnose a DNS record that is not detected after saving it. Compare the exact TXT, CNAME or MX value, identify a duplicated hostname, and avoid unsafe DNS changes.

Primary sources: Gmail SMTP errors and codes.