BIMI monitoring: watch inbox brand-mark DNS before the logo vanishes
BIMI monitoring is how you notice the inbox brand-mark pointer drifted—deleted after a zone rebuild, republished without v=BIMI1, or never restored after a mail-host move—before supporting inboxes stop showing your logo. CrowWake’s check is a public default._bimi TXT resolve, not a full SVG or VMC validator.
What BIMI monitoring means here
Operators searching for BIMI monitoring or a BIMI checker usually want an early rooster: is v=BIMI1 still published at default._bimi, and does the record still look like a real brand-mark pointer? CrowWake answers with a public TXT lookup and a short summary of the published rows. It sits beside DMARC monitoring so “enforcement still live” and “logo DNS still published” show up in the same flock—BIMI only matters after DMARC is ready.
What CrowWake checks
We resolve TXT at default._bimi.yourdomain for a record that includes v=BIMI1. Missing BIMI → warn (optional for many domains). Present → ok, with a summary of the published record. The free BIMI checker uses the same DNS lookup with no login—the same signal the hourly probe uses. CrowWake does not fetch the SVG logo or validate a Verified Mark Certificate in v1; it watches whether the brand-mark DNS pointer still exists.
Monitoring vs “what is BIMI”
The BIMI guide explains inbox logos, DMARC prerequisites, SVG/VMC shape, and the publish order in plain English. Monitoring is the repeat job: catch a deleted default._bimi after a panel cleanup, a zone copy that dropped underscore hosts, or a brand-kit cutover that emptied l= while DMARC stayed green. Both use the same free BIMI checker; CrowWake just repeats the pulse every hour. Pair with DMARC monitoring so you do not chase a missing logo when policy slipped back to p=none.
What “good enough” looks like
DMARC at quarantine or reject with alignment first. Then a single BIMI1 record with an HTTPS l= URL to a square Tiny PS SVG you control (and a= if your providers require a VMC/CMC). Intentional “no BIMI yet” is fine for domains that never want inbox logos; accidental empty after a migration is not—especially once you already shipped the mark to marketing.
Quick triage when BIMI goes yellow or red
1) Re-run the free BIMI checker and confirm missing vs present v=BIMI1. 2) If missing on purpose, leave it—BIMI is optional. 3) If you expect logos, confirm DMARC enforcement with the free DMARC checker before restoring DNS. 4) Restore TXT at default._bimi with v=BIMI1 and your l= (and a= if needed). 5) Wait for DNS TTL, re-check. 6) Add the domain so CrowWake crows on the next wipe instead of discovering a blank inbox mark months later.
If CrowWake crows
Treat the failing check as source of truth: empty default._bimi vs a logo URL that no longer loads are different jobs. Use the BIMI how-to for record shape and DMARC prerequisites, re-run the free BIMI checker, then keep watching. CrowWake monitors the public brand-mark DNS pointer—it does not host your SVG or issue a VMC for you.
Watch this on CrowWake
Add the domain, leave the boxes checked, and the flock will crow when this drifts.
Or try the free BIMI monitoring / brand mark checker with no login.
Related: what is BIMI / how to check BIMI, DMARC monitoring, DMARC, SPF monitoring, DKIM monitoring, and the free DMARC checker (enforcement first).