Syntax and cleanup
Parse the address, normalize safe variations, and report malformed input explicitly.
Email intelligence
Know what is behind an address.
Validate deliverability and turn technical mail signals into a structured profile your signup, lead, or account workflow can use immediately.
GET /v1/email/analyzeOne request. Deliverability, address, name, host, and server signals.Two levels of certainty
Validate first. Analyze when context matters.
Use the lightweight validation endpoint for an immediate gate, or request the complete analysis when downstream decisions need richer evidence.
DNS and MX
Resolve mail infrastructure and return ordered server records in a stable structure.
Mailbox availability
Use safe checks to determine whether the destination is likely to accept mail.
Address characteristics
Identify disposable providers, temporary inboxes, role accounts, and graylisting signals.
Name inference
Separate likely first and last names where the local part provides credible evidence.
Host reputation
Describe known mailers, catch-all behavior, provider context, and reputation.
Representative request
Artificial data, realistic shape.
The example uses the reserved .example namespace and does not identify a real person or organization.
REQUEST
GET /v1/email/analyze?email=demo-user-1042%40research.example Authorization: Bearer YOUR_API_KEY
RESPONSE
{
"email": "demo-user-1042@research.example",
"status": "deliverable",
"cleanedEmail": "demo-user-1042@research.example",
"metrics": [
"valid_syntax",
"known_mailer",
"has_mx",
"mailbox_exists"
],
"address": {
"isDisposable": false,
"isGraylisted": false
},
"name": {
"value": null,
"firstname": null,
"lastname": null
},
"host": {
"value": "research.example",
"provider": null,
"catchAll": false,
"isKnown": true,
"reputation": "high"
},
"server": {
"exists": true,
"records": [
{
"exchange": "mx1.research.example",
"priority": 10
}
]
}
}
Designed for decisions
Keep policy in your product.
Maail reports observable signals and a clear status. Your application decides which evidence is required for each workflow.
Block obvious failures
Reject malformed or undeliverable addresses before creating an account.
Improve lead context
Separate business, personal, academic, and role-based addresses.
Protect sender quality
Keep temporary and low-quality destinations out of important campaigns.
Make address quality explicit.
Use the same response shape in forms, imports, CRM enrichment, and account security.