Poor, with 7 things to fix

stbid.ru scored 50/100 (grade D). The main issues are no SPF record and no DKIM key found for the common selectors, plus 7 more.

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

6 need attention1 failing1 for information

Diagnosis notes

Warning: DNS lookup budget exhausted
This diagnosis stopped sending DNS queries after 8000 ms. Checks that needed more lookups report their remaining results as unknown; the domain's records may be unusually large or slow to answer.

Fix this firstThe change with the biggest effect

Publish an SPF record

No sending service was detected, so this record says no server may send as stbid.ru. If you do send mail, add your provider's include before publishing.

TypeTXT

Name / Host

stbid.ru

Some DNS providers want “@” here instead of the full domain.

Value

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
stbid.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
stbid.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 stbid.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 stbid.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 stbid.ru.
Warning: Some DKIM lookups failed
8 of 47 selector lookups under stbid.ru returned TIMEOUT, so whether those selectors hold a key is unknown. Try again later; if it persists, check the domain's nameservers.

DMARCWhat happens to fakes?Could not look up the DMARC recordNeeds attention

Warning: Could not look up the DMARC record
The DNS query for _dmarc.stbid.ru returned TIMEOUT. The DMARC result is unknown; try again later.

AlignmentDoes it match your From?Alignment could not be fully assessedInfo

Info: Alignment could not be fully assessed
Alignment could not be judged because of the DMARC lookup failed. The affected verdicts are reported as unknown rather than guessed.

BIMICan inboxes show your logo?Could not look up the BIMI recordNeeds attention

Warning: Could not look up the BIMI record
The TXT query for default._bimi.stbid.ru returned TIMEOUT, so BIMI status is unknown. Try again later.

MTA-STSIs mail to you encrypted?Could not look up the MTA-STS recordNeeds attention

Warning: Could not look up the MTA-STS record
The TXT query for _mta-sts.stbid.ru returned TIMEOUT, so MTA-STS status is unknown. Try again later.

TLS-RPTWill you hear about failures?Could not look up the TLS-RPT recordNeeds attention

Warning: Could not look up the TLS-RPT record
The TXT query for _smtp._tls.stbid.ru returned TIMEOUT, so TLS-RPT status is unknown. Try again later.