Before spending budget on a certificate, decide which provider, mail client, and visual treatment you need. BIMI prerequisites are not a single checkbox for your domain: you can have a viable Gmail plan while Apple Mail remains unresolved. Keep three conclusions separate: technical validity, provider acceptance, and whether the logo actually appears in an inbox. A valid configuration never forces a receiver to render your mark, because the specification leaves display to the receiver’s discretion. The guide chapter BIMI: showing your logo in the inbox covers the broader context.
Authentication comes first: inventory, then the DMARC policy BIMI needs
Start by auditing your legitimate sending streams. Catalog every service and fix authentication failures before tightening DMARC: hold off on any certificate purchase or deployment commitment until that evidence exists. A DMARC pass confirms an aligned identifier authenticated; it does not prove your business authorized the stream, that every service is covered, or that messages reached the inbox (DMARC readiness and evidence limits, RFC 9989).
The conservative BIMI baseline requires authenticated, aligned email with DMARC enforced at quarantine or reject across both the Author Domain (the domain in the visible From address) and the Organizational Domain. Check your subdomain policy: an explicit sp=none breaks this baseline. These criteria come from an Internet-Draft, and mailbox providers add their own conditions while keeping discretion, as outlined in the draft’s authentication baseline.
Quarantine can satisfy that baseline, so don’t move to reject solely to earn a logo. RFC 9989 requires valid DKIM for any domain on reject, forbids relying on SPF alone, and says that domains whose users might post to Internet mailing lists should not publish reject (reject interoperability guidance).
Provider requirements were verified on 15 September 2026. On that date, Google’s BIMI documentation still called for pct=100, even though RFC 9989 removes pct from modern DMARC syntax. A mismatch between two documents does not establish how a receiver processes the newer standard, so adding or removing that tag, or substituting t, is not evidence of BIMI eligibility. Compare the two references directly: Google’s published BIMI requirements and the DMARC specification changes in RFC 9989.
Which certificate path fits your target
Gmail: Plan for an issued Verified Mark Certificate (VMC) or Common Mark Certificate (CMC); a standalone SVG is not enough. A CMC can support the brand avatar without Gmail’s verified checkmark. If you need that checkmark, pursue a qualifying VMC path. Google’s checkmark covers Gmail web, Android, and iOS apps; that scope does not carry over to Apple Mail or replace Apple’s separate validation rules. Baseline authentication, artwork, hosting, certificate, and DNS requirements all apply. Google’s announcement explains the certificate and checkmark distinction.
Yahoo: Evaluate four criteria together: a BIMI record pointing to compliant SVG artwork, DMARC at quarantine or reject, bulk email rather than personal messages, and sufficient reputation and engagement for the sending address. Yahoo does not require a VMC today, though submitting one feeds into its assessment. Yahoo publishes no numerical reputation thresholds and no explicit CMC rules. Documented display locations include Yahoo and AOL mobile message lists, mobile message views, and desktop message views (Yahoo’s BIMI criteria).
Apple Mail: Identify the receiving email service behind the user’s account first, because validation takes place on the mail server rather than inside the mail client. That service must be listed by the BIMI Group, verified by Apple, check message and domain compliance, inspect a trusted BIMI Evidence Document, and add the required headers. Apple names VMCs and other Evidence Documents without establishing universal acceptance of Gmail-eligible CMCs (Apple’s receiving-service requirements).
Apple supports BIMI starting on iOS 16, iPadOS 16, macOS Ventura 13, and through iCloud.com, provided sender and server requirements pass. Using a modern Apple Mail client will not help if the recipient’s underlying email provider does not support BIMI (Apple’s BIMI support scope).
Settle the exact artwork before you apply
Certificate authorities validate the exact vector graphic you submit. VMC requirements include registered-mark and government-mark routes, and Google describes recognized registered trademarks (Google’s published BIMI requirements). Confirm the specific issuer or provider path, including the applicant, domain and rights checks described in the VMC mark verification guidelines.
If you choose the CMC prior-use route, the matching mark must appear on your currently controlled website and present in an accepted public archive of the same domain at least 12 months before verification. Current rules specifically name archive.org: issuers require verifiable proof (such as an archive.org snapshot dating back at least 12 months), not informal assertions (CMC prior-use evidence).
Version 1.8 also includes modified-registered and provisional-mark CMC routes with separate conditions. Check with the issuer which track applies; a newly drawn logo does not qualify automatically, and issuance remains subject to validation (other CMC routes).
Format artwork to the SVG Tiny PS profile. For Gmail, width and height must each be at least 96 pixels, defined in absolute units. Centering the artwork in a square, a solid background, a file no larger than 32 KB, and a desc element are recommendations rather than requirements. Name someone to host the PEM file (certificate chain and logo) at a public HTTPS URL, and someone to own the DNS TXT record that points to it. Both responsibilities follow from Google’s published BIMI requirements.
Finally, verify that your target mailbox providers accept the issuer and the certificate. Being listed in the BIMI Group directory does not constitute universal provider acceptance (certificate acceptance by provider).
A worked decision: established logo or recent redesign?
This is a synthetic planning example, not a certificate application or a display test. A newsletter sends from news@example.com, where example.com acts as both Author Domain and Organizational Domain. Assume sending streams are inventoried, authentication failures resolved, aligned DKIM and DMARC passes documented, and quarantine safely selected as the policy baseline. The team can format SVG files and provide public HTTPS hosting, though neither asset has been published or tested yet.
Candidate A is an unregistered mark matching both the current controlled website and an allowed same-domain archive 18 months before prospective verification. Candidate B is a redesign launched 2 months ago, lacking trademark registration, government status, or any modified or provisional foundation. Neither holds a certificate.
| Decision | What the evidence supports | What keeps the decision on hold |
|---|---|---|
| Artwork | Keep A for a CMC prior-use application. B’s 2 months fail that evidence test. | Hold A too if the archived mark or domain does not match. Applicant, rights and issuer validation remain outstanding. |
| Gmail avatar; checkmark optional | Plan A with CMC, subject to Google’s remaining requirements. | An accepted certificate must still be issued. If a checkmark becomes mandatory, reconsider a qualifying VMC path. |
| Yahoo bulk newsletter | Assess the SVG/BIMI reference and quarantine together with Yahoo’s reputation and engagement criteria. No VMC is required. | The sending address’s qualification remains unconfirmed; buying a CMC for Gmail does not resolve it. |
| Apple Mail; receiving service unknown | Record the target as unresolved. | Identify the service and establish its Apple-verified evidence and header path. A’s proposed CMC alone cannot clear this hold. |
If the shared authentication assumptions fail, stop the implementation commitment and revisit enforcement readiness. Otherwise keep A as the application candidate and document each provider’s outstanding evidence. No row establishes issuance or display.
Write down the target providers, visual treatment, exact artwork, certificate route, evidence owners, and any blocking condition. When you have evidence for each of these, move to the BIMI implementation procedure. If authentication is still unready, use the DMARC enforcement decision first. For broader rollout strategy, see How do I roll out DMARC without breaking my email?.
Frequently asked questions
Does BIMI require DMARC at reject, or is quarantine enough?
The conservative baseline is authenticated, aligned mail with DMARC at quarantine or reject on both the Author Domain and the Organizational Domain, and an explicit sp=none subdomain policy fails it. Quarantine can satisfy that baseline, so don’t move to reject only to earn a logo.
Does Yahoo require a VMC for BIMI?
Yahoo currently requires no VMC, although a supplied VMC contributes to its assessment. Its guidance gives no numeric qualification thresholds and does not establish CMC validation.
Can a CMC get the Gmail verified checkmark?
A CMC can support the brand avatar without Gmail’s verified checkmark. If that checkmark is required for you, investigate a qualifying VMC path.
Does a valid BIMI configuration make the receiver show the logo?
A valid BIMI configuration does not compel a receiver to show anything, because the draft leaves display to the receiver’s discretion. Keep technical validity, provider acceptance and the logo actually appearing as three separate conclusions.
How long must a logo have been in use for the CMC prior-use route?
At least 12 months. Under the CMC prior-use route, your exact matching logo must appear on your currently controlled website and in an approved public web archive of the same domain at least 12 months before verification. A simple internal assertion of age is not sufficient.


