| Yandex Mail | |
|---|---|
| Domains | yandex.ru, yandex.com, ya.ru, narod.ru |
| Mail routing | mx.yandex.ru for the consumer domains in September 2026, with narod.ru on mx1 through mx3.yandex.ru. Yandex 360 tells business domains to publish mx.yandex.net, and both names resolved to the same address when we looked. |
| What we can resolve | We resolve some mailboxes here |
How Yandex Mail answers a probe
What the server does when we open a connection and ask about one address.
- Consumer addresses that do not exist return 550 5.1.1 with reasonably consistent wording.
- Throttling is firm and applies per connecting IP, so throughput drops sharply on a large Yandex segment.
- Yandex 360 for Business allows a catch-all address, and tenants that enable it become accept-all domains.
- The ya.ru short domain and the legacy narod.ru addresses route to the same service.
The part that catches people out
What we do about it
We read the MX record before deciding what a domain is, which means a business domain on Yandex is reported as such. Where the tenant accepts everything we label it catch-all rather than guessing at the directory behind it.
Sending to Yandex Mail mailboxes
Verification is one step. These are the things that decide whether the message lands.
- Yandex publishes a postmaster interface that is more useful than Mail.ru's, though it expects a verified domain.
- Authentication requirements are conventional: SPF, DKIM and a published DMARC record all help.
- Regional sending rules and your own compliance position deserve a check before a campaign into this market.
Five spellings of one Yandex mailbox
Say these all sit in your list: ivan.petrov@yandex.ru, ivan-petrov@yandex.ru, ivan.petrov@yandex.com, ivan.petrov@ya.ru and ivan.petrov@yandex.kz. Yandex documents every one of them as the same mailbox. A Yandex login works across the company's national domains, and a period in the login can be written as a hyphen. Our lookup on September 19, 2026 agrees on the routing: yandex.ru, yandex.com, ya.ru, yandex.by and yandex.kz all return mx.yandex.ru.
So this provider needs its own normalization rule, and it's neither Gmail's nor Microsoft's. Fold the domain aliases to one form, treat the hyphen and the period as equal, and then compare. On a list with 2,000 Yandex rows that can remove a surprising number of repeats before you've paid to check any of them, and duplicates aren't billed in any case. Keep the original spelling in a separate column, though, since that's what the person typed and what your consent record refers to.
Two MX names, two kinds of customer
Consumer addresses answer on mx.yandex.ru. Companies that host their own domain with Yandex 360 are told to publish mx.yandex.net. Seeing the .net host on a business domain tells you an administrator exists, and that a catch-all may have been switched on. The .ru host on a national Yandex domain tells you it's a personal account, where nobody but Yandex sets the rules.
That split is useful when results look uneven. If the consumer rows resolve and the business rows all come back 250 for anything, nothing is broken. You're looking at two policies behind one brand. Yandex has also let users receive mail at their phone number as a local part, so a row that's a string of eleven digits at yandex.ru isn't automatically junk. It is personal data, though, and worth handling with more care than a nickname.
Questions people ask
Is Yandex easier to verify than Mail.ru?
Slightly. Yandex rejects unknown consumer recipients more consistently. Both throttle heavily, so coverage on a Russian-language list is lower than on a Western one regardless of which you are probing.
How do I tell a Yandex business domain from a consumer address?
By the MX record. A custom domain pointing at mx.yandex.net is a Yandex 360 tenant, and it may have a catch-all enabled where a consumer address would not.
Does a catch-all on Yandex mean the same thing as on Google?
Yes. Every RCPT TO returns 250 and the mailbox cannot be confirmed. The platform differs; the consequence for verification is identical.