Sender rules from Google's email sender guidelines. Postmaster Tools changes from Google's Postmaster Tools help pages. Data decay rate from Cognism research (via Cleanlist.ai). The 2% bounce ceiling, warmup volumes and recovery timelines are working guides from common deliverability practice. Updated October 2026.
Most B2B teams are trying to keep their email bounce rate under 5%. That threshold is already too late. Deliverability practitioners treat a sustained hard bounce rate above 2% as a warning sign: mailbox providers read high bounces as a sign of a poor list, and the damage to sender reputation affects every email you send from that domain, not just the ones that bounced. By the time your bounce rate is visibly climbing toward 5%, your domain reputation has usually been degrading for weeks.
There is a second problem that most guides miss entirely: in late 2025, Google retired Postmaster Tools v1 — the dashboard that showed your domain reputation as High, Medium, Low, or Bad. Many B2B teams are now sending blind, without the early warning system they relied on for years. Sales emails are landing in spam. There is no clear signal explaining why.
This guide gives you the exact framework to keep hard bounce rates under 1.5% — verified data sourcing, domain setup, list hygiene protocol, and the recovery path if you are already in damage territory. For Indian market teams: catch-all domains are common at Indian companies, and they are a frequent cause of unexpected bounce spikes for teams sourcing Indian contacts. We cover this in depth below. How CookLeads handles this →
The High/Medium/Low/Bad domain reputation dashboard no longer exists. To check your domain reputation in 2026: use Google Postmaster Tools (compliance data + spam rate), Talos Intelligence (Cisco's reputation view), and MXToolbox (blocklist checks). If you have not checked all three in the last 30 days, check now — before your next campaign.
Sources: Google's email sender guidelines (0.3% spam rate); Cognism research via Cleanlist.ai (22.5% annual decay). Bounce ceiling, volume and recovery figures are working guides.
Why 2% Is the Real Threshold — Not 5%
The "keep bounce rate under 5%" rule that circulated in B2B outbound communities for years was calibrated for an older email infrastructure. Google's sender guidelines (enforced since February 2024) set hard limits on spam complaints — keep your spam rate below 0.3% — and require authentication, but mailbox providers also weigh bounces when judging a sender. In practice, a sustained hard bounce rate above 2% is where filtering risk climbs sharply — and that filtering applies to all emails from the domain, not just the cold outreach that caused the bounce spike.
The mechanics matter here. Reputation is tracked per sending domain, so sustained high bouncing can suppress all emails from that domain. This means your onboarding emails, your invoices, your support replies — everything from that domain faces reduced inbox placement while your domain is flagged. The cold outreach that caused the problem has contaminated your entire sending infrastructure.
A single campaign with a 15% bounce rate can damage your sender reputation for two to four weeks. Recovering a damaged domain reputation typically takes between four and twelve weeks, depending on the severity of the damage. Severe damage or blocklisting can take 3–6 months. The cost-benefit analysis is not close: a verified contact list costs a fraction of a month of degraded deliverability across your entire email infrastructure.
The Catch-All Problem: Why Indian Corporate Emails Spike Your Bounce Rate
Most bounce rate guides address the problem as if all email infrastructure works the same way. It does not. Indian company email domains — particularly at SMBs and mid-market companies — are often set up as catch-all. A catch-all domain accepts every email sent to it at the mail-server check, even addresses that do not exist. Standard verification tools mark these addresses as "valid" because the server accepted the connection.
Catch-all addresses that standard verifiers return as valid carry real bounce risk. When you actually send to a catch-all address that has no valid mailbox, the email bounces after delivery — which means the bounce counts against your sender reputation even though verification passed. Lists verified more than 6 months ago also carry more invalid addresses, simply because contact data decays.
For Indian market teams sourcing contacts via ZaubaCorp, Tofler, or DIN lookup, this catch-all risk tends to show up in specific company types: manufacturing firms with legacy IT setups, smaller professional services firms, and family-owned businesses that have not upgraded their email infrastructure. The CookLeads 7-stage purification engine includes a dedicated catch-all check, so these addresses are flagged before they reach your sequence. Full methodology: CookLeads Data Purity →
The 5-Layer System for Keeping Bounce Rate Under 1.5%
Keeping bounce rate below 1.5% consistently is an infrastructure problem, not a one-time list cleaning problem. Contact data decays at roughly 2% a month (about 22.5% a year, per Cognism research) as people change jobs and companies close. The solution is a layered system — verification at sourcing, domain architecture that isolates cold outreach from business email, sending volume disciplines, monitoring triggers, and a recovery protocol if something goes wrong.
The single largest mistake B2B teams make is verifying email lists once during list building and then using the same verified list for 3–6 months. Contact data decays at roughly 2–3% per month. A list verified 6 months ago has lost 12–18% validity — far above a safe 2% bounce rate before you send a single email.
The correct approach is verification at the moment you reveal the contact — running the full check when the contact is requested, not when the list was built. CookLeads' 7-stage purification engine runs when you reveal a contact, so each contact is checked when you get it, not months earlier. That is different from tools that verify once at collection and cache the result.
Your primary domain (yourcompany.com) must never be used for cold outreach. Domain reputation follows the domain — not the IP, not the ESP. If your primary domain gets flagged by Gmail or Outlook, every transactional email your company sends is affected: onboarding sequences, invoice emails, customer support replies, investor updates.
Use secondary sending domains: trycompany.com, getcompany.co, usecompany.io. Warm each domain over 4–6 weeks before cold outreach. Cap volume at 30–50 cold emails per day per domain — one inbox per 30–50 cold emails per day is the safe volume rule in 2026. When a secondary domain shows degraded reputation signals, pause and investigate without touching your primary domain sending.
A new or recovered sending domain cannot immediately handle 500 emails per day. Mailbox providers watch volume patterns — sudden spikes from a domain with no history trigger spam filters before any bounce analysis even runs. The warmup protocol is non-negotiable.
Standard warmup ramp for a fresh domain: Start at 5–10 emails per day in week 1, send to highly engaged contacts who will reply and open. Double volume each week while engagement metrics stay healthy (open rate above 20%, complaint rate below 0.05%, bounce rate below 0.5%). By week 4–5, you can reach 30–50 cold emails per day. Tools like Instantly and Smartlead have built-in warmup infrastructure — use it, do not skip it.
For recovered domains after a reputation hit: same protocol, but more conservative. Start at 2 emails on Day 1 and reach 30–40/day by Day 30. After Day 14, maintain a 1:1 warmup-to-campaign ratio. If bounce rates exceed 2% or complaints spike above 0.1%, pull back immediately and hold for 3–5 days before resuming.
Google retired Postmaster Tools v1 in late 2025. The familiar color-coded reputation dashboard (High/Medium/Low/Bad) no longer exists. Teams that relied on it for early warning signals are now operating without a critical diagnostic layer.
The replacement monitoring stack for 2026: Google Postmaster Tools (new version) for compliance data and spam rate trends. Talos Intelligence (Cisco) for the Talos reputation score on your sending domain. MXToolbox Blacklist Check for blocklist status across major RBLs. Your ESP's bounce dashboard — set up email alerts for any campaign exceeding 1.5% bounce. Inbox placement testing (GlockApps or Mail Tester) monthly — place a test send across Gmail, Outlook, Yahoo, and Apple Mail to check actual folder placement before live campaigns.
If your bounce rate has already exceeded 2% and campaigns are landing in spam: stop all outbound from the affected domain immediately. Every additional send during active reputation damage extends recovery time.
Authentication Is Table Stakes — SPF, DKIM, DMARC in 2026
Without proper email authentication, your domain reputation starts at a disadvantage regardless of how clean your contact list is. Gmail and Outlook now require SPF, DKIM, and DMARC from bulk senders (5,000+ emails a day), and Gmail requires at least SPF or DKIM from everyone — not as a recommendation but as a condition for standard inbox delivery. Getting these wrong means bounce rate issues are compounded by authentication failures.
| Record | What It Does | Recommended Setting (2026) | Risk If Missing |
|---|---|---|---|
| SPF | Authorises which servers can send email from your domain. Prevents spoofing. | v=spf1 include:[ESP] ~all | Higher risk of spam filtering or rejection |
| DKIM | Cryptographic signature proves the email came from your domain and was not modified in transit. | 2048-bit key per sending domain. Rotate every 12 months. | DMARC alignment failures, reduced inbox rate |
| DMARC | Policy that tells receiving servers what to do when SPF/DKIM fail. Required for Gmail bulk sending. | Start: p=none (monitoring). Move to p=quarantine after 30 days clean reporting. | Required for bulk senders (5,000+ emails/day); delivery problems without it. |
| Custom Tracking Domain | Tracks opens and clicks through your own domain rather than a shared ESP domain. | Separate CNAME per sending domain (track.yourdomain.com) | ESP's shared tracking domain may be on blocklists from other senders |
Configure auth records in your DNS provider. Verify with MXToolbox →
The List Hygiene Calendar — What to Do and When
One-time list cleaning is not a hygiene practice — it is a band-aid. Contact data decays at roughly 2–3% per month. At 2.5% monthly decay, a list of 10,000 verified contacts loses 250 valid addresses every 30 days. By month 6, you have lost 1,500+ valid addresses — and if you send to the full original list, you are sending to 1,500+ addresses that may bounce. A maintenance calendar treats list quality as an ongoing operational discipline, not a quarterly project.
- Remove hard bounces from previous campaign
- Remove unsubscribes and spam complaints
- Check sending domain MXToolbox status
- Verify bounce threshold alert is set at 1.8%
- Check Postmaster Tools spam rate
- Review ESP bounce and complaint dashboard
- Segment contacts by last engagement date
- Flag contacts with 3+ soft bounces for removal
- Run inbox placement test (GlockApps / Mail Tester)
- Re-verify contacts not emailed in 60+ days
- Remove contacts with zero opens in 6 months
- Talos Intelligence reputation check
- Full list re-verification from scratch
- Audit catch-all domains — remove high-risk ones
- Review and rotate DKIM keys if approaching 12 months
- Benchmark bounce rate vs industry by segment
How CookLeads Removes Bounce Risk at the Source
Most of the bounce rate hygiene work described in this guide — re-verification schedules, catch-all classification, monthly list cleaning — exists because contact data was not verified properly at the point of sourcing. The correct solution is to fix the problem upstream: source contacts that are verified when you reveal them, not contacts that require ongoing maintenance because they were never properly checked.
The CookLeads 7-stage purification engine is built to catch the most common causes of B2B bounces: expired addresses, catch-all domain risk, duplicate and trap addresses, and incorrect mail routing. The "No Mobile, No Charge" policy applies the same principle to direct dials: you use 1 credit only when a verified mobile is found.
For Indian market teams specifically: The CookLeads Chrome extension works on ZaubaCorp, Tofler, InstaFinancials, FileSure, Falconebiz and TheCompanyCheck, so contacts sourced from Indian company registries go through the same 7-stage purification engine — including the catch-all check that basic verifiers skip. Full verification methodology →
Need Contacts That Don't Bounce?
7-stage purification engine. No Mobile, No Charge. Or have our custom lists team build your ICP list — email us and we call back within 24 hours. Custom lists →
Frequently Asked Questions
What is a good email bounce rate for B2B cold outreach in 2026?
What happens when my email bounce rate exceeds 2%?
What is a catch-all email domain and why does it matter for B2B prospecting?
How long does it take to recover from a damaged email domain reputation?
Do I need SPF, DKIM, and DMARC for cold email outreach?
What is the difference between hard bounce and soft bounce?
How often should I re-verify my B2B email list?
What replaced Google Postmaster Tools v1 for tracking domain reputation?
Can I send cold email from my primary company domain?
What causes sudden email bounce rate spikes?
How does the "No Mobile, No Charge" policy reduce B2B prospecting costs?
Sender rules from Google's email sender guidelines; Postmaster Tools changes from Google's help pages. Data decay rate from Cognism research via Cleanlist.ai. Bounce ceilings, warmup volumes and recovery timelines are working guides from common deliverability practice. Updated October 2026. All third-party tool names (Gmail, Google Postmaster Tools, Talos Intelligence, MXToolbox, Instantly, Smartlead, GlockApps) are trademarks of their respective owners. CookLeads is an independent B2B sales intelligence platform operated by Humanzo Technologies Private Limited, Gurugram.