MX, SPF, and DMARC check

Enter a domain. This page asks public DNS for MX, SPF, and DMARC and nothing else. It does not fetch the website, a registry, or a paid mailbox check. Paste a full address if you have one: the browser keeps the part before @ and sends the domain only.

A domain with no MX cannot receive the mail you are about to send.
SPF without a hard fail lets other hosts send as that domain.
DMARC at none, or missing, means a failed check is not enforced.

GET /verify/domain

$0.02 per domain

Paid API

curl -i "https://verify-x402.okwithit9.workers.dev/verify/domain?domain=examp1e-billing.com"

curl -i "https://verify-x402.okwithit9.workers.dev/verify/domain?domain=examp1e-billing.com" \
  -H "PAYMENT-SIGNATURE: <payment>"

x402 and MCP

npx -y https://verify-x402.okwithit9.workers.dev/mcp/contact-verify-mcp.tgz

{
  "mcpServers": {
    "contact-verify": {
      "command": "npx",
      "args": ["-y", "https://verify-x402.okwithit9.workers.dev/mcp/contact-verify-mcp.tgz"],
      "env": {
        "EVM_PRIVATE_KEY": "0xYOUR_BASE_PRIVATE_KEY"
      }
    }
  }
}

MCP tool: verify_domain

Questions

Does this check the mailbox?

No. It reports mail-server and authentication records only. Age, lookalike, website, and registry signals are GET /verify/domain at $0.02.

What if DNS does not answer?

The page says the lookup did not finish. It does not treat a failed lookup as a missing record.

Is the domain stored?

No. The check is not written to application logs.