verify email address exists without sending
Verify email address exists without sending
Check for mailbox existence through DNS and SMTP signals while keeping the user inbox untouched.
This workflow is useful when you want to avoid sending confirmation mail too early.
It can reduce bounce rates before the first message leaves your system.
It should be combined with a good risk score and domain checks.
220 mail.example.com ESMTP
EHLO emailverify.se
MAIL FROM:<[email protected]>
RCPT TO:<[email protected]>
QUITCan this prove ownership?
No. It indicates reachability and response behavior, not human ownership.
Why use it?
It helps you reduce spammy signups and bad CRM records before activation.
What SMTP probing actually proves
SMTP probing is a protocol conversation with the recipient domain. It can indicate whether a mailbox appears to accept mail, but it also reflects server policy, temporary throttling, anti-abuse behavior, and catch-all handling.
How to use it safely
Keep probing on the server, add timeouts, respect provider limits, and avoid repeated retries against the same domain. In production, you should store only the resulting status and score, not the full transcript.
FAQ
How do I use this page?
Use it as a quickstart reference and link it from your docs, onboarding flow, or marketing page.
What should I do next?
Create an account, try the demo, and move the integration into your backend with a real API key.
Can SMTP confirm the owner is real?
No. It only suggests that the mailbox path looks reachable at the time of the check.
Why not send a message instead?
Because many products need a quiet validation path before onboarding or import completes.