Don’t lose customers because of typos
Maximize deliverability with comprehensive verification
Mailgun performs a three-step validation check for each address we verify, including a check against the mailbox provider to determine if the address is valid.
Validation based on billions of sent emails
RFC states the formal rules for email addresses. However, in the real world ESPs accept addresses that are not RFC-valid, and reject addresses that are.
When we built our validator, we did based on real-world data + RFC spec to ensure more accurate validation.
Custom ESP grammar
All major ESPs have their own set up custom grammar that impact whether an email address is valid in the real world.
We’ve integrated custom grammar checks for Gmail, Hotmail, and Yahoo into our email validator and are always adding more custom grammar checks as we discover these rules.
Doesn’t meet Gmail’s local parts rules.
Meets local parts rules because dots are ignored.
“Did you mean gmail.com?” and other suggestions
People make typos all the time. Gmail.com can easily become gmal.com and when it does, you can miss out on connecting with that customer.
That’s why we built in a suggestion service into our email validation service. When we have a suggestion for a common typos, we’ll return it along with invalid status, so you can offer the suggestion to your user.
Avoid high risk addresses
Our email validation API is your first line of defense against high-risk recipients. When validating an email address, we check for role-based addresses or disposable email domains.
Other great features of Mailgun validation
- DNS lookups
- MX and A-record look ups
- Parse email address in bulk into local part and domain
- Avg. API response time < 500 ms
- Open source library if you want to build your own service