HomeUse casesProtect sender reputation
Check first. Protect the domains you warmed up.
Warming up a domain takes weeks. A bad list can hurt it in a day. Email Finder Verifier doesn't send anything. It tells you which addresses we could confirm, so you can keep the rest out. Make that check a required step, and write it down.
Free while in beta. No card needed.
Key takeaways
- The job: keep bounces from burning domains and mailboxes, across every client list.
- The result: a written process your team follows, with the check built in.
- The honest part: checking is one part of deliverability. We can't promise inbox placement.
Last updated 16 Nov 2026
01The job
The job, and why it matters
Your sender reputation is like a trust score. Gmail, Outlook and other mailbox providers give it to the address and domain you send from. It decides how much of your mail reaches the inbox, and how much goes to spam.
It builds slowly and drops fast. Lots of bounces in a short time tell providers you don't check who you email. For an agency, that's a client's domain. For a founder, it's the only domain they have.
A process beats good intentions. Put the check in the process so nobody has to remember it.
02The workflow
How to do it with EFV
Make verify a required step
No list goes into a sequencer until it has been through EFV. Write that sentence in your onboarding doc. Apply it to every client, every time.
Treat catch-all as its own group
A catch-all domain takes mail for any address. EFV still checks the person and marks each result. Verified on a catch-all domain: send it like any other verified email. Not confirmed: leave it out.
Leave out what isn't confirmed
Not confirmed rows stay out of the send. Check them again in a few days, or find another contact at that company.
Re-check older lists before each re-send
People change jobs and inboxes close. A list that was fine last quarter may not be now.
Watch your own bounce rate
EFV can't see your campaigns. Watch bounces and spam complaints in your sending tool, and pause a campaign if the numbers jump.
03Results
What the results mean
| Result | Reputation-safe habit |
|---|---|
| Verified | Fine to include. Keep volume steady, and start slow on new domains. |
| Verified, catch-all domain | Send it like any other verified email. |
| Not confirmed | Leave out of this send. Re-check later. |
Also remove hard bounces from your list right away. A hard bounce is permanent, and it will never work.
Add the check step to your next list. Free while in beta.
Sign up for free04FAQ
Questions, answered
01Will EFV protect my domain on its own?
No. It gives you the information to keep unconfirmed addresses out. Your copy, volume and sending setup matter too. We can't promise inbox placement.
02Does checking an email affect my domain?
No. Nothing is sent from your domain, or to the person. You just get the answer back.
03How often should I re-check a list?
Before each re-send, and most of all for lists you haven't emailed in a while. How often beyond that is your call.
04What if I run many clients?
Run each client's list through the check, and use a separate API key per client. You can delete one without touching the rest.
05Should I send to catch-all addresses?
Verified on a catch-all domain: send it like any other verified email. Not confirmed: leave it out.
06Can I put this in an automated flow?
Yes. Verify takes one request per address, so you can add it to Clay, n8n, Make, Zapier or your own code.
06Keep going
Where to next
- Cold email agenciesCheck each client's list before it touches a mailbox you spent weeks warming up.
- Outbound-led foundersCheck a list before it goes to a new domain. Find the gaps, verify, then send.
- SDR and BDR managersCheck each list once, hand reps a clean file, and re-check old prospects before a re-send.
06Start today
Make checking a required step
Sign up with email or Google. No card. Your key and a ready-made first request are waiting. Need more later? Message us on Slack.