Email Verification API with Threat Detection

Data Avoidance

We act upon the principle of thrift data and data avoidance, which means, that we dont save your data. It's that simple. You can be 100% confident that your emails will touch our systems only during the validation process.

Real-time API

Our API is as complete as possible, with validations made at multiple levels: deliverability, response of the mail servers, disposable emails, catch all, free mailer and much more.

Threat Detection

Because we are an IP & Domain Data Intelligence Provider we are able to give you real time threat detection for any given email.

Verify the deliverability of email addresses with our comprehensive API.

Our Email verification API is as complete as possible, with validations made at multiple levels: deliverability, response of the mail servers, disposable emails, catch all, free mailer and much more.


  {
    "result": "deliverable",
    "message": "2.1.5 OK",
    "is_role": false,
    "user": "dennis",
    "email": "dennis@monapi.io",
    "is_free": false,
    "smtp_server": true,
    "is_catchall": false,
    "mx_records": true,
    "block": false,
    "domain": "monapi.io",
    "code": 250,
    "is_disposable": false,
    "is_greylisted": false,
    "threat_class": none
  }

Common questions about the Email Verification API

Q: What do you check for when verifying emails?

See below some important checks:

Recipient Check: We test the email address and see if it bounces or not.
Disposable Email Address: We check if the email address has a domain name used for temporary email addresses.
Freemail Email Addresses: We verify if the email address uses a webmail like Hotmail, Gmail aso.
Catch-all Email Domain: We check if the server has a catch-all policy which accepts all the email addresses
Role based user: We check if the user relates to a role like postmaster, administrator aso.

For a complete and detailed explanation refer to our API Documentation

Q: Do you send an email to do the verification?

The email verification API does the validation without sending an email, connecting directly to the SMTP server.

Q: How do you check for greylisting?

There is no specific recommendation as to the specific choice of 4yz code to be returned as a result of a greylisting delay. So we use a combination of 4yz codes and the SMTP messages to decide wether the email is greylisted or not. For that reason we provide the "is_greylisted" field.

Q: How do you recognize a possible threat?

We use the domain and the mx_record of the provided email and lookup our Threat Intelligence Database if it matches. Use the field "threat_class"
If you catch the email address on point of contact (Signup, Contact Form aso.), you could also provide an ip address of the user to check against our Threat Data API. This would give you an even better insight into the potential threat of that email.

Simple Email Verification API with Threat Detection