2 ms·
Disclaimer: I don't work for Experian. I suspect only one of their devs could answer this affirmatively. There are different approaches. As a sibling comment m
by smt88 6y ago
Disclaimer: I don't work for Experian. I suspect only one of their devs could answer this affirmatively.
There are different approaches. As a sibling comment mentioned, you can use any login protocol that responds with a different message for users vs. non-users.
Off the top of my head, you have POP, IMAP, SMTP, OAuth, Gmail's undocumented HTTP API, Gmail's documented HTTP API, and web scraping.
You probably can't do any of those at scale.
To solve the scale issue, you could buy databases of verified email addresses, which are not expensive. For any address found in those databases, you know it's registered.
If it's not in your database, you can do a live check.
Alternatively, you could make a business arrangement with Google, which is also possible for a company like Experian.
- greenyoda 6y agoI don't think you could use POP or IMAP, since these protocols are designed for a registered user to interact with a mail server - to connect, you'd first need to know the user's userID and password on that server (and the userID isn't necessarily related to the e-mail address, even though it may be on Gmail). And if you got back an error, you wouldn't know whether it was the userID or the password that was invalid. SMTP can be used, however, since that protocol is designed to be able to send messages to a user on any mail server. (See my earlier reply for an explanation of how this can be done with SMTP: https://news.ycombinator.com/item?id=24834067 https://news.ycombinator.com/item?id=24834067)