Item: WhoisXML Email Verification API
Rating: 10
Author: Verified User

Overall Satisfaction with WhoisXML Email Verification API

Use Cases and Deployment Scope

We use WhoisXML Email Verification API to derive an added functionality from the email security system we currently have. In particular, WhoisXML Email Verification API enhanced the capability of our spam filters, as it automatically flags messages from disposable email addresses, which spammers could use.

Pros and Cons

Pros

WhoisXML Email Verification API obtains its disposable email detection capabilities from a disposable email domain database that monitors most disposable email providers regularly.
WhoisXML Email Verification API is compatible with most spam filtering solutions and other email security systems. It is also available as a Splunk application, so compatibility wasn’t an issue for us.

Cons

We had to avail ourselves of the custom plan because we have a pretty large user base, and each user receives hundreds of emails per day. We were able to come up with a reasonable agreement, in any case.

Most Important Features

Disposable email address detection
Generic email address detection
Mail server existence
Mailbox existence

Return on Investment

Enhances spam filtering, which helps keep malicious emails away. Having someone in our network falling for spam or phishing emails could be far more expensive in the long run.
Detects emails from disposable email domains, which are non-work-related.

Key Insights

Do you think WhoisXML Email Verification API delivers good value for the price?

Yes

Are you happy with WhoisXML Email Verification API's feature set?

Yes

Did WhoisXML Email Verification API live up to sales and marketing promises?

Yes

Did implementation of WhoisXML Email Verification API go as expected?

Yes

Would you buy WhoisXML Email Verification API again?

Yes

Likelihood to Recommend

We use WhoisXML Email Verification API for the additional value it provides to our corporate email security, and we recommend that most organizations do the same. Disposable email services may help protect the privacy of their users, but in the corporate setting, receiving emails from these domains may not be safe. So, aside from flagging emails from domains categorized as spam, we wanted our spam filtering system to be stricter and include disposable email addresses.

Comments

Please log in to join the conversation

WhoisXML Email Verification API provides additional value to our corporate email security