avito.ru
Good, with 3 things to fix
avito.ru scored 76/100 (grade B). The main issues are BIMI logo is unreachable and DKIM key shorter than 2048 bits, plus 1 more. Detected senders: Microsoft 365 and Salesforce.
Checked 2026-10-04 02:13 UTC · fresh check
Strengthen the DMARC policy
Rejects mail that fails DMARC, the strongest protection against spoofing. Changes: Subdomains move one step, from sp=none to sp=quarantine.
_dmarc.avito.ru
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=reject; sp=quarantine; rua=mailto:abuse@avito.ru; adkim=r; aspf=r
v=DMARC1; p=reject; sp=none; rua=mailto:abuse@avito.ru
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Find the existing TXT record with that name and replace its value.
- 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 avito.ru goes to exchange.avito.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?No issues foundPass
Nothing to report.
DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
- Warning: DKIM key shorter than 2048 bits
selector1 (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
avito.ru publishes a DKIM key under selector1, selector2, mail.
DMARCWhat happens to fakes?Subdomain policy is weaker than the domain policyNeeds attention
- Warning: Subdomain policy is weaker than the domain policy
sp=none is weaker than p=reject, so attackers can spoof any subdomain of avito.ru (for example billing.avito.ru) even though the main domain is protected.
How to fix this
AlignmentDoes it match your From?No issues foundPass
Nothing to report.
BIMICan inboxes show your logo?BIMI logo is unreachableNeeds attention
- Warning: BIMI logo is unreachable
The SVG at https://avito.ru/bimi-logo.svg could not be fetched (HTTP 301). Mailbox providers will not show the logo.
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.avito.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.avito.ru. 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 avito.ru publishes an MTA-STS policy at https://mta-sts.avito.ru/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.avito.ru
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040213
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.avito.ru. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.avito.ru/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: exchange.avito.ru max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to avito.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.avito.ru
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@avito.ru, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.avito.ru with the value v=TLSRPTv1; rua=mailto:<that address>.