adriver.ru

adriver.ru · Last checked 2026-10-04 02:11 UTC

adriver.ru

Good, with 2 things to fix

adriver.ru scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and no DMARC aggregate report address.

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

3 passed2 need attention0 failing3 for information
Fix this firstThe change with the biggest effect

Set up a DMARC report address

Without a rua address nobody receives aggregate reports, so you cannot see who sends as adriver.ru or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.

Applies to: _dmarc.adriver.ru

  1. Get an address that collects DMARC aggregate reports: add adriver.ru to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.adriver.ru and add rua=mailto:<that address>, keeping every other tag (p=quarantine) as it is. 3. A report service on another domain must authorize adriver.ru; most publish that record for you.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?No issues foundPass

Nothing to report.

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
  • Warning: DKIM key shorter than 2048 bits

    default (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.

  • Pass: DKIM key published

    adriver.ru publishes a DKIM key under default.

DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention
  • Warning: No DMARC aggregate report address

    Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.

    How to fix this
  • Info: DMARC policy is quarantine; consider reject

    Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.

    How to fix this
  • Info: DMARC uses strict alignment

    With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.

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.adriver.ru. 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.adriver.ru. 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.adriver.ru. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing. There is no report address yet: set one up first (see the DMARC reporting fix) so you can confirm your legitimate mail passes before enforcing.

TypeTXT
Name / Host
_dmarc.adriver.ru

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; adkim=s; aspf=s
Replaces
v=DMARC1; p=quarantine; adkim=s; aspf=s

Publish the MTA-STS recordTXT

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

TypeTXT
Name / Host
_mta-sts.adriver.ru

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

Value
v=STSv1; id=202610040211

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.adriver.ru. 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.adriver.ru/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: mx.adriver.ru
mx: mx4.adriver.ru
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to adriver.ru, 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.adriver.ru

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@adriver.ru, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.adriver.ru 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.adriver.ru

  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://adriver.ru/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.adriver.ru with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.