Skip to main content
  1. Knowledge base
  2. Email security

Fix BIMI SVG Tiny PS Error: Logo Rejected by Mailbox Providers

A BIMI SVG Tiny PS error means your BIMI DNS record is valid, but the SVG it points to breaks the SVG Tiny Portable/Secure profile, so mailbox providers silently drop the logo. Fix the file by removing scripts, external references and bad sizing, then serve it over HTTPS.

BIMI (Brand Indicators for Message Identification) is an email standard that lets a sender publish a logo in DNS so supporting mailbox providers can show it beside authenticated messages.

What causes a BIMI SVG Tiny PS error?

The BIMI record only holds a URL. Providers fetch the file and check it against SVG Tiny PS, a restricted profile meant to make logos safe to render inside a mail client. A logo that looks fine in a browser can still fail, because browsers accept far more than the profile allows.

Typical violations:

  • <script> elements or on* event attributes.
  • External references: xlink:href or href pointing to another URL, remote fonts, linked stylesheets, embedded raster images loaded by URL.
  • Missing version="1.2" and baseProfile="tiny-ps" on the root element.
  • A missing or non-square viewBox, or a width/height that conflicts with it.
  • Animation, <foreignObject>, filters, or other features outside the profile.
  • Files exported from design tools, which often add metadata, editor namespaces and <style> blocks.

Validators differ in strictness, and providers may apply extra rules. A pass in one tool is a good sign, but not a guarantee.

Why does it matter?

Failure is silent. Mail still delivers and the DNS record resolves, so nothing bounces. You only notice when the logo never appears, and the work you put into DMARC enforcement and branding shows no visible return.

For an auditor, a BIMI record pointing at a non-conforming file is evidence of an unverified control. For security, a file that permits scripts or external fetches is exactly what the profile exists to prevent. BIMI also has real prerequisites: an enforced DMARC policy and, for most providers, a verified mark certificate. See why a logo never shows without enforced DMARC and how a fake logo can appear without a VMC. A clean SVG replaces neither.

How do I diagnose the failing file?

Start with the record, then the file, then the transport.

dig +short TXT default._bimi.example.com

Expect something like:

default._bimi.example.com. 3600 IN TXT "v=BIMI1; l=https://example.com/brand/logo.svg; a=https://example.com/brand/vmc.pem"

Check how the file is served:

curl -sI https://example.com/brand/logo.svg

Look for HTTP/2 200 with no redirect, content-type: image/svg+xml, and a valid certificate chain. Then inspect the content:

curl -s https://example.com/brand/logo.svg | grep -Eio '<script|href=|onload|<style|foreignObject|baseProfile="[^"]*"|viewBox="[^"]*"'

Any script, href= to a remote URL or foreignObject hit is a probable cause. Confirm the TLS chain too:

openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -dates -issuer

How do I fix the SVG and its hosting?

Correct the file first. A conforming root element looks like this:

<svg xmlns="http://www.w3.org/2000/svg"
     version="1.2" baseProfile="tiny-ps"
     viewBox="0 0 96 96" width="96" height="96">
  <title>Example Corp</title>
  <rect width="96" height="96" fill="#0b3d91"/>
  <path d="M24 24h48v48H24z" fill="#ffffff"/>
</svg>

Steps:

  1. Remove scripts, event handlers, <style> blocks and external links. Use inline presentation attributes instead.
  2. Convert text to outlines so no font is fetched.
  3. Use a square viewBox and make width/height agree with it.
  4. Add a <title> element, which the profile expects.
  5. Strip editor metadata and unused namespaces.
  6. Keep the file small. Providers may enforce size limits that vary by vendor.

Then fix hosting. Serve over HTTPS with a certificate from a public CA, with no redirect chain and the correct type:

location = /brand/logo.svg {
    default_type image/svg+xml;
    add_header Cache-Control "public, max-age=3600";
}

Apache equivalent:

AddType image/svg+xml .svg

Keep the URL stable. If you later swap the file, update the VMC if it embeds the logo, since a mismatch between certificate and SVG also causes rejection.

How would monitoring catch it?

Run the checks above on a schedule instead of once. Alert when the TXT record changes, the SVG hash changes, the response is not 200 with image/svg+xml, the certificate nears expiry, or the content contains forbidden elements. Pair this with DMARC policy checks, since a regression to p=none also hides the logo; see the monitor-only DMARC trap. SetEnforce's scan checks the BIMI record, DMARC enforcement, and whether the referenced logo is reachable over HTTPS.

Common questions

Does a valid BIMI DNS record guarantee the logo will show?

No. The record only proves a URL is published. Providers also require enforced DMARC, a conforming SVG Tiny PS file reachable over HTTPS, and usually a verified mark certificate. Each provider decides independently, so a logo can appear at one and not another.

Can I upload my normal website logo SVG?

Rarely. Website SVGs usually contain styles, fonts, links or a non-square viewBox. Export a dedicated copy, simplify it, set baseProfile="tiny-ps", outline text and remove anything external. Then validate it with a BIMI-aware checker before publishing.

Why did the logo disappear after it worked?

Something changed. Common causes are a replaced SVG, an expired certificate, a new redirect, a DMARC policy relaxed to p=none, or a mark certificate that no longer matches the file. Compare the current file, headers and DNS against your last known good copy.

Key takeaways

  • A BIMI record resolving does not mean the logo is valid; the SVG must meet Tiny PS.
  • Remove scripts, external references and styles, and use a square viewBox.
  • Host the file on HTTPS with image/svg+xml, no redirects and a valid chain.
  • DMARC enforcement and a mark certificate remain separate prerequisites.
  • Monitor the record, file hash, headers and certificate continuously.

Check whether your own domain gets this right. Scanning is free and needs no account.

Scan your domain

All articles