DNS · Developer Tools · 1 endpoint
Email Deliverability
Three checks, one answer: is the syntax real, is the domain disposable, and does it actually have a mail exchanger.
- Status
- Operational
- Price
- 1 credit / request
- Rate limit
- 120 / 60s
- Cache
- None
- Requests
- 2
Endpoint
How to call it
GET/v1/utility/email
Code
Request — cURL
v1
curl https://api.diraz.co.id/v1/utility/email \
-H "Authorization: Bearer drz_live_…"For AI agents
Callable through the MCP server with the same key:
call_api {"endpoint":"email-deliverability","params":{"email":"[email protected]"}}Parameters
- emailstring · required
- The address to check.
Example response
200 OK
JSON
{
"data": {
"input": "[email protected]",
"valid_syntax": true,
"email": "[email protected]",
"local_part": "someone",
"domain": "gmail.com",
"disposable": false,
"mx_present": true,
"mx_records": [{ "exchange": "gmail-smtp-in.l.google.com", "priority": 5 }],
"deliverable": true
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- valid_syntax / disposable
- Computed on the spot.
- mx_present / mx_records[]
- From live DNS — the domain's mail exchangers, when they exist.
- deliverable
- All three checks passed — the go/no-go for sending.
Errors
When something goes wrong
Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.
401 Unauthorized
JSON
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
Health
Is it up?
- Email Deliverability
1/1 passing