yandex.kz email servers, SPF and DMARC

yandex.kz publishes a single MX host, mx.yandex.ru. With no backup host, a sender that can't reach it queues the message and retries until the server answers or the queue gives up.

2 other domains we checked on the same day also hand their mail to Yandex Mail servers, with different records from yandex.kz: inbox.kz and hotbox.ru.

The record on 5 November 2026 was v=spf1 redirect=_spf.yandex.ru.

In plain terms, it delegates to _spf.yandex.ru. The top level uses 1 DNS-querying term; SPF allows 10 in total including nested includes (RFC 7208 §4.6.4).

The record is v=DMARC1; p=none; fo=1; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected].

p=none only asks for reports; failing mail is delivered as normal.

Aggregate reports go to auth.returnpath.net and yandex.ru, so the domain's owner sees who sends mail as @yandex.kz.

2 other domains published exactly the same MX hosts and SPF record as yandex.kz on 5 November 2026: yandex.by and yandex.com.tr. Mail to any of them lands on the same servers.

yandex.kz shares mx.yandex.ru with yandex.ru. When we tested those servers for yandex.ru on 12 October 2026, the result was: Verifiable. The server rejects unknown recipients during the SMTP conversation.

Our checker treats @yandex.kz like any domain: syntax, MX, disposable and role checks first, then a made-up address to rule out a catch-all, then your address at RCPT TO, disconnecting without sending. We have not tested @yandex.kz itself, but its mail goes to the same servers as yandex.ru, so expect @yandex.kz results to follow the pattern described there. Each result carries its own reason.

DNS tells you where mail goes, not whether one person's mailbox still exists. For a list, run the whole file through a verifier before you send: invalid rows come out, risky rows (catch-all, unknown, refused) go in their own segment, and valid rows are safe to mail.