from Hacker News

Show HN: Check whether an email address exists

by nateguchi on 4/10/18, 8:53 AM with 19 comments

  • by efficax on 4/10/18, 4:16 PM

    Email address validation is basically an impossible problem. In practice, the best strategy is:

        1. Check if email is wellformed, with an *extremely* lenient algorithm. Basically, do we have .*@.* ?

    2. Check that the domain is real, has an MX record, and the SMTP server in the MX record exists.
    Ok, send mail! The only way to verify after that is to send an email with a verification link and complete the circle.

  • by astura on 4/10/18, 4:04 PM

    Um... I hate to be so harsh but this is worthless. Checking a few of mine, all different domains, I got

    Nemesis ESMTP Service not available 554-No SMTP service 554-IP address is black listed.

    ---

    This domain has a catch all email address so we are unable to determine if this email matches an account.

    ---

    Error: Invalid greeting from server - 554 No SMTPd here This email does not exist or cannot be found

    ---

    Error: Invalid greeting from server - 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact XXXXXX This email does not exist or cannot be found

    So... yeah... 100% error rate on something that says "the results should be relatively trustworthy." Relative to what? That success rate doesn't even crack the Mendoza Line.

  • by mstolpm on 4/10/18, 9:34 AM

    Not working reliantly for me. Addresses that definitely exist are reported as not existing. No info on the checks used.

    So, this could even just be a clever way to collect email addresses through a simple form.

  • by jlgaddis on 4/10/18, 10:06 AM

    Heh, we all learned to disable VRFY 15-20 years ago.

    This fails both ways on my tests.

  • by Piskvorrr on 4/10/18, 9:54 AM

    Nope. Reports @example.[something] as existing, whereas info@[something else] - which regularly gets mail - as nonexisting. Both Type I and Type II failures, but confidently proclaims the verdict? Worse than useless: actively misleading.

  • by helb on 4/10/18, 2:33 PM

    It seems that some domains just kill the backend. For my work e-mail, and probably any other on the same domain, it returns HTTP 503 (service unavailable) after ~30s, and frontend is stuck at "Checking…" forever. Maybe our mailserver fights back the spammers somehow. :)

    Also, it kinda sucks that i can't send the query with Enter key, and i bet it sucks much more for eg. visually impaired users. Is there any particular reason you used bunch of <div>s instead of good old <form>?

  • by StubleU on 4/10/18, 3:19 PM

    We use Cisco's cloud Ironport solution for email spam protection and I get the following when I check my email address: Error: Invalid greeting from server - XXXXXXXXX.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.

  • by klez on 4/10/18, 8:57 AM

    A link to an "how it works" article would be nice.

  • by joeseeder on 4/10/18, 7:05 PM

    So it failed on my dynamical created email addresses

    I have a system where i have double wildcard so X@X.some.domain and your site fails

         Error: Spam detection in use
    This email does not exist or cannot be found

  • by avenoir on 4/10/18, 4:16 PM

    Worked for my person email attached to my domain. I agree with others in that explaining how this works would be very nice.

  • by 2fifty3 on 4/10/18, 4:32 PM

    Am using namecheap's email service for my personal email and domain, this says it is an invalid email address

  • by gvoncheap on 4/10/18, 4:21 PM

    Yea this has not validated an email for me. Tried a few email clients and nothing said it was valid.

  • by pinkskip on 4/10/18, 9:22 AM

    This is cool but yea some right up would be appreciated.