smtp ping email check
SMTP ping email check
A ping check is a controlled SMTP conversation that tests mailbox acceptance without sending mail.
It is more expensive than syntax checks but more informative than format-only validation.
It helps separate obvious garbage from addresses worth deeper review.
It should remain a backend-only workflow.
220 mail.example.com ESMTP
EHLO emailverify.se
MAIL FROM:<[email protected]>
RCPT TO:<[email protected]>
QUIT
Why ping at all?
It gives an extra signal when syntax and MX checks are not enough.
What should I log?
Store the result code and timing, not the raw SMTP transcript.
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.