The BIMI Analyzer Is Live — Our Free Analyzer Suite Is Now Complete
Email authentication has four layers that matter: SPF, DKIM, DMARC, and — once DMARC is actually enforced — BIMI. Until now, our free tools covered the first three. Today we're closing that gap with a BIMI Analyzer, which means every layer a domain owner needs to check now has a dedicated, free, no-signup tool.
Logo shown: BIMI Group's own mark, used here to illustrate a passing result.
The complete analyzer suite
- Domain Scanner — a full-domain overview: SPF, DMARC, MTA-STS and TLS-RPT in one scan, with an overall risk score.
- SPF Analyzer — resolves your SPF record, counts DNS lookups against the 10-lookup ceiling, and identifies known email providers in your includes.
- DMARC Analyzer — parses every tag, checks DKIM/SPF alignment mode, and flags deprecated tags like
pct=. - BIMI Analyzer — new today. Checks your BIMI record, previews the actual logo, validates the SVG, and confirms whether your VMC and DMARC enforcement actually clear the bar mailbox providers require.
Each one works the same way: enter a domain, get a real DNS-backed result in seconds. No account, no email required to see the results.
What the BIMI Analyzer actually checks
A BIMI record can be syntactically perfect and still show nothing in anyone's inbox — that's what makes BIMI different from SPF or DMARC to diagnose. A missing space in an SPF record breaks obviously; a BIMI setup can fail silently in half a dozen different ways. The analyzer checks all of them in one pass:
- Is the record published at
default._bimi.yourdomain.com, and is it well-formed - Is the logo reachable, served as
image/svg+xml, and does it render — you see an actual preview of it, not just a checkmark - Is the logo square — BIMI requires a 1:1 aspect ratio, and a rectangular wordmark will silently fail even with everything else correct
- Does the SVG meet BIMI's restricted profile — no
<script>tags, no embedded raster images, no external references, all of which a general-purpose SVG export from most design tools will fail on the first try - Is a VMC configured, and does the certificate URL actually resolve
- Is DMARC enforced —
p=quarantineorp=reject— since a BIMI record published againstp=noneis valid DNS and functionally invisible
That last check is the one most homegrown validators skip, because it means looking up a second DNS record and cross-referencing it. It's usually the actual reason a "correctly configured" BIMI record shows nothing — see What is BIMI? for the full explanation of why that dependency exists, or What is DMARC? if enforcement itself is the part you haven't gotten to yet.
Try it
Run your domain through the BIMI Analyzer. If DMARC isn't enforced yet, start with the DMARC Analyzer to see exactly where your policy stands today — or skip the manual DNS work entirely with Hosted BIMI.