Fail

The BIMI mark certificate couldn't be fetched

The short version

Serve the certificate PEM over https at the a= URL.

What it means

Your BIMI record names a mark certificate in its a= tag, but we couldn't fetch it. The detail says why: the host can't be reached, it answered with an error such as 404, or its HTTPS certificate isn't trusted.

Why it matters

Gmail and Apple Mail need the certificate to show your logo. If they can't fetch it, they show nothing, even though you have paid for the certificate. This usually happens when the file was moved during a website change or when the certificate authority's hosting address changed at renewal.

How to fix it

  1. Open the a= address in a browser. It should download a text file starting with -----BEGIN CERTIFICATE-----.
  2. If it fails, download the current PEM from your certificate authority and publish it again at an https: address you control.
  3. Update the a= tag if the address changed.
  4. Make sure the host doesn't require a login or show a bot challenge.

Check it worked

Run the MTA-STS checker on your domain again once the old record's TTL has passed, usually within an hour. The certificate row should show it fetched.