# BIMI Checker

Validate BIMI for a domain: the default._bimi TXT record (l= logo URL, a= certificate URL), whether DMARC is enforcing (BIMI needs quarantine or reject at 100 percent), the SVG logo against the BIMI Tiny PS profile (size, square, no script, no external references, no raster), and the VMC or CMC certificate (issuer, mark type, validity, names that must cover the domain, the BIMI usage and a matching logo hash). Returns a verdict (ready, partial, not_ready, none), each part with its issues and fixes, a validated logo as a data URI for display, and a table of which mailbox providers show a logo and what they need, with sources and the date they were checked. Public domains only.

**Not for:** Making a BIMI record or converting a logo (not available yet).

- Tool id: `bimi-check`
- Category: email
- Execution: network
- MCP tool `bimi_check` at https://lookupowl.com/mcp
- REST `GET https://lookupowl.com/api/v1/tools/bimi-check` (or POST a JSON body)
- OpenAPI: https://lookupowl.com/api/openapi.json

## Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `domain` | string | yes |  | The domain whose mail should show the logo, such as example.com. An email address works too: only the part after the @ is used, and it is not stored. min length 1, max length 320 |
| `selector` | string | no | `"default"` | The BIMI selector. Almost every domain uses default; change it only if you were given another. max length 63 |

## Output

Results are wrapped in an envelope: `tool`, `version`, `requestId`, `data`, `summary`, `meta` (cache status, timing), `permalink`. `data` has these fields:

| Field | Type | Description |
|---|---|---|
| `domain` | string |  |
| `selector` | string |  |
| `asOf` | string |  |
| `verdict` | "ready" \| "partial" \| "not_ready" \| "none" | ready: every link holds. partial: the logo can show in some inboxes, or a part could not be read in time. not_ready: something blocks every inbox. none: no BIMI record. |
| `record` | object |  |
| `dmarc` | object |  |
| `svg` | object |  |
| `certificate` | object |  |
| `notChecked` | "logo" \| "certificate"[] | Parts whose host did not answer in time. |
| `providers` | object[] |  |
| `providerAsOf` | string | Month of the vendor information, YYYY-MM; re-checked every quarter. |
| `issues` | any[] | Every issue of every part, in one list. |

## Examples

### A full pass with a VMC: paypal.com

```json
{"domain":"paypal.com","selector":"default"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/bimi-check?domain=paypal.com&selector=default'
```

Web page: https://lookupowl.com/bimi-checker?q=paypal.com

### ebay.com

```json
{"domain":"ebay.com","selector":"default"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/bimi-check?domain=ebay.com&selector=default'
```

Web page: https://lookupowl.com/bimi-checker?q=ebay.com

### Hosted BIMI: cnn.com

```json
{"domain":"cnn.com","selector":"default"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/bimi-check?domain=cnn.com&selector=default'
```

Web page: https://lookupowl.com/bimi-checker?q=cnn.com

### No record: gmail.com

```json
{"domain":"gmail.com","selector":"default"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/bimi-check?domain=gmail.com&selector=default'
```

Web page: https://lookupowl.com/bimi-checker?q=gmail.com

## Web pages

- https://lookupowl.com/bimi-checker

## Limits and caching

- Cost: 8 units for a live lookup, 1 unit for a cached one. Budgets are per network and published in the `RateLimit` response headers.
- Cache: the lifetime follows the data (for DNS, the record TTL, within a few minutes). Add `fresh=true` (MCP argument or query parameter) to look again; it costs 3 units per unit and is limited to 10 per hour.
- Timeout: 20 s.

## Related tools

