Short answer: standard email verification does not send an email. It opens a conversation with the recipient’s mail server, asks whether the mailbox exists, and disconnects before any message is written, so the person never receives anything. The exception is send-based verification, such as Scrubby’s Deep Verification, which sends a real blank message from the verifier’s own infrastructure, never your domains, to resolve addresses that a handshake cannot answer.
What a Standard Check Actually Does
Most verification, including the first pass in most tools, runs in this order:
- Syntax and domain checks. Is the address well formed, and does the domain exist?
- MX lookup. Is the domain set up to receive email at all?
- SMTP handshake. The verifier connects to the mail server, names a sender and a recipient, and reads the reply to the recipient step. Then it ends the session.
The message itself, the part that would land in an inbox, is never sent. Our explainer on how SMTP verification works walks through the handshake line by line.
Why Some Verification Does Send Email
The handshake only works when the server answers honestly. A catch-all domain says yes to every address, and some servers queue mail and bounce it hours or days later. For those addresses, the only reliable evidence is what the server does with a real message.
That is what Deep Verification does: it sends a blank message to each address in the batch and watches how the server responds over 72 hours, including the delayed bounces an instant check never sees. Quick Verification does not send email. It adds a catch-all probe and secure email gateway detection to the standard checks, and settles most catch-all addresses without a send.
The Methods Compared
| Method | Sends a message? | Can the person see anything? | Uses your sending domains? |
|---|---|---|---|
| Syntax, domain and MX checks | No | No | No |
| SMTP handshake | No | No | No |
| Scrubby Quick Verification | No | No | No |
| Scrubby Deep Verification | Yes, a blank message | Possibly, a blank email | No, Scrubby’s own infrastructure |
Myth: “Verifying My List Will Hurt My Sender Reputation”
Verification traffic does not come from your mailboxes or your domains, so it does not touch the reputation you send campaigns from. What hurts your reputation is the opposite: sending campaigns to addresses nobody checked, then collecting the bounces on your own domains.
The real trade-off with send-based checks is time, not reputation. Deep Verification needs up to 72 hours for its final verdict, so most teams run Quick Verification on the whole list first and send only the unresolved remainder to Deep. Our guide to how long catch-all verification takes covers how to plan around that window.
FAQ
Will the person know I verified their email address? Not with a standard check. No message is delivered, so there is nothing for them to see. Their mail server may log the connection, as it logs every connection it receives.
Is the blank message from Deep Verification sent from my domain? No. It is sent from Scrubby’s own warmed infrastructure. Your domains and mailboxes are never used.
Can I verify an address without sending anything at all? Yes, for most addresses. Quick Verification resolves most of a list, including most catch-all addresses, without sending email. Send-based checks are only needed for the remainder.
How do I try it? Scrubby includes 200 free credits, enough to run a sample of your list through both checks. See pricing.
Amit S.
Marketing Lead