LLPROBeta

Home / Businesses / BIMI Record Check

BIMI Record Check

Check a BIMI record before it goes into DNS: one https SVG logo address, the Mark Certificate address, declination, each problem with its draft section, and whether the DMARC policy allows the logo, signed.

Testing

What it does
Check a BIMI record before it goes into DNS: one https SVG logo address, the Mark Certificate address, declination, each problem with its draft section, and whether the DMARC policy allows the logo, signed.
Who it is for
Businesses.
Start in one step
Ask your agent to call bimi_record_check at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

BIMI Record Check is for agents that set up email branding and authentication for a business (brand logo in the inbox, DMARC at enforcement) and need the BIMI record and DMARC policy checked before publishing. Check a BIMI record (the DNS TXT record that points mail receivers to a brand logo) before it is published. Send the record text, and optionally the domain's DMARC record. Get back whether receivers read it, the logo address (one https address, SVG or SVGZ), the evidence (Mark Certificate) address, avatar preference, local-part prefixes, whether it is a declination record, each problem with its draft section, and whether the DMARC policy is strong enough for BIMI (quarantine at 100% or reject, subdomain policy not none, test mode). It is one of the Email department tools LLPRO builds for the work agents do across business software (Gmail, Outlook, Google Workspace, Microsoft 365, Sendgrid). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that set up email branding and authentication for a business (brand logo in the inbox, DMARC at enforcement) and need the BIMI record and DMARC policy checked before publishing.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not query DNS, fetch the logo or the certificate, or check the SVG file itself (SVG Tiny Portable/Secure profile, size, title) or the Mark Certificate's validity, issuer or trademark: it reads the text you send. Does not check DMARC alignment or that mail actually passes DMARC (draft 7.1 steps 1-6), the np tag, or where the record should fall back to the Organizational Domain. Whether a logo is shown is each mailbox provider's choice (many require a VMC or CMC and sender reputation). BIMI is an Internet-Draft, not yet an RFC; the rules may change.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "bimi_record_check", "arguments": {"record": "v=BIMI1; l=https://brand.example.com/logo.svg; a=https://brand.example.com/vmc.pem", "dmarc_record": "v=DMARC1; p=reject; rua=mailto:d@example.com", "domain": "example.com"}}}

For agents

Tool bimi_record_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:jc7voiwgamtdnjt6a2exzpskxa): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): /5hB0pCCc15xlIEQsi2bK7XsGc3HRWAG4gxEjhf2PjU=

For agents that search MCP registries for BIMI, BIMI record, brand logo in email tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card