BIMI can let participating mailbox providers display a brand logo next to authenticated mail, but it is not the first email-authentication step. Treat it as a later-stage signal after SPF, DKIM, DMARC alignment, reporting, and enforcement are already under control.
Run the public DNS scan before publishing a BIMI record. The scan can find BIMI and DMARC signals, but provider display still depends on external eligibility rules.
Check the public sender-auth records mailbox providers expect.
Keep one URL with evidence, owner steps, and decisions.
Add human review, provider context, and verification steps.
Review DMARC policy strength before a high-volume send.
Overall sender readiness
Needs attention
Sample output: one warning and one fail mean this domain is not campaign-ready yet.
The scan becomes a focused work surface: evidence, owner action, verification, and the paid context a public lookup cannot infer.
Google says BIMI requires third-party certification for the domain and logo through a Verified Mark Certificate or Common Mark Certificate. Google also requires the domain's DMARC policy to be p=quarantine or p=reject, with pct=100.
The BIMI Group implementation guide uses the same enforcement posture: DMARC should be at enforcement on the organizational domain and subdomains, and policies with pct below 100 percent are not accepted.
The BIMI TXT record is normally published at default._bimi.example.com. Do not copy a sample record until your logo, certificate path, HTTPS hosting, and DMARC enforcement are ready:
v=BIMI1; l=https://example.com/brand/bimi.svg; a=https://example.com/brand/vmc.pem
Some certificate-backed flows use the PEM file as the primary asset. Follow the current mailbox-provider and certificate-authority instructions for the exact l and a values.
Yahoo says it considers a BIMI record, a valid SVG logo, DMARC quarantine or reject, bulk-mail context, and sufficient reputation and engagement. Google has its own VMC or CMC path. That means the DNS record can be technically present while a logo still does not appear for a given recipient or mailbox product.
Keep the promise narrow: BIMI setup is a brand-authentication readiness project, not guaranteed inbox placement, not a spam-folder bypass, and not proof that every recipient mailbox will show a logo.
No for the practical setup most senders want. Google and the BIMI Group call for DMARC enforcement, and Google requires p=quarantine or p=reject with pct=100.
No. Mailbox providers apply their own eligibility, certificate, reputation, engagement, and product-support rules. BIMI is a readiness signal, not a display guarantee.
Some providers may show self-asserted BIMI in limited cases, but Gmail and other clients require or expect certificate-backed PEM files for supported display paths.
SenderReady readiness audits check public BIMI, DMARC, SPF, DKIM, and provider-readiness signals so your DNS owner can review the next step. They are diagnostics, not logo display guarantees.