Cold email list verification

The four checks, and what each one actually proves

Syntax proves the address is shaped like an address. Nothing more. A domain check proves the domain can receive mail somewhere. A disposable-domain check proves the provider is one that creates throwaway mailboxes. An SMTP conversation proves the receiving server currently accepts the recipient, which is the strongest of the four and also the most fragile, because it reflects a moment in time.

None of them proves consent, ownership or intent. A perfectly valid address can belong to someone who never wants your email, and that is a legal and reputational question, not a technical one.

• Syntax: catches typos and malformed data from imports.
• Domain routing: catches expired domains and dead hosts.
• Disposable: catches throwaway providers and role addresses you may not want.
• Recipient conversation: catches mailboxes that do not exist right now.

Verification exists to keep one number low; bounce rate explains how to read it when it rises anyway.

Import is where verification belongs

Run the checks at import, before the addresses reach a campaign. A list that enters the system already classified is easier to govern than one that is verified later under time pressure, and it stops invalid addresses from being counted in the audience you plan around.

Classify into three outcomes rather than two. Sendable, unsendable, and unknown. The unknown group is the one that decides quality: if you include it to keep the numbers large, you have re-imported the problem you paid to remove.

If you would rather start from a checked source, verified B2B leads supplies leads that have already been through verification.

A worked import

A file of 4,000 rows arrives from a conference list. Syntax removes 120. Domain routing removes 60 more, mostly domains that expired after the event. Disposable and role filtering removes 180. The recipient conversation runs on the remaining 3,640: 3,200 accept, 140 reject, 300 cannot be confirmed.

The sendable list is 3,200. The 300 unconfirmed addresses are held, not sent. If the campaign had included them, roughly one in twelve would have bounced, which is enough to change how the sending domain is treated. Holding them cost nothing except a smaller number.

• Keep the original file; never overwrite the source with the cleaned version.
• Store the classification per address so a later campaign does not repeat the work.
• Re-check the unknown group once, later, rather than including it now.

Re-verify close to the send

Lists age. A file verified in January is not verified in June, because people change jobs and mailboxes close. For cold outreach, re-run the cheap checks immediately before a campaign and the recipient conversation on any segment that has been sitting for weeks.

Worked example: a list verified six weeks earlier produced a 9 percent hard-bounce rate on a fresh send. Re-checking the same file found that one company's domain had moved to a new mail provider and was rejecting everything for a week. Removing that domain restored a normal rate for the rest of the campaign.

Verification is one line of the deliverability checklist; the rest still applies.

Keep a verification record you can reuse

A verification result is only useful if it carries a date and a method. Store, per address, when it was checked, which checks ran, and what each returned. Without that, a later campaign either repeats the work or trusts a result that may be months old.

Classification codes help more than a single valid flag. Distinguish a mailbox that accepted the recipient, a domain that cannot receive, a disposable provider, and an address that could not be confirmed at the time. Those four lead to different decisions, and collapsing them into “invalid” throws away the information that would let you retry intelligently.

Write the re-check policy down. For cold lists, re-check anything older than a few weeks before a send, and re-check the unconfirmed group once rather than including it. The policy is more valuable than any single result, because it keeps the list honest over time.

• Store date, method and result per address.
• Keep unconfirmed addresses separate from invalid ones.
• Re-check before a send, not only at import.
• Verification is also a speed control. Cleaning a list before a campaign means the first hundred sends are representative, so you learn whether the message works instead of learning which addresses are dead.

Check, what it catches and what it cannot catch

Each check answers a narrow question. None of them answers whether the recipient wants the email.

Frequently asked questions