Look up a domain’s MX and DMARC records
Inspect mail routing and the presence of a DMARC TXT declaration before configuring a domain.
3 credits · USD $0.003
Input schema
{
"type": "object",
"properties": {
"domain": {
"type": "string",
"maxLength": 253,
"x-maxUtf8Bytes": 253
}
},
"required": [
"domain"
]
}Request
curl -X POST 'https://staging.callmint.dev/v1/email-domain' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Idempotency-Key: unique-request-001' \
-H 'Content-Type: application/json' \
-d '{"domain":"example.org"}'Response result
{
"domain": "example.org",
"mx": [
"0 ."
],
"dmarc": [],
"note": "DNS records only; does not verify a mailbox, SPF or DMARC policy correctness."
}Limitations
Uses a fixed Cloudflare DNS-over-HTTPS resolver, never the supplied domain as an HTTP destination. Maximum 20 records per result and 32 KB per DNS response. NXDOMAIN/no records is successful data and billed. Resolver errors/timeouts are not billed. Does not verify mailbox existence, SPF or DMARC policy validity. DNS examples are illustrative and can change.
All enabled routes accept a JSON object of at most 60,000 UTF-8 bytes. String limits are also measured in UTF-8 bytes.