yandex.net

yandex.net · Last checked 2026-10-04 02:03 UTC

yandex.net

Poor, with 2 things to fix

yandex.net scored 58/100 (grade D). The main issues are no DMARC record and no DKIM key found for the common selectors.

Checked 2026-10-04 02:03 UTC · fresh check

1 passed1 needs attention1 failing5 for information
Fix this firstThe change with the biggest effect

Publish a DMARC record

Starts DMARC in monitoring mode (p=none), so you can see who sends as yandex.net before enforcing a policy. Move to quarantine once the reports show only your own services.

TypeTXT
Name / Host
_dmarc.yandex.net

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=none; adkim=r; aspf=r

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Add a new TXT record with the name and value above.
  3. Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?Only one MX hostInfo
  • Info: Only one MX host

    All mail for yandex.net goes to mx.yandex.ru. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.

SPFWho may send as you?SPF ends in softfail (~all)Info
  • Info: SPF ends in softfail (~all)

    "~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
  • Warning: No DKIM key found for the common selectors

    None of the 47 selectors probed under yandex.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for yandex.net.

DMARCWhat happens to fakes?No DMARC recordFailing
  • Fail: No DMARC record

    There is no v=DMARC1 TXT record at _dmarc.yandex.net. Without DMARC, receivers have no policy for mail that fails SPF and DKIM, and Gmail and Yahoo require one for bulk senders. Start with p=none and a rua address to collect reports.

    How to fix this
AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.yandex.net. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.

    How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

    No MTA-STS record at _mta-sts.yandex.net. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

    How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.yandex.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Publish the MTA-STS recordTXT

Tells sending servers that yandex.net publishes an MTA-STS policy at https://mta-sts.yandex.net/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.yandex.net

Some DNS providers want just “_mta-sts” here.

Value
v=STSv1; id=202610040203

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.yandex.net. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location
https://mta-sts.yandex.net/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: mx.yandex.ru
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to yandex.net, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.yandex.net

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@yandex.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.yandex.net with the value v=TLSRPTv1; rua=mailto:<that address>.

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.yandex.net

  1. Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://yandex.net/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.yandex.net with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.