Cold Email Verification
Clean the list before the first send, not after the damage is done.
The Problem
Cold outreach is the one channel where you have no prior relationship with the recipient and no permission signal to lean on. Every send is judged on the raw mechanics: did the address exist, did the mailbox accept it, did anyone engage. When a meaningful share of your list is dead, the mechanics turn against you fast.
What a bounce actually costs you
A hard bounce is not a neutral event. Mailbox providers log it against the sending domain and the sending IP. A prospecting list assembled from scraped sources, exports from an old CRM, a partner spreadsheet, or a purchased database will contain addresses of people who left the company two years ago, addresses that were never real, generic inboxes nobody reads, and throwaway domains that stopped resolving. Send to all of them and you are telling the receiving provider, in the clearest language it understands, that you do not know who you are mailing.
The consequences compound in a specific order:
- Bounces accumulate against the sending domain, and filtering gets stricter for every future message from it.
- Messages that used to reach the inbox start landing in spam, so replies drop even from the good addresses on the list.
- Spam traps and long-abandoned addresses that were recycled into traps can get the domain listed on a blocklist.
- Once a domain is burned, warming a replacement takes weeks, and the sequences you already scheduled are running into a wall the whole time.
Why cold lists rot faster than anything else
People change jobs. Companies get acquired and consolidate domains. Aliases are retired. A cold list is a snapshot of who worked where at the moment it was built, and it starts decaying the same day. Lists bought or shared between teams are worse, because you inherit someone else's decay on top of your own.
The trap of guessing
The usual instinct is to send anyway and let the sequencing tool report the bounces. That works exactly once. By the time the tool has told you which addresses were dead, the receiving providers have already recorded the attempt and adjusted how they treat you. Bounce data is a post mortem, not a safeguard. The other instinct, running the list through a tool that marks everything green so the report looks clean, is worse: it hands you false confidence and you send with it.
Cold email works when the list is tight, the domain is trusted, and the send volume matches the quality of the data behind it. Verification is what makes those three things line up before the first email leaves.
The Solution
Mailthentic verifies a cold list before you load it into your sequencer, so the addresses that would have bounced never reach a mailbox provider in the first place.
The checks that run on every address
- Syntax: malformed addresses, stray characters and broken local parts from scraping and CSV exports.
- Domain and MX records: the domain must resolve and actually publish mail exchange records. Dead companies and parked domains get caught here.
- Disposable detection: a maintained set of known temporary and throwaway email domains are flagged.
- Role-based flagging: maintained prefixes such as info@, admin@, support@ and sales@. These are shared inboxes, not people, and on cold outreach they are usually a complaint waiting to happen.
- Catch-all detection: domains that accept every address are identified as catch-all.
- Mailbox probing: an SMTP conversation with the receiving server, with the response code recorded.
Where we tell you the truth instead of a number you want
Some domains are catch-all: the server accepts every address it is offered, whether the mailbox exists or not. No verifier on earth can confirm an individual mailbox behind a catch-all domain. Mailthentic reports these as catch-all or unknown rather than dressing them up as valid, so you can decide the risk yourself instead of finding out at send time.
The same applies to Gmail, Google Workspace, Outlook and Microsoft 365. Those servers return 250 OK even for addresses that do not exist, as a deliberate defence against harvesting. A mailbox on those providers cannot be confirmed by SMTP, and we say so rather than guessing.
Greylisting is handled properly too. A 421, 450 or 451 response is a temporary deferral, not a rejection. Mailthentic retries with a backoff instead of throwing away a perfectly good address because a server asked it to come back later.
The workflow
Upload the list as a CSV and Mailthentic removes duplicates before processing, so you are not charged for the same address twice. Every result comes back with the status, the reason, the SMTP response code and a confidence score, so you can build your own send rules: mail the confirmed addresses, hold the catch-alls for a lower volume test, drop the invalid and disposable ones entirely.
If your prospecting data lives in a CRM, connect Brevo, HubSpot, Salesforce, Mailchimp or PlusVibe and run the round trip: pull the list, verify it, write the verdicts back so the dead records are marked at the source. Verification runs on pay-as-you-go credits governed by the current expiry terms shown on pricing, or on a monthly plan. Contact data is never sold, shared or reused, and the service is GDPR aligned.
Key Benefits
-
Protect the sending domain you spent months warming, by catching bounces before the first send instead of reading about them afterwards
-
Every result carries the status, the reason, the SMTP response code and a confidence score, so you decide what to send to
-
Catch-all domains are reported honestly as catch-all, never inflated into false green ticks that bounce at send time
-
A maintained set of disposable domains and maintained role-based prefixes flagged, so shared inboxes and throwaways stay out of your sequences
-
Greylisting deferrals are retried with a backoff, so good prospects are not discarded because a server asked us to wait
-
Bulk CSV or real-time API, with duplicates removed before processing so you are never charged for the same address twice
Frequently asked questions
Why verify a cold list before sending instead of just letting the sequencer report bounces?
Can you confirm a Gmail or Outlook mailbox exists?
What is a catch-all domain and what should I do with those addresses?
Should I remove role-based addresses like info@ and sales@ from a cold list?
What happens to duplicates in my upload?
Can I verify prospects directly in my CRM?
Ready to get started?
Start with 50 free verification credits. No credit card required.