Info Endpoint

Checks the provided email address

Request Method: GET
Request URL: https://api.emailvalidation.io/v1/info

Request Parameters

Parameter	Type	Mandatory	Description
apikey	string	️	Your API Key
email	string.	️ ️	The email address you want to check
catch_all	boolean		If set to 1 we check if the email domain is a catch-all enabled domain (Only available in higher up plans)

Sample Response

{
    "email": "support@everapi.com",
    "user": "support",
    "domain": "everapi.com",
    "smtp_check": true,
    "mx_found": true,
    "did_you_mean": "",
    "role": true,
    "disposable": false,
    "score": 0.64,
    "free": false,
    "format_valid": true,
    "catch_all": false
}

MX Check

The Simple Mail Transfer Protocol (SMTP), which is the very same protocol we all use to move emails on and across networks, is used by the emailvalidation.io API to verify email addresses.

By determining whether the requested domain is set up to accept email, our system starts the process of real-time email verification. Here is where the MX-Records check in the API is useful. The mx found response object of the API will inform you if MX-Records for the specified domain have been located.

Example

{
    ...
    "mx_found": true,
    ...
}

SMTP Check

Next, an SMTP request is made to the mail server responsible for the given email address. The crucial element that eventually reveals whether the specified email address genuinely exists is the ensuing SMTP dialogue.

Although sending emails may appear to the end user to be as simple as pressing a button, sending emails from one server to another involves moving a sizable quantity of data back and forth. One reason why more and more businesses are choosing to use an email verification service like the emailvalidation.io API is that email servers frequently have a tendency to behave in extremely unforeseen ways and generate issues out of nowhere.

Example

{
    ...
    "smtp_check": true,
    ...
}

"Did you mean" Check

In the "did you mean" object of the API result set, the emailvalidation.io API will propose a different email address if a potential misspelling or mistake in the requested email address's domain portion is identified.

Please be aware that the email address in the did you mean object is just a recommendation and has no bearing on the other API response objects.

Example

{
    ...
    "did_you_mean": "support@emailvalidation.io",
    ...
}

Catch-All Detection

One SMTP check is not the end of the real-time verification procedure used by the emailvalidation.io API. A catch-all detection mechanism has been created since many email servers are set up to catch (accept) all incoming mail traffic, independent of the local component of the requested email address.

This functionality is disabled by default due to the significant negative impact it has on the API's response time. However, you can enable catch-all detection by adding the request URL's catch all option and setting it to 1.

Depending on whether the requested email address is discovered to be a part of a catch-all mailbox, the catch all JSON object in the API response will either return true or false.

Example

{
    ...
    "catch_all": true,
    ...
}

Tip

Please take note that the catch-all JSON response object will return null if the catch-all parameter of the API is not active.

Disposable Check

If the requested email address is discovered to be utilizing a disposable email service like mailinator.com or trashmail.com, the API will also return a disposable JSON object with the values true or false.

Example

{
    ...
    "disposable": true,
    ...
}

Services for Disposable Emails

A disposable email service enables users to anonymously create temporary email identities that are often used only once for tasks like activating accounts or getting passwords and expire after a set amount of time. Many of these email services don't require users to register, therefore the inbox of these one-time email accounts is made available to the public. We strongly advise against adding these email addresses to your recipient list.

Free Email Provider Check

The emailvalidation.io API can recognize free email services like Gmail, GMX or Yahoo since it is connected to a regularly updated database that lists all available email providers.

The free JSON object in the API response will either return true or false depending on whether the given email address is discovered to be utilizing a free service.

Example

{
    ...
    "free": true,
    ...
}

Even while free email addresses are typically included in recipient lists, it might make sense for some email campaigns to separate them out and only deliver to addresses with a specific domain.

Role Check

Determining whether the requested email address is a role email address is another step in the emailvalidation.io email verification procedure. A role email is an address that often refers to a function rather than a person or name (for example, "support" or "postmaster"). Due to the low open rates of this sort of email address, it could occasionally be undesirable when sending email campaigns.

Example: If the requested email is a role address, the role JSON object in the API response will return true; otherwise, it will return false.

Example:

{
    ...
    "role": true,
    ...
}

Quality Score

The API will return a numeric Quality Score ranging from 0 (Bad) to 1 (Good), reflecting the quality and deliverability of the given email address, to complete the emailvalidation.io validation & verification procedure.

Based on a system that gets smarter with each email address validated, this Quality Score is determined for each requested email address.

Example:

{
    ...
    "score": 0.64,
    ...
}

It is impossible to draw clear distinctions between recipients who are "worth sending to" and recipients who are "not worth sending to" because the validity of the numeric quality score depends heavily on the sort of email approach you are making. However, the following rules seem reasonable to us:

For transactional email:

Score	Quality
1.00-0.65	Perfect
0.64-0.33	Medium
0.32-0.00	Poor

For marketing email:

Score	Quality
1.00-0.80	Perfect
0.79-0.49	Medium
0.48-0.00	Poor

Tip

Please be advised that when deciding whether or not to send an email to an address, the Quality Score should only be used as a guide.