Why does email list verification matter for cold email deliverability?
Bounces damage the domains you send from, and with them every campaign after this one. Email providers read a high bounce rate as a sign of a careless sender and start filtering your mail to spam. In our own pre-launch checks, the most common reason a campaign failed was the list, not the copy: we have seen inherited lists bounce at over 20%.
What bounce rate thresholds are safe for B2B cold email?
Aim for under 2% before launch, and pause above 5%. These are the limits we apply to every Leadee campaign:
| Check | Limit | Action |
|---|---|---|
| Projected bounce before launch | 2% or less | Launch |
| Projected bounce before launch | Above 5% | Block; clean the list first |
| Catch-all, risky or unknown results | Above 10% of the list | Block; move them to a separate batch |
| Live campaign, 300+ people contacted | Bounces above 5% | Pause and fix the list |
| Live campaign, 100+ people contacted | Bounces at 8% or more | Pause and fix the list |
How do you verify a B2B email list? A step-by-step checklist
1. Re-verify the list right before you send (90-day rule)
Verify as close to launch as possible. An address that was valid three months ago may not be valid today. We re-verify anything not checked as safe in the last 90 days.
2. Send only to addresses marked valid
Verification tools return results such as valid (safe), invalid, catch-all, risky and unknown. Send to valid. Remove invalid. Treat the rest with care (next step).
3. Split out catch-all and unknown addresses
A catch-all domain accepts every address, so a tool can't confirm the person exists. Large Gulf companies and groups often run catch-all servers or strict security gateways. Keep these out of the first batch. Once the main list is sending well, test them in a small separate batch, and stop if bounces rise. Some teams also run a second, specialized check on catch-all addresses before sending.
4. Confirm the person still holds the role
People change jobs often in the UAE and Saudi Arabia. An address can be technically valid but belong to someone who has left, or now does a different job. Check current roles from a recent source before launch.
5. Match the company name to the email domain
If the company name and the email domain don't clearly match (for example, a personal email or an unrelated domain), move the contact to a review file instead of the first batch.
6. Remove duplicates by person, not just by email address
The same person often appears with two or more addresses. Remove duplicates using a stable identifier for the person (such as their LinkedIn profile), so nobody gets the same email twice.
7. Limit contacts per company
Send to no more than two people at the same company in one campaign, and never on the same day.
8. Remove role-based addresses
Generic addresses (info@, sales@, admin@) rarely reach a decision-maker at larger companies. Remove them for enterprise targets. At very small companies a generic address may reach the owner, but a named contact is still better.
9. Remove opt-outs and past bounces
Take out anyone who has unsubscribed or bounced before, across every campaign you run. The UAE's Personal Data Protection Law (Federal Decree-Law No. 45 of 2021), the DIFC and ADGM data protection rules and Saudi Arabia's Personal Data Protection Law all make honoring opt-outs more than good manners.
Why is UAE and Saudi B2B email data harder to verify?
Four reasons: fast job changes, catch-all company email systems, directory data full of generic addresses, and Arabic names spelled several ways in English.
- Job changes: roles move quickly in both countries, so data goes stale faster than many teams expect.
- Group and government email systems: catch-all settings and security gateways are common in large groups and government-related entities.
- Free-zone and directory data: lists built from public directories often contain generic addresses (info@, sales@) and old domains. Generic addresses rarely reach a decision-maker.
- Name spellings: Arabic names are written in English in several ways (for example Mohammed, Muhammad, Mohd). Guessed email patterns often miss because of this; verify every guessed address.
What else should be ready before launch?
Verification is one part of a launch check. Also confirm:
- Sending domains separate from your main domain.
- SPF, DKIM and DMARC set up on every sending domain.
- Inboxes warmed up before the first campaign.
- Copy that is relevant, short and plain text.
