Fail

The BIMI logo couldn't be fetched

The short version

Serve the SVG logo over https at the URL in the record.

What it means

We couldn't fetch the logo named in the l= tag of your BIMI record. The detail says what happened: the host can't be reached, the server answered with an error such as 404 or 403, or its certificate isn't trusted.

Why it matters

Mailbox providers fetch the logo the same way. If they can't, they show no logo. This often happens after a website redesign moves or renames files, when the logo sits behind a login or a bot challenge, or when a CDN blocks requests that don't come from a browser.

How to fix it

  1. Open the logo address from your BIMI record in a private browser window. It should load the SVG directly, without redirects to a login page.
  2. Restore the file at that address, or update the l= tag to the new address.
  3. Make sure the host has a valid certificate and allows automated requests for that file.
  4. Serve it with Content-Type: image/svg+xml.

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 logo row should show it fetched, with its size.