I'm using Amazon SES where doesn't allow high bounce rate. They will suspend sending emails when the user make large amount of bounces. So I want to keep bounce rate low as possible.
So, here's my question: Is it good idea to lookup DNS MX and A record of the domain part of destination address (e.g. example.com) for every emails before sending? Is there any bad side effect of this approach? Or do you have any other better typical solution?
More information about my situation
Sometimes my customers enter wrong addresses. for example, when they seem want to enter email@example.com but sometimes it went wrong such as jane.doe@example, which .com part is missed.
In such case, bounces will be returned after 840 minutes because SES keeps email which have destination of jane.doe@example, will arguably never be delivered successfully.
The problem is, SES keeps the emails that never be delivered successfully for 840 minutes long, after that the emails will be returned as bounces, so my bounce processing mechanism which implemented as explained in https://sesblog.amazon.com/post/TxJE1JNZ6T9JXK/Handling-Bounces-and-Complaints can't get any feedback immediately. eventually, I got thousands of hard bounces, that make my bounce rate higher.