Where does an email go after an MX lookup?
When a mail server sees an address such as ivan@company.ru, it looks up the MX record for company.ru. The record names the receiving mail server and its priority: lower numbers are tried first. If the primary server is unavailable, the sending system tries the next listed route.
| Domain state | What happens to the email | Outreach risk |
|---|---|---|
| MX points to a working mail service | The server accepts the message and routes it to the mailbox | The address can be assessed using other signals |
| MX is missing or points to a nonexistent host | The sender receives a delivery failure | The list accumulates bounced addresses |
| MX works, but the mailbox was deleted | The domain exists, but that specific address cannot receive mail | You need another contact at the same company |
MX controls the route for incoming email. It does not establish sender reputation or guarantee inbox placement. Domain identity is addressed separately by an SPF record.
How can an MX error lose a reply when the first email was sent?
Imagine an equipment supplier writes to a prospect about an expanding warehouse and asks whether a project estimate would be useful. The decision-maker replies, “Yes, please send an example.” If the sender’s domain retained an incorrect MX record after a mail migration, that reply may never reach the sales inbox. To the prospect, it looks like a delivery failure; to the sales team, it looks like lead silence.
- Before launch, send a test email from an external mailbox to every domain you plan to use for correspondence.
- Reply to that test message and confirm that the reply reaches the intended mailbox, not merely a service interface.
- After changing email providers, verify the MX record, mailboxes and reply route before restarting the campaign.
List quality is a separate task: confirm the company and role, verify the address, then record the result. See email list verification for that work.
Which MX mistakes appear before an outreach launch?
- The MX record contains an IP address rather than a mail-server hostname. An MX record must point to a hostname, which is then resolved to an IP address.
- After moving to a new mail service, the old MX records were removed but new ones were not added, or contain a typo.
- Two providers are configured at once without a clear priority, so some messages go to the old server and others to the new one.
- Messages are sent from a subdomain, but the team checks only the main domain and not where replies to the subdomain will arrive.
A weak check is confirming only that a test email can be sent. A useful check covers the full loop: sending, receiving, replying and seeing the reply in the manager’s mailbox. Then you can address email deliverability and begin email outreach.
When will an MX record not solve an email problem?
A correct MX record will not help if an email is sent to a nonexistent address, the recipient domain is temporarily refusing external mail, or the message is filtered before the inbox. It also cannot fix an irrelevant offer: technical delivery does not create buyer interest.
MX validation is not a sufficient measure of list quality. For a focused company list, you need to assess the role, contact source and a backup route such as a second corporate address. If the task is broader than one DNS setting, start with decision-maker list building rather than a bulk send.