I’m experiencing the same issue. When I use deep-email-validator to check invalid or “garbage” emails, it works perfectly on my local machine, correctly identifying them as invalid. However, after deploying the same code to an AWS server, the validator always returns that the email is invalid, regardless of whether it’s actually correct or not. I suspect this is related to SMTP port restrictions on AWS, which prevent the validator from performing mailbox-level checks in production.