Yes. Verify the list before the first campaign goes out, not after the first bounce report lands in your inbox. When you take on a new client, the list usually arrives from them as a spreadsheet, a CRM export or a folder of old event sign-ups, and nobody in the room can tell you how old half of those addresses are. Send to that file from a brand-new domain and you can damage the domain's reputation in a single afternoon.
Plenty of agency owners hesitate here, and the doubt is usually about automated email list cleaning legitimacy. Is it a real safeguard, or a paid service that quietly deletes good contacts? It's a real safeguard. It's cheap insurance against the one mistake that copy, design and timing can't fix later. But it only works when it runs at import, sits alongside warmup and suppression, and is understood for what it can't do.
This piece covers what goes wrong when an unverified list meets a new domain, exactly what verification checks and how, where it falls short, and when it should run. You'll finish knowing what to tell a client who asks why you won't just send to everything they gave you.
Verify before the first send, because the client's list is the biggest unknown in the launch
Everything else in a launch is something you control. You write the copy, you pick the send time, you set up the domain. The list is the one input you didn't make, and it's the one that decides whether mailbox providers trust you from day one.
Think about where a client's list actually comes from. A dental practice hands over every patient email since they switched booking systems in 2017. A florist exports a till system that captured addresses for receipts. A B2B consultancy pulls contacts from a CRM where sales reps typed addresses from business cards. Some of those people have changed jobs, closed accounts or mistyped their address at the counter. Some never agreed to marketing at all.
Now pair that with timing. The first campaign is when a sending domain is at its most fragile, because providers have nothing to judge it on except what happens in the first few sends. A bad result early sticks. That's why verification belongs in onboarding, next to domain setup, rather than in a clean-up task you get round to in the second quarter.
One bad import can damage a new sending domain faster than any copy mistake
A weak subject line costs you some opens on one campaign. A bad list costs you inbox placement on the next ten. The difference comes down to bounces and what providers infer from them.
A hard bounce is a permanent failure. The mailbox doesn't exist, the domain is gone, or the server refuses the address outright. A soft bounce is temporary, such as a full mailbox, a server that's briefly down or a message the receiving side wants to slow down. Soft bounces sort themselves out or convert to hard bounces after repeated failures. Hard bounces are the ones that hurt, because a sender who keeps mailing addresses that don't exist looks like a sender who bought, scraped or neglected their list.
Mailbox providers don't publish a hard bounce threshold, and anyone quoting you an exact cut-off is guessing. Our working rule is simple. If a single send produces hard bounces above about 2%, stop and fix the list before anything else goes out. On a fresh list that has been verified, you should see far fewer than that.
A brand-new domain has no history to absorb a bad send. An established domain with years of clean sending can take a rough campaign and recover. A domain sending its first few hundred messages has only those messages as evidence. That's why automated domain warmup starts with small volumes and builds up, and why warming a domain on an unverified list wastes the warmup. You're building reputation with one hand and burning it with the other.
The damage rarely arrives as a dramatic block. It shows up as mail quietly routed to spam folders, as providers accepting messages slowly or deferring them, and as open rates that sag for no visible reason. By the time the client notices, several campaigns have gone out under a cloud.
Why the agency, not just the client, carries the risk
The client gave you the list, but the client won't remember that when the report shows poor results. They'll remember that they hired you to run email and the email didn't work. Then the recovery work lands on your team. Pausing sends, re-warming, splitting out engaged contacts and explaining it all on a call eats retainer hours you'd rather spend on campaigns that make the client money.
Automated email list cleaning legitimacy: what verification actually checks
Verification is legitimate, and it doesn't harm a good list. A reputable verification process never sends an email to your contacts. It checks each address against public records and the receiving mail server, then labels it valid, invalid, risky or unknown. Your contacts never see anything.
The checks run in a sensible order, from cheapest to most involved.
- Syntax. Is it shaped like a real address? This catches missing @ signs, spaces, double dots and typos like gmial.
- Domain exists. Does the part after the @ resolve to a real, registered domain?
- Mail exchange records. MX records are the DNS entries that tell the internet which server accepts mail for a domain. No MX record usually means no inbox.
- Mailbox response. The checker opens a conversation with the receiving server and asks whether it would accept mail for that address, then ends the conversation before any message is sent.
- Disposable domains. Throwaway inbox services that self-destruct after a few hours get flagged.
- Role addresses. Addresses like info@, admin@, sales@ and support@ reach a shared inbox or a team, not a person who signed up, so they complain more and engage less.
- Duplicates. The same address entered twice, or in different capitalisation, gets merged so nobody receives two copies.
Each step removes a different kind of problem. Syntax and duplicates are tidiness. Domain and MX checks catch dead businesses and typos in the domain. The mailbox response catches people who've left a company or closed an account. Disposable and role flags catch addresses that technically work but are bad bets for a marketing send.
If you want the cost-benefit case for B2B lists specifically, we've written up whether automated email list cleaning is worth it for B2B agencies, including how to handle company domains.
Verification has limits, and knowing them stops you trusting a clean report too much
Verification proves an address can receive mail. It says nothing about whether the person wants your mail. Keep that sentence in your head and you'll avoid the main ways a clean report misleads you. Here are the four gaps worth explaining to every client.
Catch-all domains accept everything and bounce later
A catch-all domain is set up to accept mail for any address at that domain, real or not. Ask its server whether jane@ exists and it says yes. Ask about xyz123@ and it also says yes. The checker can't tell real from fake, so these come back as risky or unknown. Some of them bounce days later, after the server has had a proper look. This is the usual answer when a client asks why a verified list still produced bounces. Treat catch-all results as a separate segment and send to them in small batches once the domain has some history.
Spam traps look like valid addresses
A spam trap is an address run by a mailbox provider or a blocklist operator to catch senders with poor list practices. Some are old addresses that were abandoned and later reactivated as traps. Others were never used by a person at all. They answer a mailbox check exactly like a real inbox. Verification catches some known traps but not all of them, and nobody can promise otherwise. Old lists and scraped lists carry the highest risk.
Real addresses that never consented
An address can pass every check and still belong to someone who never agreed to hear from your client. Verification doesn't fix that, and it doesn't make an inherited list GDPR-compliant. Under GDPR and similar rules, what matters is how and when the person gave permission, and whether your client can show it. If the client can't say where a segment came from, don't send to it until they can. That's a practical stance, not legal advice, and a client with a large or messy list should talk to someone qualified.
Data decays after the check
People change jobs, abandon inboxes and let domains lapse every week. A list verified in January is already slightly worse by March. B2B lists decay fastest because job changes kill work addresses. A verification result has a shelf life, which leads straight into when to run it.
Run verification at import, not as a quarterly clean-up
The right time to verify is the moment an address enters your system, and again whenever you're about to wake up contacts you haven't mailed in months. A quarterly clean-up checks the list after the damage has already been done.
There are three checkpoints worth building into your process. First, when the client's spreadsheet arrives, verify it before it's imported as live contacts, so invalid and disposable addresses never reach a send. Second, before any send to a segment that's been untouched for three months or more, re-check it, because those addresses have had time to decay. Third, at the sign-up form, catch typos and fake entries as they happen.
One-off bulk cleaning works in a pinch, but it relies on someone remembering to export the list, upload it to a separate service, download the results and re-import them. That's four steps where a file gets out of date or a column gets mangled. Checking that's built into the import flow removes those steps. The file goes in once and comes out sorted.
The form is the checkpoint agencies forget. A form with no protection collects bot submissions, fake addresses and typos that pass syntax checks but go nowhere. If you protect sign-up forms from bot submissions and add double opt-in where it suits the client, bad addresses never enter the list at all. That's cheaper than cleaning them out later, and it gives you a consent record as a bonus.
Verification works best as one layer alongside warmup, throttling and spread across domains
A verified list stops you mailing addresses that don't exist. That's all it does. It doesn't control how fast you send, which domain you send from, or who must never hear from the client again. Other layers handle those jobs, and each one covers a gap the rest leave open. Leave one out and the remaining layers carry more risk than they should.
- Verified list: invalid, disposable and duplicate addresses come out before they bounce.
- Warmed domain: small daily volumes build a history, so providers have evidence before the big sends start.
- Dispatch speed per provider: each mailbox provider and receiving domain gets mail at a pace it accepts, instead of 20,000 messages landing on one provider in five minutes.
- Volume across several domains: brand-matched sending domains share the load, so no single domain carries every campaign.
- Platform-wide suppression: unsubscribes, hard bounces and complaints stay blocked across every list, so nobody who opted out gets mailed again after a fresh import.
Spreading volume across several sending domains starts to matter once a client sends in the tens of thousands. If one domain carries everything and a campaign goes badly, every message the client sends suffers. With the load shared, a dip on one domain doesn't drag the others down. It won't hide a bad list, though. Providers judge recipients and content as well as the domain, so a dirty list spread across four domains damages four domains.
Clean lists also keep your reporting honest. Corporate mail filters open and click messages to check them for threats, and those security scanner opens push open rates up on B2B lists in particular. Take out the dead addresses and filter out scanner activity, and the open rate on the client's report counts people. That's the number you want to defend on a monthly call.
A clean list is worth more than a big one, which answers the 'what is 1,000 emails worth' question
To whoever sends to it, a bought or scraped list of 1,000 addresses is worth less than nothing. Those addresses bring hard bounces, spam traps and complaints from people who never heard of the sender. They also eat into the reputation of a domain you spent weeks warming. And because nobody on a bought list gave consent, the list fails the GDPR question before deliverability even comes into it.
A list of 1,000 people who signed up and still open is worth whatever those subscribers buy, and that depends on the trade. A thousand past clients of a wedding venue, a thousand customers of a café and a thousand finance directors at software firms are three very different assets. There's no honest per-subscriber figure that covers all three, so don't give clients one, and don't promise what a campaign will bring in. Tell them what you'll measure instead: clicks, bookings and replies from the people who really are on the list.
The more useful question is which part of those 1,000 holds the value. Split the list by what people did on past campaigns. People who clicked are your strongest segment. People who opened but didn't click are interested but not yet convinced. Non-openers go last, get a short re-engagement send, and are suppressed if they stay silent. On a new domain, send to the clickers first. Their engagement gives providers the good signals the domain needs before the wider list goes out.
The questions clients ask about spam, phishing and monitoring have straight answers
These come up on onboarding calls, often from the client's own office staff. Here are short answers you can pass on as they are.
How can I clean my email from spam?
There are two sides to this. In your own inbox, unsubscribe from legitimate senders you no longer want, mark real junk as spam so the filter learns, set up filters for repeat offenders, and never reply to unknown senders, because a reply confirms your address is live. As a sender, take role, disposable and dead addresses off your list so your own mail isn't treated as spam. A list full of unreachable addresses makes even a decent campaign look careless to the providers filtering it.
Can I get phished just by opening an email?
In an up-to-date mail client, opening a message carries little risk on its own. The danger comes from clicking links, opening attachments or typing a password or card number into a page the email sends you to. Loading images is different. It can tell the sender your address is live, which is why some people set their mail client to block remote images by default. Keep your software updated and check where a link points before you click it.
How do I tell if my emails are being monitored?
Marketing email commonly carries a tracking pixel, a tiny image that records an open when it loads, and tracked links that record clicks. Blocking remote images cuts most open tracking, though tracked links still record clicks. On a work account, your employer may monitor mail under its own policy, and the IT team or staff handbook will tell you what applies. Corporate security systems also open and click incoming mail to scan it, which is the reason raw open rates overstate how many people actually read a campaign.
How SendTo builds verification into the launch so agencies do not have to bolt it on
SendTo is an email marketing platform you run under your own brand, so every check in this article happens inside the product your clients see as yours. Here's what we handle for you.
We verify addresses before sending, so the checks run on every campaign without you exporting files to another service. List imports map spreadsheet columns automatically and pick up where they left off if an upload gets cut off halfway, which matters when a client hands over a 40,000-row export. Platform-wide suppression applies across every list, so an unsubscribe stays an unsubscribe after a re-import. New sending domains get automated warmup. We set dispatch speed per provider and per domain, and we spread campaign volume across several brand-matched sending domains.
Sign-up forms come with bot protection, either embedded on the client's site or hosted on a landing page, with optional double opt-in. Reports leave out security scanner opens, so the client portal and your partner view show real human opens, clicks and bookings. You can also build segments from clicks, unclicked opens and non-openers on past campaigns, which is how you send to the most engaged people first.
Some honest limits. We can't make an inherited list consented. That still depends on where your client got the addresses. No checker can tell real from fake behind a catch-all domain either, so those addresses still need careful, small sends. You sell the platform at prices you set, and our own costs are on the pricing page.
Your next step: make verification part of every client onboarding, and earn from recommending the platform that does it
Put this checklist into onboarding, so it happens before the first send for every new client, not after a bad report.
- Verify the import: run every client file through verification before it becomes live contacts.
- Remove role and disposable addresses: flag role addresses, decide client by client, and drop throwaway domains.
- Confirm the consent source: ask where each segment came from and hold back any segment the client can't account for.
- Warm the domain: build volume gradually before the full list goes out.
- Send to the most engaged segment first: recent clickers go first, then openers, then everyone else in stages.
Five steps, done once per client, protect the domain, the reporting and your retainer hours. If you write about email, advise agencies or recommend tools to them, you can also earn from pointing them to a platform that already does all five.
Refer agencies to the platform that verifies, warms and suppresses for them, and earn 20% of their partner subscription every month they pay.
Join the SendTo affiliate programme