- [DMARC Record Checker](https://lookupowl.com/tools/dmarc-checker.md): Look up and validate a domain's DMARC policy, report addresses and alignment settings.
- [Email Health Checker and Spoofing Test](https://lookupowl.com/tools/email-health.md): Check a domain's whole mail setup in one report: mail servers, SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and blocklists, with the fixes to make first.
- [Certificate and CSR Decoder](https://lookupowl.com/tools/x509-decode.md): Read a certificate, chain or CSR field by field: names, validity, key, fingerprints and lint findings. It runs in your browser.
- [SPF Record Checker](https://lookupowl.com/tools/spf-checker.md): Check a domain's SPF record, count its DNS lookups against the limit of 10 and find errors.
- [DKIM Record Checker](https://lookupowl.com/tools/dkim-checker.md): Find and check a domain's DKIM public keys, even when you do not know the selector.

## Guide: BIMI checker

Find out why a domain's logo is not showing next to its mail, and what to fix first.

### What BIMI needs

BIMI (Brand Indicators for Message Identification) lets a domain show its logo next to the mail it sends, in inboxes that support it. It is a chain, and one weak link stops the logo. That is why most people who set it up end up asking why nothing shows.

1. **Enforced DMARC.** The policy must be `quarantine` or `reject`, applied to 100 percent of mail, with no `t=y` testing flag. `p=none` does not qualify. This is the most common reason a logo is missing.
2. **A BIMI record.** A TXT record at `default._bimi.<domain>` that reads `v=BIMI1; l=<logo address>; a=<certificate address>`. Both addresses must be HTTPS.
3. **A logo in a strict format.** A square SVG that follows the Tiny PS profile: version 1.2, `baseProfile="tiny-ps"`, a title, no script, no external references, no embedded picture, no CSS, 32 KB or smaller.
4. **A certificate, for most inboxes.** A Verified Mark Certificate (VMC) for a registered trademark, or a Common Mark Certificate (CMC) without one. It must cover your domain and carry a copy of the exact logo you serve.

The checker walks that chain in order, marks each link, and shows the logo it found in light and dark settings at the sizes inboxes use. At the end it says which inboxes would show it.

### How to check a domain

1. **Enter the domain**: Use the domain in your From address, such as `example.com`. If you paste an email address, we keep only the part after the @, and we do not store the address.
2. **Read the answer**: The top tile says ready, partly ready, not ready or not set up, with the six links of the chain under it. Open the first one that fails.
3. **Check the logo and the certificate**: The logo appears only if it passed every rule. The certificate card shows the type, who issued it, the days left, the names it covers and whether its logo matches yours.

> **Nothing shows yet?** Start with DMARC. Check it with the [DMARC checker](https://lookupowl.com/dmarc-checker), and build a record with the [DMARC record generator](https://lookupowl.com/dmarc-record-generator) if you have none.

> **In Claude, ChatGPT or Cursor** Connect the LookupOwl MCP server and ask: "Would the logo for example.com show in Gmail?" The assistant calls `bimi_check` and reads the same structured answer you see here.

### VMC and CMC certificates

Both certificate types prove that the logo belongs to the domain. They differ in what they prove about the logo itself.

| Type | What it proves | What Gmail does |
|---|---|---|
| VMC, Verified Mark Certificate | The logo is a registered trademark of the organization. | Shows the logo and a checkmark. |
| CMC, Common Mark Certificate | The organization has used the logo, or a modified registered logo, but needs no registration. | Shows the logo, without a checkmark. |

The certificate has a BIMI usage in its extended key usage list, which tells it apart from an ordinary web certificate. It also holds a hash of the logo, so a logo you change later no longer matches. The checker compares that hash with the file your record serves and tells you when they differ, which is the usual reason a working setup stops working after a rebrand.

Certificates for BIMI last about a year. When one expires, inboxes stop showing the logo, so the checker warns when fewer than 30 days remain. To read every field of the certificate yourself, paste it into the [certificate decoder](https://lookupowl.com/certificate-decoder), where it stays in your browser.

### Which inboxes show the logo

Support differs by inbox, and the rules change. Gmail and Apple Mail want a certificate. Yahoo and AOL can show a logo without one for some senders, based on their own checks of volume and history. Outlook and Microsoft 365 do not support BIMI at all.

The table in the result lists each inbox with what it needs, why it gave its answer, and a link to the vendor page the row comes from. The table has a date, and we re-check it every quarter. It is vendor information. We cannot see an inbox from outside, so a row says what the vendor documents, not what one particular inbox did with one particular message.

### How the check works

We read the TXT record at `<selector>._bimi.<domain>`. Almost every domain uses `default`. If the domain has none of its own, we look at its organizational domain, as inboxes do. In parallel we read the DMARC policy the same way.

Then we fetch the logo and the certificate from the addresses in the record. Only HTTPS is used, only public web servers, and each file is cut off at a small size limit with a short timeout. We never follow a redirect to plain HTTP. We read the logo as text and never run it. It is shown on the page only after every rule passed, and only as a picture, never as markup. A file that breaks a rule is shown as text, so you can see the line.

We do not check the full certificate chain up to a root, because that is each inbox provider's job against its own list of authorities. We do not test a real message. And the Tiny PS check covers the common failures, not every element the standard allows. If your logo passes here and still does not show, the inbox may be applying a rule we cannot see, such as sending reputation.

### Frequently asked questions

**Do I need a certificate?**

For Gmail and Apple Mail, yes: a VMC or a CMC. Yahoo and AOL can show a logo without one for some senders, and Outlook and Microsoft 365 show none either way. The checker tells you what your setup earns in each inbox.

**Why must DMARC be enforced?**

BIMI shows a logo only for mail that is hard to fake. A DMARC policy of quarantine or reject, applied to all mail, is the proof. With p=none or a partial percentage, anyone could send forged mail that would carry your logo.

**Why does my logo fail the format check?**

Most design tools export SVG 1.1 with styles, a rectangle canvas and no title. BIMI needs version 1.2 with baseProfile tiny-ps, a square viewBox, a title, no CSS, no script and no embedded picture. The result lists each broken rule with the line it is on.

**Why does the logo in the certificate not match mine?**

The certificate holds a hash of the logo it was issued for. If you changed the file after that, the hashes differ and inboxes refuse it. Serve the original file, or ask your certificate authority to reissue the certificate for the new logo.

**How long until the logo shows after I fix things?**

DNS changes follow their TTL, and inboxes cache BIMI results, so it can take hours or days. Use the checker to confirm each link holds, then send mail. Results here are kept for up to ten minutes, so use Check again after you change something.

**Do you store my logo?**

Not beyond a short cache. We fetch it, check it and show it in the result. The answer, with the checked logo in it, is kept for up to ten minutes so repeat checks are fast, and then it is deleted. The logo is shown only after it passed every rule.
