Choose a certificate category for a specific outcome
A Common Mark Certificate can make a certificate-backed BIMI logo possible when the organization does not have the kind of registered mark used for a conventional VMC application. It is not a certificate with no verification, and it is not interchangeable with a VMC for every receiver feature. Begin by stating whether the business needs a logo, a particular verified indicator, or both, and which receiving services must support that outcome.
This article uses primary issuer and receiver pages retrieved on 8 November 2026. It is a preparation and comparison guide, not legal advice or an eligibility decision. BIMI remains draft work rather than an established IETF Standards Track RFC. A documentary comparison cannot establish the rights, prior use, domain control or successful display of a real applicant, so those evidence requirements remain separate and open.
Understand the issuer's actual eligibility paths
DigiCert's CMC documentation, modified 30 October 2026, identifies Prior Use Mark and Modified Registered Trademark options. For its prior-use path, it describes at least 12 months of logo use before mark verification on a domain the applicant controls, with historical use verifiable through Archive.org. This is materially more specific than “the business has existed for a year.” The age of an organization or domain does not by itself establish use of the exact logo. DigiCert CMC eligibility
The modified-mark category should not be interpreted as permission to alter any registered logo and self-declare eligibility. Ask the issuer what relationship, permitted modification and supporting rights it needs for the candidate. Treat its evaluation as a distinct decision. The page's simplified “similar to your registered trademark” wording is an introduction to an issuer process, not a complete rule that an engineering team can adjudicate independently.
Build a prior-use record without manufacturing certainty
Prepare a timeline linking the exact candidate mark to dated public use and domain ownership context. Record historical URLs, capture dates, visible versions and gaps. Distinguish a source showing a company name from one showing the actual graphic. If older pages contain a different badge, note the difference instead of counting them automatically toward the new mark's history. Ask the issuer whether the available evidence meets its current process.
Do not backdate a website, create misleading archive evidence or describe a recently redesigned mark as continuously unchanged. If the record is incomplete, the useful outcome is an unresolved eligibility question with a named owner. A CMC may be inappropriate for a brand-new launch under the chosen prior-use route. Other categories or a later application may need consideration, but the issuer must confirm the applicable path rather than the project assuming an exception.
CMC still involves identity and technical validation
DigiCert describes organization validation and additional applicant identity checks for CMC, including documentary or live validation routes and interaction with its validation team. It also requires suitable SVG-P/S artwork and DMARC readiness. These requirements mean CMC is not simply a fee for uploading an arbitrary picture. Keep the secure identity-verification channel and authorized representative outside the ordinary design collaboration folder. DigiCert validation process
Use one approved asset version throughout the preparation record. If the designer changes the mark after the historical evidence is assembled, reconsider whether that evidence still concerns the same candidate. If the issuer returns a certificate package, preserve the package and its relationship to the approved SVG. A later web replacement should not silently sever the link between the visible asset and the mark that was verified.
Compare issuer eligibility with receiver behavior
Google's setup documentation, updated 26 October 2026, supports either VMC or CMC for its certificate-backed BIMI workflow. It specifically associates the Gmail checkmark with VMC-verified senders. The practical distinction is therefore not simply “BIMI supported” versus “unsupported”: a CMC can fit the documented logo path without providing the same verified checkmark outcome. Google certificate requirements
Google also documents a PEM workflow and says a standalone SVG-only deployment is not supported in Gmail. The source requires DMARC enforcement values for its BIMI setup and specifies its SVG dimension rules. Certificate eligibility therefore does not remove authentication, hosting or asset dependencies. Consult each other receiver's current primary documentation before asserting equivalent support. An issuer's general description of inbox visibility is not proof of every mailbox's implementation.
The proposed comparison should have separate columns for issuer category, required rights evidence, target receiver, supported logo experience, verified indicator and deployment dependencies. Keep unsupported receiver rows unknown. Record both the retrieval date and the page's own update date when available, since a current fetch can still contain an older claim. Avoid reproducing an issuer's historical mobile-feature note as a current receiver-wide guarantee.
Original CMC decision worksheet
This worksheet is an original planning aid, not a completed application or a determination of trademark rights. Each row needs an owner, evidence reference, date and unresolved question.
- Intended outcome: logo, verified indicator and named target receiver or client.
- Category: issuer-confirmed prior-use or modified-registered-mark route.
- Candidate identity: approved SVG digest and relationship to historical versions.
- Rights context: legal owner, applicant authority and any licenses or organizational transfers.
- Prior use: dated observations of the exact logo on an applicant-controlled domain and evidence gaps.
- Issuer verification: requested organization and representative checks through an approved secure channel.
- Receiver comparison: current certificate-category support and deployment prerequisites.
- Renewal continuity: responsible owner, backup contact, review date and rebrand or ownership-change procedure.
Use the worksheet to make a go, wait or investigate decision before procurement. A go decision should state the assumptions it depends on and who confirmed them. A wait decision can be appropriate when a new mark lacks sufficient history. An investigate decision should identify a specific issuer question rather than invite a speculative application with unresolved rights and technical requirements.
Fictional example: an old company with a new logo
Fictional Orchard Signal has operated for eight years but introduced a new symbol two months ago. Its marketing team assumes the company's age establishes the prior-use condition. The proposed evidence review instead distinguishes the old wordmark from the new symbol and asks which asset the application would cover. Historical pages showing the old mark do not automatically prove a year of use for the redesigned candidate.
The team would ask the issuer to assess the available category and evidence before committing funds. If the desired outcome includes Gmail's VMC-linked checkmark, it would also revisit whether a CMC meets the business requirement at all. No historical archive was queried for Orchard Signal, no application was submitted, and no receiver display was observed. The example illustrates a decision conflict, not evidence of eligibility or rejection.
Keep renewal ownership attached to the rights record
A certificate-backed logo needs continuity beyond the initial application. Assign responsibility for issuer notices, rights changes, domain ownership, hosting and replacement artwork. Review a rebrand or acquisition before changing the public asset. Do not invent a universal renewal interval or assume payment alone preserves eligibility; use the actual certificate dates and issuer's current instructions for the applicant.
The catalogue requires a current issuer-and-receiver comparison with brand-rights evidence and renewal ownership. This manuscript provides documented comparison points and a proposed worksheet, but no real applicant's rights evidence or assigned renewal owner. Original evidence, human SME, source applicability, production routes, visual accessibility and owner release all remain open. The document is a draft guide, not a publication-ready or operationally verified CMC approval.