An example
maria@gmial.com
- The domain looks like a typo of a popular one.
Did you mean maria@gmail.com?
Check an address before you send to it. We look for typos, throwaway inboxes, shared addresses and domains that cannot receive mail.
maria@gmial.com
Did you mean maria@gmail.com?
Nothing wrong found. The domain accepts mail and the address has no warning signs.
Not a valid address, a domain that does not exist, or a domain with no mail server. Do not send.
It can receive mail, but it is a throwaway inbox, a shared address, or a likely typo. We suggest the fix when we can.
The domain’s DNS did not answer in time. Try again in a moment.
That the address is well formed, that its domain exists and has a mail server, whether it belongs to a throwaway inbox service, whether it is a shared address such as info@ or support@, and whether the domain looks like a typo of a popular one such as gmial.com.
No. To know that, a tool would have to open a connection to the recipient’s mail server and ask, which many servers refuse or answer falsely, and which can get the checking address blocked. We do not do it. So “looks good” means worth sending to, not guaranteed to arrive.
It is fine for a receipt or a reply. For a newsletter it is a poor target: it reaches a group, often with no one who asked for your email, and is more likely to be reported as spam.
Mail to addresses that do not exist bounces, and a high bounce rate damages your sender reputation, so later mail to real people is more likely to land in spam. Checking sign-ups and lists first keeps that rate low.
No. We look up the domain in public DNS to answer, and keep nothing about the address.
Yes, with a SendSend account: up to 100 addresses per request in the API and every library, in the command line, and in the dashboard.
Also free: check your domain’s SPF, DKIM and DMARC · verify addresses with the API