Suped

What Happens to Your BIMI Logo and Blue Checkmark When Your VMC Expires?

Published 27 Dec 2025
Updated 17 Oct 2026
12 min read
Summarize with
Expired Verified Mark Certificate (VMC) beside a BIMI logo and faded Gmail blue checkmark.
Updated on 17 Oct 2026: We added VMC and hosting TLS expiry checks and clarified Gmail's certificate renewal requirements.
When your Verified Mark Certificate (VMC) expires, your BIMI setup no longer has valid certificate evidence. Gmail stops showing the blue checkmark after it revalidates the certificate. Gmail also requires a valid VMC or CMC for its BIMI logo display, so an expired VMC does not leave a Gmail logo-only path by itself. At providers that accept self-asserted BIMI, logo display depends on the provider's certificate policy and other eligibility checks.
The practical answer is that an expired VMC provides no valid verified mark. It does not become partly trusted, a CMC, or a self-asserted record. Providers do not all remove cached treatment at the same second, but the VMC path fails once a receiver checks the certificate date and finds it outside the valid period. There is no VMC validity grace period after the notAfter expiry timestamp.
Treat this as a certificate lifecycle issue first and a BIMI DNS issue second. The BIMI TXT record can look correct while the certificate behind the a= tag is expired. A format-only BIMI check catches syntax, but it does not prove that the VMC is current, unrevoked, and trusted.
Short answer
An expired VMC makes the certified BIMI path fail. Gmail's blue checkmark disappears after Gmail revalidates the expired certificate. A valid CMC can provide Gmail logo-only display, while self-asserted logo display remains limited to providers that accept it.

What mailbox providers check before showing BIMI

A receiver does not simply read the BIMI record and trust the logo. It decides whether the message qualifies, whether the visible From domain passes DMARC alignment, whether DMARC is fully enforced, whether the logo meets SVG Tiny Portable/Secure (SVG Tiny PS) requirements, and whether any certificate evidence is valid. The BIMI Group VMC requirements explain the certificate path used for certified logo display.
  1. Message result: The message must pass DMARC through aligned SPF or DKIM for the visible From domain.
  2. DMARC policy: The organizational domain needs p=quarantine or p=reject. Any applicable subdomain policy must also enforce DMARC.
  3. BIMI record: The DNS record must identify the logo and, where the provider requires certification, a VMC or CMC through the a= tag.
  4. Certificate validity: The certificate must be inside its valid date range, remain unrevoked, cover the sending domain, contain the matching logo, and chain to an issuer the receiver accepts.
  5. Receiver policy: Each mailbox provider applies its own caching, reputation thresholds, and display rules.
RFC 9989 removed the pct tag from DMARC. Gmail's published BIMI instructions still specify pct=100, so retain that value where needed for compatibility with Gmail's BIMI checks. Treat this as provider compatibility guidance, and keep DMARC enforcement active.
BIMI validation flowchart showing an expired VMC preventing a verified checkmark.
BIMI validation flowchart showing an expired VMC preventing a verified checkmark.

Does an expired VMC become self-asserted BIMI?

No. An expired VMC remains expired evidence referenced by the BIMI record. A self-asserted record omits certificate evidence, using an empty or missing a= tag. To publish that configuration, change DNS deliberately; do not rely on expiry to trigger a fallback.
Providers that accept self-asserted BIMI apply their own reputation and display rules, including how they handle a published but invalid certificate. Gmail does not accept a standalone SVG for BIMI display. It requires a valid VMC or CMC, and only a valid VMC produces Gmail's blue checkmark.
Valid VMC path
  1. Certificate status: The VMC is inside its valid date range and chains to an accepted issuer.
  2. Gmail result: The message qualifies for the logo and blue checkmark when all other checks pass.
  3. Brand signal: The certificate provides validated rights to the mark for the sending domain.
Expired VMC path
  1. Certificate status: The date check fails even when the BIMI TXT syntax and certificate URL are correct.
  2. Gmail result: The logo and blue checkmark stop unless a valid replacement certificate is published.
  3. Logo-only option: Gmail needs a valid CMC; self-asserted display depends on another provider accepting it.
This distinction explains a confusing result: a sender can have a correct BIMI record, a reachable SVG, and a certificate file at the right URL, yet still lose Gmail's logo and checkmark because the certificate expired. A sender can also see different results across providers because their certificate and self-asserted display rules differ.
A valid Common Mark Certificate can qualify a BIMI logo for display in Gmail without the blue checkmark. It is a separate certificate path, not a fallback status applied to an expired VMC. The CMC must cover the sending domain and logo, be hosted as a complete PEM chain, and be referenced by the BIMI a= tag.
Choose the replacement by outcome
  1. Keep the Gmail blue checkmark: Renew or replace the VMC before expiry and publish the valid PEM file.
  2. Keep a Gmail logo only: Obtain a valid CMC and update the certificate reference after the file is reachable.
  3. Use self-asserted BIMI: Publish an empty a= value only when logo display at supporting non-Gmail providers meets the business need.
