Non-HTTPS URL Encountered While Fetching the VMC Certificate

What Does “Non-HTTPS URL Encountered While Fetching the VMC Certificate” Mean?

“Non-HTTPS URL encountered while fetching the VMC certificate” means certificate retrieval encountered a non-HTTPS authority URL at fetch time. The VMC validation algorithm requires the a= retrieval URI to use HTTPS. Fetch and Validation of Verified Mark Certificates draft 11 documents the controlling requirement or boundary.

VMC validation returns an error before path validation. Redirect behavior and the exact checker stage are implementation-specific.

Why Does Non-HTTPS URL Encountered While Fetching the VMC Certificate Appear?

Non-HTTPS URL encountered while fetching the VMC certificate appears when a non-HTTPS URL is encountered at certificate-retrieval time, after the earlier syntax check of the published a= value. The exact diagnostic should be read at the scope of VMC retrieval path rather than as proof that every BIMI layer failed.

How Do You Fix Non-HTTPS URL Encountered While Fetching the VMC Certificate?

To fix Non-HTTPS URL encountered while fetching the VMC certificate, publish and retain an end-to-end HTTPS certificate URL without a scheme downgrade.

Correcting the fetch scheme does not repair certificate content or trust.

What Should You Verify After Fixing Non-HTTPS URL Encountered While Fetching the VMC Certificate?

After fixing Non-HTTPS URL encountered while fetching the VMC certificate, trace the complete retrieval path and confirm every effective certificate URL remains HTTPS. 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 VMC retrieval path.
• The direct correction is to publish and retain an end-to-end HTTPS certificate URL without a scheme downgrade.
• Correcting the fetch scheme does not repair certificate content or trust.