bk.ru: mail servers, SPF, DMARC, DKIM and reputation

Mail servers for bk.ru

DNS lists 1 mail host for bk.ru, starting with mxs.mail.ru. Lower priority values are tried first; the rest exist for failover.

Who runs the mail

The hosts match the pattern of an unrecognised provider. The mail hosts do not match a known provider pattern, so the domain is probably self-hosted or on a smaller provider. Catch-all behaviour varies from server to server, which is exactly why a mailbox-level probe, not the MX record, decides whether an address exists.

What this means for verification

For bk.ru, verification runs the whole pipeline: syntax, live MX, the open lists, and then the SMTP handshake with the mail host, with no message ever transmitted. Each verdict carries a machine-readable reason.

SPF for bk.ru

bk.ru publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record has no explicit all mechanism, so receivers treat unlisted servers as neutral.

DMARC for bk.ru

bk.ru enforces DMARC at p=reject, so messages that fail alignment are dropped by receivers rather than delivered or quarantined. That is the end state most domains work towards.

Why it matters

Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from bk.ru. A domain with a strict SPF record and an enforcing DMARC policy is hard to spoof and easier to deliver for; one without either is neither. Spaw reports has_spf and dmarc_policy on every lookup and adds a small risk weight when SPF is missing.

DKIM keys for bk.ru

1 DKIM selector found for bk.ru (mail). Each is a public key in DNS that receivers use to check the signature on messages from bk.ru; together with SPF it is what a DMARC policy enforces.

What the check reads

DKIM keys live in DNS at <selector>._domainkey.bk.ru, one TXT record per selector, and the selector is chosen by whoever signs the mail. This checker asks for the selectors the large providers and sending platforms use by default (google, selector1 and selector2 for Microsoft 365, k1, s1, fm1 and about thirty more), so a key found here is a real key, and a key not found here may simply sit under a name the list does not know.

How it fits with SPF and DMARC

bk.ru enforces DMARC at p=reject, so messages that fail alignment are dropped by receivers rather than delivered or quarantined. That is the end state most domains work towards. bk.ru publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record has no explicit all mechanism, so receivers treat unlisted servers as neutral.

Transport security for bk.ru

bk.ru publishes an MTA-STS policy record at _mta-sts.bk.ru. MTA-STS tells sending servers to insist on a valid TLS certificate when they deliver to this domain, which closes the downgrade attack that opportunistic STARTTLS leaves open. bk.ru publishes a TLS-RPT record at _smtp._tls.bk.ru. TLS-RPT is where senders report the connections that failed to negotiate TLS, so the domain owner sees the failures MTA-STS causes.

Brand indicators for bk.ru

bk.ru publishes no a BIMI record record at default._bimi.bk.ru. BIMI is optional and mostly cosmetic; it only becomes possible once DMARC enforces quarantine or reject.

SPF details for bk.ru

bk.ru publishes SPF. The policy's all qualifier is ~all (soft fail: unlisted servers are marked suspicious but usually delivered). Evaluating it takes 1 DNS lookup, within the ten RFC 7208 allows.

DMARC details for bk.ru

bk.ru enforces DMARC at p=reject, so messages that fail alignment are dropped by receivers rather than delivered or quarantined. That is the end state most domains work towards. The policy applies to all of the domain's mail (pct=100). Aggregate reports are collected (rua= is set), so the owner sees who sends as the domain.

Is bk.ru disposable?

bk.ru is a consumer email service rather than a company domain: real people, personal accounts, and no way to infer an employer from the address.

About the domain

Its mail is handled by an unrecognised provider.

How Spaw treats addresses at bk.ru

For bk.ru, verification runs the whole pipeline: syntax, live MX, the open lists, and then the SMTP handshake with the mail host, with no message ever transmitted. Each verdict carries a machine-readable reason.

Common questions about bk.ru

Does bk.ru accept mail?

bk.ru accepts mail through a third-party mail host.

Does bk.ru publish SPF and DMARC?

bk.ru publishes SPF ending in ~all and a DMARC policy of reject.

Is bk.ru a disposable, relay or free-provider domain?

bk.ru is a free mailbox provider, so an address there is a consumer inbox rather than a company's.

Does bk.ru publish DKIM, MTA-STS, TLS-RPT or BIMI?

bk.ru publishes MTA-STS, publishes TLS-RPT and does not publish BIMI. DKIM keys were found under the selector mail.

Where does this report come from?

Live DNS, the open disposable, role and free-provider lists, the registry's RDAP record and the threat blocklists the IP product installs, read on 2026-10-08 and cached for a week. Nothing here says anything about a person; it describes the domain's mail setup on that day.

Check another domain

• Email checker
• MX record lookup
• SPF & DMARC checker
• Disposable email domain checker
• DKIM checker
• MTA-STS, TLS-RPT and BIMI checker
• The same answer over the API: GET /api/v1/email/domain/bk.ru