Do not wait for expiry to choose between VMC renewal and a CMC. Both certificate types require validation and issuance lead time. Publish a valid replacement VMC before notAfter to avoid a gap in eligibility for Gmail's blue checkmark.

Expected behavior by mailbox provider

Use the table as a troubleshooting model. Reputation, certificate acceptance, caching, and interface rules still affect whether a provider displays a logo. The blue-checkmark column refers specifically to Gmail's VMC badge.

Mailbox

Expired VMC

Logo-only route

Gmail blue checkmark

google.com logoGmail
Certificate path fails
Valid CMC
No
yahoo.com logoYahoo Mail
Invalid evidence can affect eligibility
Self-asserted record can qualify
No
aol.com logoAOL
Invalid evidence can affect eligibility
Self-asserted record can qualify
No
laposte.fr logoLa Poste
Certificate evidence fails
Self-asserted record with domain approval
No
Other providers
Policy varies
Provider-specific
No Gmail badge
Likely receiver behavior after VMC expiry
Gmail inbox showing a sender without a BIMI blue checkmark.
Gmail inbox showing a sender without a BIMI blue checkmark.
Yahoo's BIMI guidance says Yahoo and AOL do not require a VMC, but use a published VMC when assessing eligibility. La Poste's self-asserted path requires domain approval. Gmail requires a valid VMC or CMC for BIMI logo display; only the VMC qualifies for its blue checkmark.

How to confirm the VMC is the problem

Start with DNS because it identifies the evidence file. The a= tag points to the certificate PEM. In Google's certificate-based BIMI setup, the logo is embedded in that PEM, so l= can be empty. If you also publish a standalone SVG URL, keep its logo consistent with the certificate. Check the PEM's certificate type and validity period, plus the chain and revocation status.
BIMI record with a certificateDNS
default._bimi.example.com. 3600 IN TXT ( "v=BIMI1; l=https://assets.example.com/bimi.svg; " "a=https://assets.example.com/vmc.pem" )
  1. Find the record: Look up the default BIMI selector first, then any selector the sending stream declares.
  2. Fetch the certificate: Open the URL in the a= tag and confirm it returns the expected PEM file without access controls or a broken redirect.
  3. Check the certificate: Confirm whether it is a VMC or CMC, inspect notBefore and notAfter in UTC, verify coverage of the sending domain, check revocation, and verify the full chain.
  4. Match the logo: Validate the embedded SVG Tiny PS logo. If the l= tag points to a separate SVG, confirm that it matches the embedded logo.
  5. Check DMARC: Confirm the organizational domain and applicable subdomain policy enforce DMARC, and the production message passes DMARC alignment.
  6. Send a test: Send new mail through the affected stream, inspect its Authentication-Results header for DMARC, and check what each target mailbox renders.
Replace the example URL with your own a= URL to inspect the hosted certificate. With the entity certificate first in the PEM, these OpenSSL commands print its validity dates and check whether it expires within 30 days.
Inspect the VMC expiry date with OpenSSLBASH
curl --fail --silent --show-error --output vmc.pem 'https://assets.example.com/vmc.pem' openssl x509 -in vmc.pem -noout -dates -subject -issuer openssl x509 -in vmc.pem -noout -checkend 2592000
The final command exits nonzero if the certificate is expired or expires within 2,592,000 seconds (30 days). This inspects the first certificate only; it does not validate the complete chain or revocation status. The hosting server's TLS certificate has its own validity period.
Suped, our DMARC reporting and email authentication platform, connects sending-source authentication results with policy state and issue alerts. Its DMARC monitoring helps identify authentication failures that prevent BIMI qualification. The VMC or CMC still needs a separate owner, renewal process, and certificate check.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
Use Suped's DMARC checker for a DNS and enforcement check before debugging the certificate. If the domain is not at full enforcement, fix that dependency first.

The hosting TLS certificate can expire separately

The HTTPS server hosting your PEM file has a TLS/SSL certificate separate from the VMC inside that file. If the TLS certificate expires or the secure connection fails validation, the receiver cannot retrieve the PEM through the required HTTPS connection, even while the VMC remains current. The same hosting checks apply to a separately hosted SVG.

Certificate

What it validates

Expiry check

VMC or CMC
The mark associated with the sending domain
Read notAfter in the hosted PEM's entity certificate
Hosting TLS/SSL certificate
The HTTPS connection to the asset hostname
Check the certificate presented by each hosting endpoint
The VMC and hosting TLS certificate have separate renewal dates
Monitor both expiry dates and test each published HTTPS URL from outside your network. Renewing one certificate does not renew the other. The BIMI Group's certificate guidance confirms that shorter browser-trusted TLS certificate lifetimes do not change the 398-day maximum for BIMI mark certificates.

How to renew a VMC and restore BIMI display

