The client-visible payoff for doing email security right
BIMI puts the client's logo next to their email in Gmail, Yahoo, and Apple Mail — but only after DMARC reaches enforcement. That makes it the perfect capstone to sell: invisible security work, made visible.
Readiness before records
BIMI silently fails unless DMARC is at p=quarantine or p=reject with full coverage and no weakened subdomain policy. Trustliant checks the prerequisites first and turns 'you qualify for BIMI now' into an automatic opportunity finding the moment a domain reaches enforcement.
VMC or CMC? Decided by facts
Verified Mark Certificates need a registered trademark and light up Gmail's blue check. Common Mark Certificates (2024+) cover logos in use 12+ months with no registration — logo display without the checkmark. Trustliant explains the trade-off per client, with current issuer options (DigiCert, GlobalSign, SSL.com).
Beyond the record
Record syntax, HTTPS logo URLs, SVG format expectations, and certificate presence are validated today; full SVG Tiny PS profile validation and Apple Business Connect guidance are on the roadmap — the goal is 'logo everywhere,' whatever each mailbox provider requires.
For your technicians
Record parsing with per-tag errors, DMARC prerequisite tracing, and the exact default._bimi record to publish once assets are ready.
For your clients
“Your logo, verified, in your customers' inboxes — visible proof your email is authentic, powered by security work already done.”