Verify an email domain API

Resolve a public domain and report whether nameserver, address, and MX records were found. MX presence does not mean a mailbox exists.

The Verify an email domain operation is part of the Email & Domain Intelligence API on BRAINIAC.software. Resolve a public domain and report whether nameserver, address, and MX records were found. MX presence does not mean a mailbox exists. It is exposed as POST /api/v1/email-domain/verify and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Public DNS resolution. Public RDAP registration data. The domain's TLS certificate on port 443 and public crt.sh certificate transparency results. Limitations: No test message is sent and no mailbox login is attempted. Syntax and MX records do not show that a mailbox exists. Missing records, lookup failures, and malformed records are separate results. Reputation stays unavailable because no unauthenticated public reputation verdict is queried. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Validate email syntax, Check MX records, Analyze an SPF record, Check DKIM records. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/email-domain/verify

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/email-domain/verify" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "domain": "gmail.com"
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Email & Domain Intelligence APIFull docsHow it works