Logo URL Scheme is Not HTTPS (Missing VMC in Record)
“Logo URL scheme is not HTTPS (missing VMC in record)” means the checker found a logo URI that does not use HTTPS. The BIMI draft requires the l= URI to use HTTPS; its a= evidence tag is optional at t
The exact error
Logo URL scheme is not HTTPS (missing VMC in record)What Does “Logo URL Scheme is Not HTTPS (Missing VMC in Record)” Mean?
“Logo URL scheme is not HTTPS (missing VMC in record)” means the checker found a logo URI that does not use HTTPS. The BIMI draft requires the l= URI to use HTTPS; its a= evidence tag is optional at the protocol level. Brand Indicators for Message Identification draft 14 documents the controlling requirement or boundary.
Indicator discovery fails until the logo location uses HTTPS. Whether certificate evidence is also required depends on the receiving provider.
Why Does Logo URL Scheme is Not HTTPS (Missing VMC in Record) Appear?
Logo URL scheme is not HTTPS (missing VMC in record) appears when the l= value uses a scheme such as HTTP; the pinned summary associates this condition with missing VMC evidence but does not establish that missing evidence is a necessary trigger. The exact diagnostic should be read at the scope of BIMI record and logo URI rather than as proof that every BIMI layer failed.
How Do You Fix Logo URL Scheme is Not HTTPS (Missing VMC in Record)?
To fix Logo URL scheme is not HTTPS (missing VMC in record), replace the l= value with a publicly retrievable HTTPS URI and evaluate certificate evidence separately for each target mailbox provider.
Changing the URI scheme does not prove that the asset is retrievable or that a provider will display it.
What Should You Verify After Fixing Logo URL Scheme is Not HTTPS (Missing VMC in Record)?
After fixing Logo URL scheme is not HTTPS (missing VMC in record), test the exact HTTPS logo URL and then validate the SVG, DMARC eligibility, and any provider evidence requirement. Verification should use the exact public selector, URL, record, or file evaluated by the receiver.
The correction clears only this condition; it does not guarantee that a receiver will display an indicator.
Key Takeaways
- The affected object is BIMI record and logo URI.
- The direct correction is to replace the l= value with a publicly retrievable HTTPS URI and evaluate certificate evidence separately for each target mailbox provider.
- Changing the URI scheme does not prove that the asset is retrievable or that a provider will display it.




