How to Verify Emails Scraped From Resumes and Job Boards Before You Send
To verify emails scraped from resumes or job boards, remove duplicates, sort out obvious parsing errors, then run the list through a bulk verifier and send only to valid rows first. Sourced data picks up errors at each step, and the order below keeps the cleanup short. The email list cleaner does the first pass in your browser, and the email verification for recruiters page covers the mailbox check.
Step 1: remove duplicates
One candidate often arrives from several boards. Paste the addresses into the duplicate email remover so each is checked once. If candidates appear under more than one address, see finding duplicate contacts with different emails.
Step 2: spot the parsing errors
Look for addresses that were cut or merged. Common signs are a domain with no dot, a trailing character that does not belong, or two addresses in one cell. The multiple emails in one cell splitter separates the last case. Fix typo domains with the email typo corrector.
Step 3: separate personal and work addresses
Personal addresses outlast jobs; work addresses do not. Use the free email providers list to see which domains are webmail. A work address from a past role is the one most likely to return Mailbox not found. For the same split in lead lists, see personal emails in a B2B lead list.
Step 4: run the mailbox check
Upload the cleaned CSV on the verify page. Each row gets a syntax check, an MX lookup and a mailbox check, and comes back with one of these reasons where it applies:
- Mailbox not found, No mail server and Typo domain are invalid; drop them.
- Disposable address is invalid too, and rarely a real candidate contact.
- Accepts all addresses and Role address are risky; hold them back from the first wave.
Step 5: send in waves
Send the valid rows first and read the bounce count before the next wave. Then test risky rows in a small batch. Our guide to verifying candidate and client emails explains why client contacts need re-checking more often than candidates.
A note on using scraped data
Whether you may contact someone depends on your country, theirs and how you got the address. Verification does not answer that, and this post is not legal advice. Check the rules that apply to your outreach before you send.
What this cannot do
- It confirms that an address can receive mail, not that it belongs to the right candidate.
- Yahoo and AOL accept mail for any address during the check, and Microsoft consumer mailboxes are not probed, so they come back risky.
- Results confirmed in the last 14 days are reused at no cost, but an address can change after that.
Check your sourced list
Upload it on the verify page: the first 100 email checks are free with a Google sign-in, no card. For lists that arrive every week, see list cleaning and pricing.
Common questions
How do I verify emails scraped from resumes?
Export them to a CSV, remove duplicates, then run them through a bulk verifier. Each address comes back valid, risky or invalid with a reason, and you send only to the valid rows first.
Why do emails from resume parsers fail so often?
Parsers can cut an address at a hyphen, merge it with surrounding text, or pick up an old address from a past job. The result looks like an email but may not exist.
Should I remove duplicates before or after verifying?
Before. The same candidate often appears from several boards, and removing duplicates first means you check each address once.
Is it a problem to email people who did not apply to me?
Rules differ by country and by how the data was collected, so check the rules that apply to you. Verification only tells you whether an address can receive mail, not whether you may use it.
Are role addresses like jobs@ worth keeping?
Not for personal candidate outreach. They are shared inboxes, and the role address filter sets them aside.
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.