BIMI is a small system with several owners. Keep authentication healthy, assets available, certificates current, and change records clear.
- Assign an owner to every dependency.
- A logo change may need a new certificate.
- Re-test after changes to email, DNS, hosting, or branding.
Make ownership visible
Record who owns DNS, email authentication, asset hosting, certificate procurement, and brand approval. Include a backup contact and the renewal process. A deployment should not depend on one person remembering where a file lives.
Keep the domain list, selectors, public URLs, certificate expiry dates, and change history in a shared operational document.
Monitor the parts that can change
- Authentication and DMARC reports for new or failing senders.
- Availability and TLS validity of public asset URLs.
- Mark certificate expiry and renewal progress.
- DNS changes that alter selectors or published URLs.
- Representative mailbox display after significant changes.
Set monitoring intervals that fit your organisation’s existing operations. Escalate an actual failure with enough detail for the responsible owner to act.
Treat renewal as a project with a deadline
Start with the issuer’s current requirements and lead times. Verify that the organisation, domains, and artwork are still accurate. Prepare replacement files and test access before changing the live reference.
Document the new expiry date and check representative messages after the update. Renewing a website TLS certificate does not renew a BIMI mark certificate.
Coordinate a rebrand before replacing files
A mark certificate is tied to specific logo evidence. Discuss new artwork with the issuer, prepare and validate the replacement SVG, obtain the necessary certificate, and host both new assets before updating DNS.
Keep the current valid deployment available while the replacement is prepared where possible. Allow for receiver caches when evaluating the visual change; do not repeatedly overwrite files to force an instant refresh.
A short change review
For every material update, ask: what is changing, which domains are affected, who owns the change, how will we verify it, and what is the recovery path? Attach before-and-after values and test evidence.
Common triggers include moving a website, switching DNS hosts, adding a marketing platform, acquiring a domain, and updating brand artwork.
Go to the source
Provider policies and specifications can change. These primary sources informed this guide, reviewed on 1 November 2026.