BIMI Record Validator API

About the BIMI Record Validator API

A BIMI validator API that looks up a domain's Brand Indicators for Message Identification record and checks the files it points to. Use it as a BIMI check for any sender domain: it reads the same BIMI DNS record that Gmail, Yahoo and Apple Mail look up before showing a brand logo, confirms the record carries the v=BIMI1 tag, and reports what it found in a single JSON response.

Email marketers, deliverability teams and email security tools use it to confirm a brand's logo setup after publishing the record, to monitor customer domains for a broken logo link, and to flag domains that have not adopted BIMI at all.

The Free plan tells you whether a BIMI record exists at default._bimi.{domain}, how many TXT records sit at that host, the version tag, any issues found and an overall verdict. Paid plans add the full record text and fetch both linked assets: the SVG logo URL with its HTTP status and file size, and the VMC (Verified Mark Certificate) URL with its HTTP status.

How it works

BIMI Record Validator queries the TXT records at default._bimi.<domain>, the default selector. The domain parameter has any scheme and leading www. removed first. Among the TXT strings found, the first containing v=BIMI1 becomes bimi_record; bimi_records_count is the number of TXT records at that host, whether or not they are BIMI.

The record is split into tags on ;, and each tag on its first = only, so l= and a= URLs keep any query string intact. version is the v value. When l= is present the logo URL is fetched, and svg_logo reports the url, the HTTP status_code, valid (true when that status is 200) and file_size_bytes. When a= is present the certificate URL is fetched and vmc_certificate reports its url, status_code and valid in the same way. The two fetches run in parallel, each with an 8-second timeout, and only to public addresses. Neither the SVG markup nor the certificate chain is parsed, so a 200 means the file is reachable, not that it meets the BIMI SVG profile or that the certificate is trusted.

A failed fetch adds SVG_FETCH_FAILED or VMC_FETCH_FAILED to issues_found but does not change valid, which is true whenever a v=BIMI1 record exists. With no record, has_bimi_record and valid are false and issues_found holds BIMI_LOOKUP_FAILED. If DNS gives no answer at all, the call returns a 503 rather than a "no record" verdict. Results are cached for 30 minutes. On the Free plan bimi_record, svg_logo and vmc_certificate are removed.

What people use it for

Deliverability Audit Reports

Email deliverability consultants check client domains for valid BIMI records and configuration issues before launching sender authentication and inbox branding campaigns.

Sender Domain Setup

When onboarding new marketing senders, email platforms inspect DNS for active BIMI records and return setup issues to verify brand readiness.

Brand Impersonation Defense

To catch broken branding assets, domain monitoring services track published BIMI records continuously and alert administrators whenever record validity drops to false.

Outbound Inbox Readiness

Inspect target sending domains during prospect list building to confirm who publishes valid BIMI records and protocol versions in DNS.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/bimivalidator

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

1
2

curl "https://api.apiverve.com/v1/bimivalidator?domain=ebay.com" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/bimivalidator

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

{
  "status": "ok",
  "error": null,
  "data": {
    "host": "ebay.com",
    "bimi_host": "default._bimi.ebay.com",
    "has_bimi_record": true,
    "bimi_record": "v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem",
    "bimi_records_count": 1,
    "version": "BIMI1",
    "svg_logo": {
      "url": "https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg",
      "status_code": 200,
      "valid": true,
      "file_size_bytes": 1518
    },
    "vmc_certificate": {
      "url": "https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem",
      "status_code": 200,
      "valid": true
    },
    "issues_found": [],
    "valid": true
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive BIMI Record Validator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — BIMI Record Validator API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1Data refreshed realtime