You bought or scraped a list of leads. Every row has a name, a company, maybe an email pulled from a Google Maps listing or a website footer. Nothing tells you which of those emails are about to bounce.
What this actor does, in one line: give it a list of website URLs, it visits each one and gives back every email it finds — plus two checks on each address: is it real (does the domain have a mail server?) and is it worth reaching out to (a named person on the company's own domain, vs. a generic info@ mailbox, vs. someone's personal Gmail)?
Input: a list of website URLs — the output of a Google Maps scraper, a LinkedIn export, or any CSV of leads you already have.
Output, per email found:
-
deliverability:mx_confirmed(the domain has a real mail server) orno_mx_record(the domain can't receive mail — this address is dead, skip it) -
address_type:corporate_personal(a named contact on the company's own domain — the good one),role_or_generic(info@, contact@ — still usable, just not a person), orpersonal_free_provider(a real person, but on gmail.com/yahoo.com, not the company) -
source:mailto(wired into a real clickable link — trust it) ortext(found as plain text — usually real too, but this is also where fictional example emails hide: found this the hard way testing against a well-known payments company's homepage, which surfaced a made-up customer email used in a product screenshot) - Whatever LinkedIn/X/Instagram/Facebook links are on the same page
What it deliberately doesn't do: a live SMTP handshake (actually connecting to the mail server to check one specific mailbox). Outbound port 25 is blocked on most infrastructure to stop spam — mine included, while building this. mx_confirmed is the strongest signal available without it; it's not a guarantee, and the README says so instead of pretending otherwise.
Top comments (0)