drom.ru
Excellent, with 1 thing to fix
drom.ru scored 92/100 (grade A). The main issue is DKIM key shorter than 2048 bits.
Checked 2026-10-04 02:08 UTC · fresh check
All checks
MXCan servers find your inbox?Only one MX hostInfo
- Info: Only one MX host
All mail for drom.ru goes to mx.drom.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?DKIM key shorter than 2048 bitsNeeds attention
- Warning: DKIM key shorter than 2048 bits
smtp (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
drom.ru publishes a DKIM key under smtp.
DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
- 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
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.drom.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.drom.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.drom.ru. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
How to fix it
Strengthen the DMARC policyTXT
Rejects mail that fails DMARC, the strongest protection against spoofing.
_dmarc.drom.ru
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=reject; rua=mailto:dmarc@drom.ru; adkim=r; aspf=r
v=DMARC1; p=quarantine; rua=mailto:dmarc@drom.ru
Publish the MTA-STS recordTXT
Tells sending servers that drom.ru publishes an MTA-STS policy at https://mta-sts.drom.ru/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.drom.ru
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040208
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.drom.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.drom.ru/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: mx.drom.ru max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to drom.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.drom.ru
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@drom.ru, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.drom.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.drom.ru
- 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://drom.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.drom.ru with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.