Why Candidate Emails Bounce, and What Each Bounce Reason Tells a Recruiter
A candidate email bounces for one of four reasons: the mailbox is gone, the address was typed or parsed wrongly, the domain has no mail server, or the receiving server would not confirm either way. Each calls for a different response, so the useful move is to read the reason, not just count the bounces. Run the sourced list through the bulk email checker and every row comes back valid, risky or invalid with a reason. Recruiters can see how this fits their work on the email verification for recruiters page.
The reasons, and what to do
| Reason on the row | What it usually means for a candidate | What to do |
|---|---|---|
| Mailbox not found | The person left that employer, or the address was never right | Drop it, and look for a personal address or another channel |
| No mail server | The domain has no mail setup, often a typo in the domain or a company that shut down | Check the spelling; if it is right, drop it |
| Typo domain | gmial.com, hotmial.com and similar | Fix it with the email typo corrector, then re-check |
| Disposable address | A throwaway mailbox | Treat it as a weak contact |
| Accepts all addresses | A catch-all domain, so no single mailbox can be confirmed | Test in a small batch, not the first wave |
| Role address | info@, jobs@ and similar shared inboxes | Not a person; leave out of personal outreach |
Where the bad addresses come from
Old employer addresses. A candidate sourced from a past role list may have been reachable at work only. When they move on, the mailbox closes, and every email to it bounces.
Guessed formats. An address built as first.last@company.com is a guess about how the company names mailboxes. If the company uses initials or a different order, it bounces. Our note on catch-all emails and what to do with them covers why some guessed addresses look fine until you send.
Parsing and typing errors. Resume parsers sometimes cut an address at a hyphen or merge it with the next word, and application forms are typed on phones. The typo correction guide shows the common patterns.
Why it matters for the rest of your outreach
Bounces count against the inbox you send from. A high bounce rate can hurt delivery of later messages, including those to candidates who would have replied. The bounce rate calculator shows where your list stands before you send.
A simple routine
- Export the segment you plan to contact from your ATS or sourcing tool.
- Upload the CSV on the verify page and download the valid rows.
- Send the first wave to valid rows only.
- Fix typos and retry them; test risky rows in a small batch.
- Mark invalid rows in the ATS so no sequence picks them up again.
Our guide to verifying candidate and client emails goes into how candidate and client records decay differently.
What this cannot do
- A valid result means the mailbox existed at the time of the check. A candidate can still change address later.
- Yahoo and AOL accept mail for any address during the check, and Microsoft consumer mailboxes (Outlook.com, Hotmail, Live) are not probed, so those rows come back risky.
- Verification does not tell you whether a candidate will reply, only whether the message can arrive.
Check your next outreach list
Upload it on the verify page: the first 100 email checks are free with a Google sign-in, no card. For larger or recurring lists, see bulk email verification and pricing.
Common questions
Why do candidate emails bounce?
Usually because the mailbox no longer exists, the address was mistyped or mis-parsed when it was entered, or the domain has no mail server. Old employer addresses are a common cause, because a work mailbox is often closed when the person leaves.
Is a bounce always the candidate's fault?
No. Many bounces come from the data path: a resume parser that cut an address short, a guessed first.last format, or a typo on an application form.
Can I tell before sending whether an address will bounce?
For most addresses, yes. A verifier asks the mail server whether the mailbox exists without sending anything. Some providers do not answer honestly, so those rows come back risky rather than valid.
What should I do with risky candidate addresses?
Hold them back from the first wave, then send small batches and watch the bounces. A risky row is not a bad address; it means the mailbox could not be confirmed.
How many free checks do I get?
The first 100 checks are free with a Google sign-in, no card.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.