yandex.ru is a free email provider

yandex.ru is a major consumer mailbox provider. Anyone can open an address, and at this scale a forged message is usually caught by the provider even where the domain's own records would let it through.

Major provider Spoofable

81 /100

Strong

Email authentication report card

What yandex.ru publishes in DNS to stop other people sending mail in its name, read record by record.

5 weak

Can mail be forged as this domain?

Yes on paper, but unlikely to land

DMARC is set to p=none, which only asks for reports, so nothing this domain publishes tells a receiver to reject a forged message. In practice a forgery will still be caught: a provider this size runs its own reputation and content filtering on top of what the domain publishes. That safety net is the provider's, not the domain's.

  • Weak

    SPF ~all

    The record ends in ~all. Mail from a host outside the list is only marked, not rejected, so it usually still arrives.

  • Weak

    DMARC p=none

    A DMARC record is published, but p=none only asks for reports. Receivers are told to deliver failing mail anyway, so this stops no forgery.

    A checker that reports "DMARC found" here is telling you nothing useful.

  • Weak

    MTA-STS Not published

    No MTA-STS policy, so a sending server has nothing that tells it to insist on verified TLS for this domain.

  • Weak

    DNSSEC Not signed

    The zone is not signed. A resolver has no cryptographic way to tell a real answer from a forged one.

  • Weak

    TLS-RPT Not published

    No reporting address, so failed TLS deliveries to this domain go unnoticed by its owner.

Why it scores 81?

  1. Accepts mail through 1 MX host.
  2. Mail is handled by a mailbox provider we recognize.
  3. A website answers on this domain.

What to publish to close the gaps

The records yandex.ru is missing, in the order they are worth doing. Owner names are written out in full, so they work whether your DNS panel wants a full name or a relative one.

  1. Tighten SPF to -all

    Nameyandex.ru
    TypeTXT
    Valuev=spf1 <your existing mechanisms> -all

    Keep the mechanisms you already have and change the final qualifier. Anything softer leaves the forgery path open.

  2. Move DMARC off p=none

    Name_dmarc.yandex.ru
    TypeTXT
    Valuev=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]

    p=none blocks nothing. Once your reports show every legitimate sender passing, raise the policy to quarantine and then to reject.

  3. Publish an MTA-STS policy

    Name_mta-sts.yandex.ru
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

    Serve the policy body at https://mta-sts.yandex.ru/.well-known/mta-sts.txt, start it in testing mode, then switch it to enforce so senders refuse to deliver over an unverified connection.

  4. Publish a TLS reporting address

    Name_smtp._tls.yandex.ru
    TypeTXT
    Valuev=TLSRPTv1; rua=mailto:[email protected]

    Without it, a sending server that could not negotiate TLS with your mail hosts has nowhere to tell you.

  5. Sign the zone with DNSSEC

    Turn DNSSEC on with your DNS provider, then publish the DS record it hands you at your registrar. Every record above is only as trustworthy as the answer that carries it, and signing the zone is what makes the answers verifiable.

Questions about yandex.ru

Every answer below is generated from the stored record for this domain.

Is yandex.ru a disposable email domain?
No. yandex.ru is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is yandex.ru spoofable?
Yes on paper, but unlikely to land. DMARC is set to p=none, which only asks for reports, so nothing this domain publishes tells a receiver to reject a forged message. In practice a forgery will still be caught: a provider this size runs its own reputation and content filtering on top of what the domain publishes. That safety net is the provider's, not the domain's.
Does yandex.ru publish SPF and DMARC?
yandex.ru publishes an SPF record, though it does not end in -all, so hosts outside the list are not treated as forgeries. DMARC is published but set to p=none, which only asks for reports. It looks like protection and is not.
Who handles email for yandex.ru?
Mail for yandex.ru is handled by Yandex Mail, which carries 27 other domains we track.
How old is the yandex.ru domain?
The registry for .ru does not publish a registration date we can read, so we do not state an age.
How do I block yandex.ru on my signup form?
We do not classify yandex.ru as disposable, so blocking it outright would turn away real people. If you want to act on it, decide on the signals listed above rather than the name.
Can I trust email from yandex.ru?
yandex.ru scores 81 out of 100, which is a strong band. The score is a summary of the classification, infrastructure, authentication, reputation and lifecycle signals we hold, not a judgment about any individual sender at that domain.

Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.