BIMI Record Validator API

GET

Know whether any domain can display verified logos in email inboxes.

BIMI Validator checks if a domain has a valid BIMI record published in DNS. BIMI enables domain owners to display verified logos in supported email clients.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/bimivalidator?domain=ebay.com

Query parameters

domainstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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
  }
}

About the BIMI Record Validator API

This API performs a DNS TXT record lookup for the BIMI policy at default._bimi.{domain}. It verifies the structure of the BIMI record, the presence of the 'v=BIMI1' tag, and checks for a valid SVG logo URL and optional VMC (Verified Mark Certificate) reference.

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
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use BIMI Record Validator

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the BIMI Record Validator API.

Read the docs →

What specific BIMI components does the validator check?

It queries the TXT record at default._bimi.{domain}, verifies the v=BIMI1 tag, and checks the SVG logo URL and file size. It also inspects optional Verified Mark Certificate references and returns a list of any syntax or configuration issues found.

Are BIMI records cached or checked live against DNS?

Every check runs in real time. BIMI Record Validator queries the live DNS TXT records at default._bimi.{domain} and attempts to fetch the hosted SVG logo and certificate directly when requested.

How far does the Starter plan go for domain validations?

Starter provides 200,000 credits each month, which covers 20,000 domain validations at 10 credits per call. That works out to about $1.50 per 1,000 checks, or $0.0015 per call. The Free plan includes 20 validations per month.

Are SVG logo and VMC certificate details included on the Free plan?

No. The Free plan confirms whether a BIMI record exists and reports basic validity, but complete record content, SVG logo status, and VMC certificate details require a paid plan starting with Starter.

Will validation fail if a domain does not publish a VMC certificate?

No. Verified Mark Certificates are optional in BIMI records. If a domain publishes a valid record with only an SVG logo URL, the API still validates the record syntax and logo file without flagging the missing certificate as a failure.

Can I show BIMI validation results inside my own deliverability dashboard?

Yes, as long as you are on a paid plan. You can run checks for your users and display the findings inside your monitoring tools, email platforms, or security audits. Reselling the raw lookup data directly as a standalone feed is not permitted.

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

Parameter	Type	Example	Description
`domain`Required	string	`ebay.com`	The domain to validate the BIMI record for domain

Example request

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.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

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.

Sample response

{
  "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.

Field	Type	Example	Description
`host`	string	`"ebay.com"`	The domain name that was validated
`bimi_host`	string	`"default._bimi.ebay.com"`	The BIMI DNS record host location
`has_bimi_record`	boolean	`true`	Whether a BIMI record exists for domain
`bimi_record`Premium	string	`"v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238…`	The complete BIMI DNS record content
`bimi_records_count`	number	`1`	Number of BIMI records found in DNS
`version`	string	`"BIMI1"`	BIMI protocol version identifier, e.g. BIMI1; absent when the domain publishes no BIMI record
`svg_logo`Premium	object	`{...}`	SVG logo validation details
`url`Premium	string	`"https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg"`	URL where the SVG logo is hosted
`status_code`Premium	number	`200`	HTTP status code when fetching SVG logo
`valid`Premium	boolean	`true`	Whether the SVG logo file is valid
`file_size_bytes`Premium	number	`1518`	Size of SVG logo file in bytes
`vmc_certificate`Premium	object	`{...}`	VMC certificate validation details
`url`Premium	string	`"https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem"`	URL where the VMC certificate is hosted
`status_code`Premium	number	`200`	HTTP status code when fetching certificate
`valid`Premium	boolean	`true`	Whether the VMC certificate is valid
`issues_found`	array	`[]`	Validation issues discovered during the check; absent when the record is valid and no issues were found
`valid`	boolean	`true`	Overall validity status of BIMI record

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.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

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

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

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.

Plan	Per month	Credits	BIMI Record Validator calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

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.

Compare all pricing tiers →

Call it from cURL — GET /v1/bimivalidator

No SDK to install — this is a plain HTTPS call to /v1/bimivalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

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

Resources

GitHubapiverve/bimivalidator-apiSource, issues and the examples this page is built from.ReferenceBIMI Record Validator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/bimivalidatornpm APIVerve.API.BIMIRecordValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/bimivalidator

Install the Node.js SDK, then call the BIMI Record Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/bimivalidator

Node.js

const res = await fetch("https://api.apiverve.com/v1/bimivalidator", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/bimivalidatorThe published Node.js client, versioned and signed.GitHubapiverve/bimivalidator-apiSource, issues and the examples this page is built from.ReferenceBIMI Record Validator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.BIMIRecordValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/bimivalidator

No SDK to install — this is a plain HTTPS call to /v1/bimivalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/bimivalidator",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/bimivalidatornpm APIVerve.API.BIMIRecordValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/bimivalidator

Install the C# / .NET SDK, then call the BIMI Record Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.BIMIRecordValidator

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/bimivalidator");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.BIMIRecordValidatorThe published C# / .NET client, versioned and signed.GitHubapiverve/bimivalidator-apiSource, issues and the examples this page is built from.ReferenceBIMI Record Validator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/bimivalidatornpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/bimivalidator

No SDK to install — this is a plain HTTPS call to /v1/bimivalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/bimivalidator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/bimivalidatornpm APIVerve.API.BIMIRecordValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/bimivalidator

No SDK to install — this is a plain HTTPS call to /v1/bimivalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/bimivalidator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/bimivalidatornpm APIVerve.API.BIMIRecordValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/bimivalidator

No SDK to install — this is a plain HTTPS call to /v1/bimivalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/bimivalidator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/bimivalidatornpm APIVerve.API.BIMIRecordValidatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

DNS Lookups: A Developer's Debugging GuideDNS problems cause connection failures and email issues. Learn how to use DNS lookups to diagnose problems faster.Read

WHOIS Data: Domain Intelligence for Business and SecurityWHOIS data reveals domain ownership, age, and infrastructure. Use it for lead qualification, research, and fraud detection.Read

BIMI Record Validator API

Try it — live request, no key required

About the BIMI Record Validator API

What people use it for

Ways to call it

Other ways to use BIMI Record Validator

Questions.

Request parameters — GET /v1/bimivalidator

Required

Authentication

Response — GET /v1/bimivalidator

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/bimivalidator

Resources

Also published for

Call it from Node.js — GET /v1/bimivalidator

Resources

Also published for

Call it from Python — GET /v1/bimivalidator

Resources

Also published for

Call it from C# / .NET — GET /v1/bimivalidator

Resources

Also published for

Call it from Go — GET /v1/bimivalidator

Resources

Also published for

Call it from PHP — GET /v1/bimivalidator

Resources

Also published for

Call it from Ruby — GET /v1/bimivalidator

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — BIMI Record Validator API

Domain Data

Related articles

Ready to build with BIMI Record Validator? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog