ShipReady rates this low. Worth fixing. Small individually, and they accumulate.

Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.

Can I check my own site?

Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.

lowmissing-bimi

Eligible for BIMI but not configured

Why it matters

`{org_domain}` already enforces DMARC (p={dmarc_policy}), which is the hard prerequisite for BIMI — publishing a BIMI record would display your logo beside your messages in Gmail, Apple Mail and Yahoo. This is a trust and recognition improvement rather than a security fix, and the verified-mark certificate some providers require is a paid annual product, so treat it as optional polish.

How ShipReady detects it

Email-authentication DNS records (DMARC / SPF). Almost every AI-built SaaS sends transactional email — password resets, magic links, receipts — through Resend, SendGrid or Postmark. Setting that up gets the mail delivered; it does not stop anyone else sending mail that claims to come from the same domain. Without a DMARC policy, a receiving server has no instruction to reject a forgery, so an attacker can send "reset your password" from the product's own domain and the message will land in the inbox looking authentic. This is the only check in the scanner that reads DNS rather than HTTP. It is also the most deterministic: a record either exists or it does not, so there is no heuristic and no false-positive surface. The one place judgement is required is deciding WHICH domain to ask about — see _organizational_domain.

Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.1.0.

How to fix it

This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.

The domain {domain} already enforces DMARC, which is the difficult prerequisite for BIMI. To display your logo beside your messages in Gmail, Apple Mail and Yahoo, publish your logo as an SVG Tiny P/S file over HTTPS and add a TXT record at default._bimi.{domain} of the form "v=BIMI1; l=https://{domain}/logo.svg; a=". Gmail and Apple Mail additionally require a Verified Mark Certificate, which is a paid annual product from a certificate authority — this is optional brand polish, not a security fix, so skip it if the cost is not worth the recognition.

Frequently asked questions

What does "Eligible for BIMI but not configured" mean?: `{org_domain}` already enforces DMARC (p={dmarc_policy}), which is the hard prerequisite for BIMI — publishing a BIMI record would display your logo beside your messages in Gmail, Apple Mail and Yahoo.
How serious is it?: ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
How do I fix it?: Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
Can I check my own site?: Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.

Related checks

Does your site have this?

ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.

Scan my site