BIMI Checker
Check the default BIMI record, logo and mark certificate URLs, SVG response, and the DMARC enforcement BIMI depends on.
Checking BIMI and DMARC...
What this BIMI checker reviews
Record location
The default selector is queried at default._bimi for a v=BIMI1 TXT record.
DMARC readiness
BIMI requires an enforcing DMARC quarantine or reject policy before supported inboxes display the logo.
Logo response
The HTTPS logo is fetched through an SSRF guard, checked for an SVG-compatible response, and never inlined into the page.
Balanced scoring
BIMI is a branding control, so it is reported but does not reduce the core email-security score.
What BIMI can and cannot prove
Brand Indicators for Message Identification lets supported mailbox providers display a verified brand logo for authenticated email. The BIMI record points to an approved SVG logo and can include a Verified Mark Certificate or Common Mark Certificate URL. Provider support and certificate requirements vary, so a technically valid record does not guarantee that every inbox will display the logo.
BIMI is the final layer, not the first. SPF and DKIM should authenticate legitimate senders, and DMARC must enforce quarantine or reject. This scanner checks those prerequisites alongside the BIMI record. It treats a missing BIMI record as informational because lack of a logo is not an email spoofing vulnerability.
A practical BIMI rollout order
Begin with DMARC aggregate reports, not the logo. Confirm every production sender aligns through SPF or DKIM, enforce DMARC on the organizational domain, and account for subdomains that send mail. A visible logo is not worth disrupting invoices, password resets, support replies, or marketing campaigns by moving to enforcement before legitimate traffic is understood.
Prepare the logo as SVG Tiny Portable/Secure rather than exporting an unrestricted website SVG. Remove scripts, external references, embedded raster images, animation, and other active content. Host the file at a stable public HTTPS URL with an SVG-compatible content type. Avoid short-lived signed URLs because mailbox providers need to retrieve the same asset over time.
Decide whether the mailbox providers important to your audience require a VMC or CMC. Certificate eligibility, accepted marks, and display rules are provider decisions. Publish the certificate URL only after the PEM file is reachable and the certificate details match the organization and logo you intend to use.
Why a valid record may not display a logo
First check DMARC enforcement and real-message alignment. Then verify the exact default._bimi TXT response, the logo URL, redirects, TLS certificate, response content type, and SVG profile. If a mark certificate is used, verify its URL and validity period. Finally, check the receiving provider's current BIMI program; reputation thresholds, certificate requirements, caching, and rollout support can differ even when DNS is correct.
This scanner fetches referenced assets through an SSRF guard and inspects the response as untrusted data. It deliberately does not render an external SVG in the report. That security boundary prevents a branding check from becoming a path for active content to execute in a visitor's browser.
For current logo, DMARC, and certificate preparation steps, use the BIMI Group implementation guide. Recheck provider requirements before purchasing a certificate or scheduling a production rollout.
BIMI FAQ
Does BIMI stop spoofing?
No. DMARC enforcement stops unauthorized use of the visible From domain. BIMI builds on that enforcement to display a brand logo.
Do I need a VMC or CMC?
Some mailbox providers require a supported mark certificate. Requirements vary by provider and brand eligibility.
Why does the scanner not display my external SVG?
External SVG is treated as untrusted content. The backend checks it as an opaque response and the frontend never inlines it.
