I am currently trying to get the api to block emails that don’t actually exist, that way you avoid spellcheck errors and stuff.
However, when i’m feeding it a gmail address that i know does not currently exist (checked with the create an account page), it still returns valid.
For example, the email ‘andfnkdshk3@gmail.com’ returns valid when submitted to the API. If you go to create an account in gmail, as of the posting of this, you will see that is a name free to choose.
Does this API only validate domains? Or should it check emails too?
Join in the discussion - add comment below:
Hi,
The only way to test that is to actually deliver an e-mail, otherwise the API endpoints would quickly be blocked for spamming.
The API checks the username part of the e-mail too (if submitted), but only checks it against suspicious bots, disposable addresses, or abusive behaviour, not regular typos.
For example, the e-mail “workeractua.l.l.y1.57.9 AT gmail.com” is blocked by the API.