3 ms·
Hey, thanks a lot for testing. Since gmail.com is legit domain, I don't think I could flag it as disposable. But, the API does return normalised gmail address
by 42newuser 2y ago
Hey, thanks a lot for testing. Since gmail.com is legit domain, I don't think I could flag it as disposable.
But, the API does return normalised gmail address which you can use to create a unique hash column on your database to prevent any signups using that same gmail address!
For example. u.s.e.r+platform@gmail.com will be normalised to "user@gmail.com" and you can save this unique value to database and prevent signups using "u.s.e.r+platform1@gmail.com", "u.s.e.r+platform2@gmail.com" etc
- chrisjj 2y ago> Since gmail.com is legit domain There is the start of the problem. Mailinator.com is equally legit. > I don't think I could flag it as disposable. Agreed. But your service would simply push your targets to use gmail.com.
- 42newuser 2y agoThe purpose of this project is to let developers take informative decision, like they can allow/deny access to service based on all the returned fields. This doesn't vouch for allowing or blocking any particular services. In my case, I refuse access to my services if the user is using a known temp mail service. If they're using "labeled" gmail service, I simply save the hash of normalised gmail to database and prevent any further signups using different labels.
- chrisjj 2y ago> The purpose of this project is to let developers take informative decision, like they can allow/deny access to service based on all the returned fields. Sounds good, but the blurb does give a slightly different impression: "Features: - Detect disposable email addresses"
- 42newuser 2y agoThanks a lot for the feedback. Technically it does detects disposable emails and returns a bunch of other validations along with API response. However, I will try to improve the wordings on next revision. Thanks!