WhoisXML Email Verification API provides additional value to our corporate email security
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
- 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.
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.
