Enter a person’s name to generate every common address format on @zoom.us, then verify which one actually exists.
| Address | Format | |
|---|---|---|
| jane.smith@zoom.us | first.last | Verify → |
| j.smith@zoom.us | f.last | Verify → |
| jsmith@zoom.us | flast | Verify → |
| janesmith@zoom.us | firstlast | Verify → |
| jane@zoom.us | first | Verify → |
| jane_smith@zoom.us | first_last | Verify → |
| jane-smith@zoom.us | first-last | Verify → |
| smith@zoom.us | last | Verify → |
| smith.jane@zoom.us | last.first | Verify → |
| smithj@zoom.us | lastf | Verify → |
| s.jane@zoom.us | l.first | Verify → |
| janes@zoom.us | firstl | Verify → |
| jane.s@zoom.us | first.l | Verify → |
These are the address formats corporate mail systems commonly use. Which one Zoom actually issues can only be settled by checking whether the mailbox accepts mail.
Our engine opens an SMTP conversation with the @zoom.us mail servers and stops before delivery, so nothing lands in anyone’s inbox.
Sending to addresses you have merely guessed drives hard bounces, and mailbox providers read those as a stale list — which hurts placement for every recipient, not just the bad ones.
Building one address at a time is fine for a single prospect. If you have a list of @zoom.us contacts, upload it to the bulk email verifier and clean the whole file at once, or wire the real-time verification API into your signup and CRM flows so unverified addresses never enter your database in the first place.
New to this? Start with the guide to email verification APIs, or run a single address through the free email verifier.