No BIMI record published
What this check looks for
You have not published a BIMI record, so your logo does not appear next to your messages in the inboxes that support it. This is optional and costs you no points.
Why it matters
BIMI is a visible reward for having your email authentication in order rather than a security control in itself. It is worth doing once DMARC is enforcing.
When the check passes, your report says: “A BIMI record is published for the domain”.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- Email authentication
- Module
- Email bimi
- Fix owned by
- dns host
- In the ruleset since
- 2026.09
How to fix it
Publish a BIMI record once DMARC is at quarantine or reject.
It puts your logo in the inbox and is a visible signal that your authentication is complete.
Get DMARC to
p=quarantineorp=rejectfirst, with nopcttag and nosp=none.Prepare a square SVG Tiny Portable/Secure logo and host it over HTTPS.
Publish
v=BIMI1; l=<logo url>atdefault._bimi.‹domain›.Obtain a Verified Mark Certificate if you want the logo shown by Gmail and Apple Mail.
How to confirm it worked
dig +short TXT default._bimi.‹domain› — expect a v=BIMI1 record
default._bimi.{{domain}}. 3600 IN TXT "v=BIMI1; l={{logoUrl}}; a="A named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.
Technical detail
No TXT record was found at default._bimi.‹domain›. BIMI requires an enforcing DMARC policy first; publishing the record before that has no effect. Gmail, Yahoo, Fastmail and Apple Mail additionally require a Verified Mark Certificate before the logo is displayed.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.