mhverifier.ru
At risk, with 4 things to fix
mhverifier.ru scored 20/100 (grade F). The main issues are no DMARC record and no SPF record, plus 2 more.
Checked 2026-10-04 02:16 UTC · fresh check
Publish an SPF record
No sending service was detected, so this record says no server may send as mhverifier.ru. If you do send mail, add your provider's include before publishing.
mhverifier.ru
Some DNS providers want “@” here instead of the full domain.
v=spf1 -all
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.
- Add a new TXT record with the name and value above.
- 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?Mail relies on implicit A recordNeeds attention
- Warning: Mail relies on implicit A record
mhverifier.ru has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.
SPFWho may send as you?No SPF recordFailing
- Fail: No SPF record
mhverifier.ru publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as mhverifier.ru.
How to fix this
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 mhverifier.ru 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 mhverifier.ru.
DMARCWhat happens to fakes?No DMARC recordFailing
- Fail: No DMARC record
There is no v=DMARC1 TXT record at _dmarc.mhverifier.ru. 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.mhverifier.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.mhverifier.ru. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.mhverifier.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 a DMARC recordTXT
Starts DMARC in monitoring mode (p=none), so you can see who sends as mhverifier.ru before enforcing a policy. Move to quarantine once the reports show only your own services.
_dmarc.mhverifier.ru
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=none; adkim=r; aspf=r
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to mhverifier.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.mhverifier.ru
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@mhverifier.ru, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.mhverifier.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.mhverifier.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://mhverifier.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.mhverifier.ru with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.