Updated · Volt Ghost team
yandex.com, yandex.ru and ya.ru MX
Queried on 12 November 2026 via Cloudflare DNS-over-HTTPS; all three domains answered the same way.
| Domain | Pref. | Exchange |
|---|---|---|
yandex.com | 10 | mx.yandex.ru |
yandex.ru | 10 | mx.yandex.ru |
ya.ru | 10 | mx.yandex.ru |
The international yandex.com domain still receives on a .ru host. mx.yandex.ru returned one IPv4 address, 77.88.21.249, and one IPv6 address, 2a02:6b8::311, so IPv6-capable senders can deliver without IPv4. Looked up in Team Cymru's routing data, the IPv4 block 77.88.0.0/18 sits under AS13238 (YANDEX LLC, RU); it also showed a second origin AS for that block, so treat the network label as a hint.
Yandex's SPF, DMARC and (missing) MTA-STS
| Record type | Name | Answer, 12 Nov 2026 |
|---|---|---|
| SPF | apex TXT, same on all three | v=spf1 redirect=_spf.yandex.ru |
| SPF list | _spf.yandex.ru TXT | Six include: lists (one IPv6, five IPv4), ending ~all |
| DMARC | _dmarc.yandex.com and _dmarc.yandex.ru | v=DMARC1; p=none; fo=1, aggregate reports to returnpath.net and yandex.ru |
| DMARC | _dmarc.ya.ru | v=DMARC1; p=none; fo=1; rua=mailto:[email protected] |
| MTA-STS | _mta-sts.yandex.com, .ru, ya.ru | Not published |
| TLS reporting | _smtp._tls on each | Not published |
- DMARC in monitoring mode:
p=nonemeans receivers report failed mail but don't act on it, so a spoofed "@yandex.com" sender relies on SPF and spam filtering to be caught. - Failure reports on:
fo=1asks for a report when any check fails, and yandex.com and yandex.ru also send forensic reports to a returnpath.net address. - No MTA-STS: unlike GMX or Tuta, there is no published policy telling senders to require TLS.
Yandex next to Mail.ru
Both Russian providers use a single MX name and an SPF redirect, but their policies differ sharply: Mail.ru publishes DMARC p=reject and an MTA-STS policy in testing, while Yandex stays at p=none with no MTA-STS. For a company domain, our email host lookup shows Yandex 360 when the MX ends in yandex.ru or yandex.net.
Yandex addresses and sign-up screening
Forms that screen for throwaway addresses accept yandex.com and ya.ru, since mx.yandex.ru is a big provider's own server and not a shared temp-mail host. The weak DMARC policy doesn't change that; it only affects how spoofed Yandex mail is handled. The signals forms do look at are in how sites detect disposable email, and the disposable email checker shows whether one domain is listed.
Questions
What is the MX record for yandex.com?
yandex.com has one MX record, mx.yandex.ru at priority 10. yandex.ru and ya.ru publish exactly the same record.
Does Yandex Mail support IPv6 for incoming mail?
Yes. On 12 November 2026 mx.yandex.ru returned an IPv4 address (77.88.21.249) and an IPv6 address (2a02:6b8::311).
What DMARC policy does Yandex use?
p=none on all three domains, which asks receivers to report failures but not to block or quarantine them. That is looser than Mail.ru's p=reject.
Will a site reject a yandex.com address as disposable?
Not for being disposable. yandex.com, yandex.ru and ya.ru are long-standing Yandex Mail domains, and our checker's open-source throwaway list doesn't include them.