The preferred fix is to renew or replace the mark certificate, publish the complete new PEM chain, update the BIMI record if the certificate URL changed, and then retest mail that leaves the production sending platform. Remove the certificate reference only when the business has deliberately chosen self-asserted BIMI at providers that support it.
Renewal sequence
  1. Renew certificate: Complete issuer revalidation early enough to publish the replacement before notAfter. Confirm the organization details and domain control, plus the mark rights and authorized contacts.
  2. Publish PEM: Host the renewed entity certificate first, followed by the required issuer chain, at a public HTTPS URL.
  3. Validate before cutover: Fetch the new file, confirm that its validity period has started, and verify the chain and embedded logo before changing production.
  4. Update BIMI: Replace the hosted PEM and clear any CDN cache you control. Change the a= value only if the certificate URL changed.
  5. Retest mail: Send new messages and check authentication results plus inbox rendering.
Do not assume the logo returns immediately. DNS TTL matters when the TXT record changes; receiver caches can delay display even when the PEM URL stays the same. There is no universal receiver cache deadline. Test fresh messages across the affected mailbox providers after publishing the replacement.
The VMC fetch and validation draft leaves receiver cache TTLs unspecified and describes using a new certificate URL to request a fresh fetch. If you use that approach, update a= to the new public HTTPS URL; it does not guarantee immediate logo display.
Self-asserted BIMI recordDNS
default._bimi.example.com. 3600 IN TXT ( "v=BIMI1; l=https://assets.example.com/bimi.svg; a=;" )
An empty a= value makes the record self-asserted. That can support logo display at providers that accept self-asserted BIMI, but it does not qualify for Gmail. Use a valid CMC for a Gmail logo without the checkmark, or renew the VMC to restore the Gmail logo and blue checkmark.

Why a valid-looking BIMI record still fails

A BIMI record can be syntactically valid and still fail display. Separate record format from certificate validation. A DNS parser can confirm v=BIMI1, the SVG URL, and the certificate URL without proving that the certificate is current, unrevoked, issued for the right mark and domain, or chained to an accepted issuer.
VMC renewal risk window
Internal operating targets for deciding how urgently to act before certificate expiry.
Healthy
90+ days
Renewal has enough time for validation and publishing.
Watch
30-89 days
Start renewal and verify mark documentation now.
Critical
1-29 days
Escalate because display loss is close.
Expired
Past notAfter
Expired certificate evidence fails validation until a valid replacement is published.
BIMI mark certificates (VMCs and CMCs) have a maximum validity period of 398 days. A multi-year purchase does not extend an individual certificate; use its actual notAfter value for renewal planning. The chart uses internal warning thresholds, not protocol-mandated renewal dates.

Checks that prevent repeat failures

The prevention work needs a named owner. Assign responsibility for the certificate renewal date, hosted PEM file, BIMI SVG, and DMARC enforcement state. When ownership is split across teams without a common runbook, BIMI can fail without affecting message delivery.

Item

Owner

Failure symptom

VMC or CMC
Security or IT
Logo or checkmark missing
Mark evidence
Legal
Renewal delay
SVG
Brand
Logo rejected
DNS and HTTPS hosting
IT
Record or file unavailable; hosting TLS invalid
DMARC
Email operations
BIMI blocked
Operational ownership for BIMI and VMC
Keep a certificate-specific expiry test. BIMI record syntax alone does not show whether the PEM contains a current entity certificate, the required chain, or the logo that matches the published assertion.
  1. Expiry reminders: Set reminders at 90, 60, 30, 14, and 7 days before the notAfter date.
  2. Real-message tests: Test through each production mail stream, not only through a DNS check.
  3. URL stability: Keep certificate and SVG URLs stable, publicly reachable, and covered by change control.
  4. Policy guardrails: Keep organizational-domain and applicable subdomain policies enforced. Prevent rollback to p=none or a testing policy, and preserve Gmail's published pct=100 compatibility setting where needed.
For deeper follow-up, check the VMC expiry guide, confirm Gmail and VMC requirements, and use the BIMI validation guide when the SVG or certificate format is suspect.

Frequently asked questions

No. Gmail needs a valid VMC for the blue checkmark. An expired VMC fails that certificate check after Gmail revalidates it.

Provider behavior varies. Gmail needs a valid VMC or CMC for BIMI logo display. Certificate-optional providers apply their own handling of expired evidence and their other logo-display requirements; an expired VMC does not guarantee logo removal everywhere.

No. The record still references expired certificate evidence. To publish self-asserted BIMI, deliberately remove the certificate reference or use an empty a= value. Certificate-optional receivers still apply their own display rules.

A valid CMC can qualify the logo for Gmail without the blue checkmark. It does not extend or convert the expired VMC.

There is no universal receiver cache deadline. DNS TTL matters if you changed the record; a cached PEM or display decision can delay restoration even at an unchanged URL. Test new messages after publishing the valid replacement.

VMC expiry alone does not cause SPF, DKIM, or DMARC to fail and does not instruct receivers to reject your messages. It affects certificate-backed logo and checkmark eligibility. If delivery also changes, investigate authentication results and sender reputation separately.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing