---
title: "Cold Email Bounce Rate: The 5/9/10 Scale and the Domain Burn Line"
description: "Cold email bounce rate runs on two scales: campaign (under 5% healthy, 10%+ stop) and the 7% domain burn line. Q4 2026 data from 833.9K+ MailDeck inboxes."
canonical: "https://maildeck.co/blog/cold-email-bounce-rate"
last-updated: "2026-11-18"
---

> Cold email bounce rate runs on two scales: campaign (under 5% healthy, 10%+ stop) and the 7% domain burn line. Q4 2026 data from 833.9K+ MailDeck inboxes.

Guide

# Cold Email Bounce Rate: The 5/9/10 Scale and the Domain Burn Line

Nov 18, 2026 21 min read

Contents

Cold email bounce rate runs on two scalesThe campaign scale: what under 5%, 5-9% and 10%+ meanThe domain burn line: above 7% on one domainWhat drives cold email bounce rate upHow to reduce cold email bounce rate before it touches a domainBounce rate and the inbox type you send fromWhich setup fits your bounce numbersWhere MailDeck FitsMethodology

A healthy cold email bounce rate is under 5% per campaign, 5-9% means monitor closely and fix list errors, and 10%+ means stop. MailDeck tracks that campaign scale and a separate 7% burn line per sending domain, across 833.9K+ managed inboxes placing 98% of mail in the inbox in Q4 2026.

| Your bounce reading | Scale it belongs to | Verdict | Action today |
|---|---|---|---|
| Under 5% on a campaign | Campaign bounce rate | Healthy | Keep sending, verify each new list |
| 5-9% on a campaign (7% included) | Campaign bounce rate | Monitor closely, fix errors | Pull the bounced segment, re-verify it before the next step |
| 10%+ on a campaign | Campaign bounce rate | Stop | Stop the campaign today |
| Above 7% on one sending domain | Domain burn diagnostic | Domain is burning | Pause the domain, rotate in a warm reserve |
| 42% or 50% in Google Analytics | Website sessions with no engagement | Website metric | Read it separately from email |
| 42% or 50% on a cold email campaign | Campaign bounce rate | Dead list | Stop, verify the full list before any resend |

> As of Q4 2026, MailDeck infrastructure places 98% of cold email in the inbox across 833.9K+ managed inboxes sending 7.5M+ emails a day, so in the accounts we run, a bounce rate above 5% traces mainly to list quality.

## Cold email bounce rate runs on two scales

> In Q4 2026 MailDeck platform data across 1,200+ managed domains, the campaign bounce scale (under 5%, 5-9%, 10%+) and the domain burn line (above 7% on one domain) use different denominators and trigger different actions.

Sequencer dashboards report the campaign number: bounces divided by sends inside one campaign, across every inbox and domain that campaign uses. It tells you whether the list is clean enough to keep mailing. The domain number has to be built from a bounce export: bounces divided by sends from one sending domain, across every campaign that domain carries.

The two readings can disagree. In the agency case further down, one campaign blended to 3.8% across 60 domains in August 2026 and looked healthy on the sequencer dashboard while six of those domains carried a bad segment and sat above 7%. The reverse also happens: a campaign in the 5-9% band spread thinly over many domains can leave each domain below the burn line for a few days.

|  | Campaign bounce rate | Domain burn diagnostic |
|---|---|---|
| Unit measured | One campaign | One sending domain |
| Denominator | Sends in that campaign | Sends from that domain, all campaigns |
| Thresholds | Under 5% healthy, 5-9% fix errors, 10%+ stop | Above 7% bounce |
| Read together with | Reply rate, positive rate | Spam complaints above 0.3%, Postmaster reputation "Bad" |
| What it diagnoses | List quality | Domain reputation damage |
| Action when crossed | Clean or stop the list | Pause the domain, swap in a warm reserve |
| Where to read it | Sequencer campaign report | Bounce export grouped by sending domain, Google Postmaster Tools |

Cold lists are assembled from data providers and scraped sources, so a cold email bounce rate benchmark has to allow for data decay that an opt-in list never sees. The 5/9/10 scale above is the one MailDeck applies to cold sending, and the 7% line is the per-domain check that sits underneath it.

## The campaign scale: what under 5%, 5-9% and 10%+ mean

> In Q4 2026 MailDeck platform data, a sending domain under active load lasts 45 days to 2 months, and the campaign bounce scale exists to stop a bad list before it shortens that window.

### Under 5%: healthy

A good bounce rate for cold email is anything under 5% per campaign. Some bounce is unavoidable on cold data, because people change jobs and some catch-all servers accept mail at the gateway and reject it later. Keep sending, and suppress every hard bounce so it never reaches a second domain.

### 5-9%: monitor closely and fix errors

At 5-9%, something in the list is wrong. The usual causes are an old export mixed into a fresh pull, or a pattern-guessed batch (firstname.lastname@ applied to companies that use a different format). Find the segment the bounced addresses share, then re-verify it before the next sequence step fires. A 7% campaign belongs in this band as a list warning, and it turns into a domain problem when one domain carrying it crosses 7% on its own sends.

### 10%+: stop campaigns immediately

At 10% or more, stop the campaign the same day. Every further send at that rate adds bounces to the domains carrying it, and mailbox providers read a high invalid-recipient rate as a sign the sender bought or scraped the list. Restart after the full list has been verified, and restart on a small slice first.

### Hard bounce vs soft bounce in cold email

The hard bounce vs soft bounce split decides what you do with each address. SMTP servers answer with three-part status codes defined in [RFC 3463](https://datatracker.ietf.org/doc/html/rfc3463): a 5.x.x code is permanent, a 4.x.x code is temporary.

| Code | Type | Typical meaning | Counts toward campaign bounce | What to do |
|---|---|---|---|---|
| 5.1.1 | Hard | Mailbox does not exist | Yes | Suppress the address permanently |
| 5.1.10 | Hard | Recipient not found (Microsoft 365) | Yes | Suppress the address permanently |
| 4.2.2 | Soft | Mailbox full | Usually, after retries fail | Retry once, then suppress |
| 4.7.x | Soft | Temporary throttling or deferral | Only if retries fail | Lower per-inbox volume on that domain |
| 5.7.1 | Hard (policy) | Message refused on policy or reputation | Yes | Check authentication and domain reputation before resending |
| 5.7.26 | Hard (policy) | Authentication failed (SPF, DKIM or DMARC) | Yes | Fix DNS records before any further send |

Policy bounces in the 5.7.x family deserve separate attention. A 5.1.1 means the list is stale. A cluster of 5.7.1 responses from one receiving provider means the sending domain or its authentication has a problem, and that cluster feeds straight into the domain burn check. For the full list of codes with the action each one calls for, see the [SMTP error code reference for cold email senders](https://maildeck.co/blog/smtp-error-codes-cold-email).

## The domain burn line: above 7% on one domain

> At enterprise scale (100K+ emails a month), 10-20% of sending domains burn every month in Q4 2026 MailDeck platform data, and a bounce rate above 7% on one domain is one of the burn signals MailDeck tracks alongside spam complaints above 0.3% and a "Bad" reputation in Google Postmaster Tools.

Gmail and Outlook score every sending domain on its own history. When bounces pile up on one domain, both providers treat it as a sender with poor list hygiene and start filtering its mail, and the damage persists after the bad list is gone. MailDeck reads 7% as a domain diagnostic for that reason, separate from the campaign scale.

The burn signals, read per domain:

- Bounce rate above 7% on that domain's sends.

- Spam complaint rate above 0.3%, the same ceiling Google sets in its [bulk sender guidelines](https://support.google.com/a/answer/81126).

- Domain reputation shown as "Bad" in [Google Postmaster Tools](https://postmaster.google.com/).

Microsoft's [SNDS](https://sendersupport.olc.protection.outlook.com/snds/) adds IP-level data on Outlook-bound mail from dedicated Private SMTP IPs, which helps confirm whether a bounce spike on one SMTP domain is reaching Microsoft recipients as a reputation problem.

### How many bounces cross 7% on one domain

How many bounces push a domain over 7% depends on how much mail that domain sends at safe per-inbox limits.

| Inbox type | Inboxes per domain | Sends per day per domain | Bounces/day to reach 5% | Bounces/day to cross 7% | Warm-up before cold sends |
|---|---|---|---|---|---|
| Google Workspace | 5 | ~100 | 5 | 8 | 2-3 weeks |
| Outlook Premium | 100 | ~900 | 45 | 64 | 3-5 days |
| Outlook Normal | 100 | ~400 | 20 | 29 | 5-7 days |
| Private SMTP | 5 | ~65 | 4 | 5 | 3-4 weeks |

Per-domain volumes and warm-up times: Q4 2026 MailDeck platform data. Bounce counts are calculated from those volumes and rounded up to whole bounces.

A Google Workspace or SMTP domain crosses the burn line on a handful of bad addresses, so a small unverified segment routed to one domain can burn it in a day. An Outlook domain needs dozens of bounces a day to cross 7%, and when it burns, 100 inboxes go quiet together. The warm-up column is the price of losing a domain without a reserve. For how domain reputation is scored and what lifts it back, see the [cold email domain reputation guide](https://maildeck.co/blog/cold-email-domain-reputation).

### Case: a 3.8% campaign hiding six burning domains

A B2B SaaS lead-generation agency ran 300 Google Workspace inboxes across 60 domains, sending about 6,000 emails a day for four clients. In August 2026 its sequencer showed a blended campaign bounce rate of 3.8%, inside the healthy band.

When the agency grouped its bounce export by sending domain, six domains had sat above the 7% burn line for eight straight days. The cause was one client's 5,400-contact list, pulled from an older CRM export and routed to those six domains by the rotation settings.

The agency paused the six domains the same afternoon and rotated in replacements from a reserve of 14 warmed domains, and all six were sending within two days. The client's list went back through verification and lost 1,150 of its 5,400 addresses. In the following 90 days the agency replaced 8 domains, down from 19 in the 90 days before, and every campaign stayed in the under-5% healthy band.

## What drives cold email bounce rate up

> In MailDeck's Q4 2026 platform data, inbox placement holds at 98% across 833.9K+ managed inboxes, so a cold email bounce rate above 5% points to the list or to DNS configuration far more often than to the inbox provider.

| Cause | Bounce type | Code family | Typical campaign impact | Fix |
|---|---|---|---|---|
| Stale list (job changes, company renames) | Hard | 5.1.x | Rises month by month as data ages | Re-verify any list before a 90-day re-hit |
| Pattern-guessed addresses | Hard | 5.1.x | Spikes on companies using a non-standard format | Verify guessed addresses before import |
| Catch-all domains accepting then rejecting | Hard, delayed | 5.1.x or 5.7.x | Hidden at verification, shows up after send | Send catch-all segments from a test layer first |
| Role addresses (info@, sales@) | Hard or policy | 5.1.x, 5.7.x | Higher complaint and block rate | Remove from cold lists |
| Broken SPF, DKIM or DMARC | Policy | 5.7.26, 5.7.1 | Sudden spike across one receiving provider | Fix records, verify propagation |
| Volume above safe per-inbox limits | Soft, then policy | 4.7.x, then 5.7.x | Deferrals that turn into blocks | Drop to safe sends per inbox |

List decay is the slow driver. A verified list starts clean and loses accuracy every month as people leave roles, which is why MailDeck's TAM guidance has teams re-hit lists every 90 days with fresh angles and a fresh verification pass.

Authentication failures are the fast driver. A campaign that sits in the healthy band for weeks and jumps into the 5-9% band in one morning, with the new bounces all carrying 5.7.x codes from one provider, almost always means a DNS record changed. A MailDeck audit of 1,000+ domains (Q4 2026 platform data) found 67% had at least one critical authentication error, which is why MailDeck automates SPF, DKIM and DMARC on every client domain and verifies propagation before the first cold send.

Volume pressure sits between the two. Sending above safe limits (18-22 cold emails per Google Workspace inbox per day, 8-10 per Outlook Premium inbox, 3-5 per Outlook Normal inbox, 10-15 per Private SMTP inbox) produces 4.7.x deferrals first. Ignored deferrals become hard policy blocks, and those count against both scales.

## How to reduce cold email bounce rate before it touches a domain

> MailDeck's Q4 2026 platform data shows domain replacement takes 1-3 days with warmed reserves ready and 7-10 days without, so the cheapest bounce fix is the one applied before a list reaches a primary sending domain.

A list travels from the data source, through a test layer, onto primary inboxes and into daily monitoring, and each stage gets its own step.

- Verify the list before import. Drop invalid and unknown results, and hold risky catch-all addresses for the test layer.

- Send the first day of each new list from Private SMTP inboxes: 100 inboxes at 10 cold emails each covers about 1,000 contacts. Promote the list to Outlook or Google Workspace only if that slice stays in the under-5% band.

- Keep per-inbox volume at the safe limits listed in the previous section, and spread each campaign across enough domains that no single domain carries a whole segment.

- Export bounces grouped by sending domain every day and compare each domain against 7%, alongside its spam complaint rate.

- Apply the stop rules on the campaign scale (fix errors at 5-9%, stop at 10%+) and on the domain scale (pause any domain above 7%), and log the cause of each pause against the list that produced it.

- Hold warmed reserve domains equal to 20-25% of active domains so a paused domain is back in service in 1-3 days.

Step 2 uses a part of the stack most senders skip. Private SMTP inboxes cost $0.50 each on MailDeck with a 100-inbox minimum, and their job in the recommended 50/30/20 split is to absorb volume and test lists and copy before anything reaches the premium layers. A burned SMTP domain is a replaceable operating cost; a burned Google Workspace domain costs 2-3 weeks of warm-up. For how to schedule reserves and rotate domains around a pause, see the [domain rotation playbook for cold email](https://maildeck.co/blog/cold-email-domain-rotation).

### Case: a staffing firm that stopped losing Outlook domains to bad lists

A recruiting and staffing firm sending candidate and client outreach ran 400 Outlook Premium inboxes across four domains, about 3,500 sends a day. Between March and June 2026 it lost three of those four domains to bounce-driven burns, each time after loading a client-supplied list straight into the primary inboxes.

From July the firm added 100 Private SMTP inboxes across 20 domains at $50 a month, about 1,200 sends a day, and routed every new list through a 1,000-contact SMTP slice first. In September one list, an export from a 2022 CRM, bounced on 152 of its first 400 sample sends; the firm stopped it there and sent it back for verification.

Across July to October 2026 the firm lost zero Outlook domains and replaced two SMTP domains. Outlook campaign bounce stayed inside the under-5% healthy band in every one of those four months.

### Case: a solo founder who hit 11.7% on day one

A bootstrapped founder selling a scheduling tool to dental practices ran a Google Workspace Starter plan: 10 mailboxes across two domains at $39 a month, warmed for 21 days. The founder loaded a purchased list of 2,400 contacts and sent 180 emails on the first morning. By noon the campaign showed 21 bounces on those 180 sends, an 11.7% campaign bounce rate.

The founder stopped the campaign the same day under the 10% rule. Verification removed 504 of the 2,400 addresses as invalid or risky catch-all. The remaining 1,896 contacts ran over the next three weeks with 36 bounces, a 1.9% bounce rate.

Those same 1,896 contacts produced 64 replies, a 3.4% reply rate inside the 2-5% good band. Both domains were still sending ten weeks later.

## Bounce rate and the inbox type you send from

> On identical lists in Q4 2026 MailDeck tests, Outlook Premium placed 15-20% below Google Workspace, Outlook Normal 20-25% below, and Private SMTP 35-50% below.

A hard bounce on an invalid address happens on every inbox type. What changes by inbox type is how much a bounce costs: how many inboxes share the domain it lands on, and how long a replacement takes to warm. Matching inbox type to the list's risk keeps the expensive layers away from untested data.

| Layer in a 50/30/20 stack | Share of volume | Bounce exposure | Role for bounce control |
|---|---|---|---|
| Outlook (Premium or Normal) | 50% | Moderate per bounce, 100 inboxes share a domain | Primary bulk sending on verified lists |
| Private SMTP | 30% | Low cost per burned domain | List and copy testing, overflow volume |
| Google Workspace | 20% | High cost per burned domain (2-3 week warm-up) | Top segments and C-suite lists that passed testing |

ESP matching helps here as well. Sending Outlook-to-Outlook and Google-to-Google routes delivery inside the same provider and tends to place better, so segmenting a verified list by recipient provider before assigning inboxes lowers policy blocks on the receiving side.

## Which setup fits your bounce numbers

Best for: a bootstrapped founder sending under 10,000 emails a month who needs a Google Workspace Starter setup at $39 a month with two domains to protect.

Best for: an outbound agency running several client lists that needs per-domain bounce readings and a warm reserve of 20-25% of active domains so one client's bad list never burns another client's domains.

Best for: a recruiting or staffing firm loading client-supplied lists that needs a Private SMTP test layer at $0.50 per inbox before lists reach primary Outlook inboxes.

Best for: a team outside the US sending into US buyers on a tight budget that wants Outlook Normal at $0.30 per inbox and more domains instead of more inboxes per domain.

Best for: a high-volume sender above 100K emails a month, where MailDeck measured 10-20% monthly domain burn in Q4 2026, that needs replacement in 1-3 days from warmed reserves.

Best for: a team selling into Gmail-heavy markets that wants Google-to-Google ESP matching on its top segments after lists clear the under-5% campaign band.

## Where MailDeck Fits

Any provider carrying cold email should be held to one standard on bounce rate: warmed inboxes that place well enough that a bounce spike points at the list, plus warm reserves that replace a paused domain within days. Without both, a single bad list costs weeks.

MailDeck clears that bar with a published record: 98% inbox placement across 833.9K+ managed inboxes sending 7.5M+ emails a day in Q4 2026, with replacement in 1-3 days when warmed reserves are ready. All three inbox types sit under one provider, so the SMTP test layer and the premium layers share one setup.

The outcome is campaigns that stay in the under-5% bounce band and domains that last their full active lifespan instead of burning in the first week of a bad list. If you want your current per-domain bounce readings mapped onto that kind of stack, the MailDeck team will walk through them with you.

## FAQ

### Is a 7% bounce rate good?

For a cold email campaign, 7% sits in the 5-9% band, so monitor closely and fix list errors before the next step goes out. For a single sending domain, 7% is the burn line, and a domain above it is burning and should be paused. On MailDeck infrastructure, which placed 98% of mail in the inbox across 833.9K+ managed inboxes in Q4 2026, a 7% reading usually traces back to the list in the accounts we run, so cleaning the bounced segment brings the number down without touching the inboxes.

### Is a 42% bounce rate good?

No, on a cold email campaign 42% means the list is dead, so stop at once, because the stop line is 10%. In Google Analytics 4 the same figure describes website sessions that were not engaged, a separate metric with no link to email delivery. A campaign at 42% on a Google Workspace domain sending about 100 emails a day returns roughly 42 bounces daily, far past the 7% burn line, and MailDeck's Q4 2026 data puts replacement at 7-10 days for a domain with no warm reserve.

### Is a 50% bounce rate high?

Yes, on a cold email campaign 50% is five times the 10% stop line, and the list should go back for full verification before another send. A 50% reading in Google Analytics 4 counts website sessions that were not engaged and says nothing about email. At enterprise scale (100K+ emails a month), MailDeck sees 10-20% of domains burn monthly in Q4 2026 under normal sending, so a 50% list can take a domain out within days.

### Can cold emailing get you blacklisted

Yes, a sending domain that keeps mailing invalid addresses or draws spam complaints above 0.3% gets filtered by Gmail and Outlook and can land on blocklists. In Q4 2026 MailDeck platform data, 10-20% of domains burn monthly at enterprise scale (100K+ emails a month), and a bounce rate above 7% on one domain is one of the burn signals we track. Holding campaigns under 5% bounce and replacing burned domains from a warm reserve in 1-3 days keeps a blocklisting from stopping outreach.

### What is the success rate of cold emails?

Reply rate is the usual success measure: 0.8-2% is average, 2-5% is good, 5-10% is strong and above 10% is elite. In MailDeck's booking math from 270M+ cold emails sent lifetime through Q4 2026, a 4% reply rate with 20% positive and 20% booked needs about 190,000 emails a month for 300 calls. A high bounce rate drags every one of those numbers down, because bounced sends count against the domain and never reach a buyer.

### Is cold email still effective in 2026?

Yes, for senders who keep bounce rate and domain health under control. MailDeck infrastructure carried 7.5M+ cold emails a day in Q4 2026 at 98% inbox placement across 833.9K+ managed inboxes. Domains last 45 days to 2 months under active load in that data, and holding campaigns under 5% bounce is how senders reach the end of that window.

### Should I delete hard bounce emails?

Yes, suppress every hard bounce, such as a 5.1.1 user-unknown response, in your sequencer and CRM so the address is never mailed again from any domain. Resending to a hard-bounced address adds bounces to the next domain in the rotation, and on a Private SMTP domain sending about 65 emails a day, 5 bounces put it over the 7% burn line. MailDeck keeps a warm reserve sized at 20-25% of active domains so a domain lost that way is replaced in 1-3 days.

## Methodology

MailDeck figures in this article are first-party production measurements from the MailDeck platform as of Q4 2026: 833.9K+ managed inboxes across Microsoft 365 Outlook, Google Workspace and Private SMTP, 7.5M+ cold emails sent per day and 270M+ cold emails sent lifetime. Inbox placement of 98% is measured on warmed infrastructure across that inbox base.

The domain burn rate of 10-20% a month applies to senders at enterprise scale (100K+ emails a month) in Q4 2026. Domain lifespan under active load (45 days to 2 months) and reserve sizing (20-25% of active domains) come from the same data.

Replacement times (1-3 days with warmed reserves, 7-10 days without) are Q4 2026 platform figures. The DNS audit covered 1,000+ domains, of which 67% had at least one critical authentication error.

The campaign bounce scale (under 5% healthy, 5-9% monitor and fix errors, 10%+ stop) and the domain burn signals (bounce above 7%, spam complaints above 0.3%, Postmaster reputation "Bad") are the thresholds MailDeck applies in production monitoring in Q4 2026. The per-domain bounce counts in the 7% table are our arithmetic from MailDeck's per-domain sending volumes at safe limits, rounded up to whole bounces. Relative placement figures come from identical-list tests in Q4 2026.

Competitor data: no competitor vendor is named on this page, so no competitor pages were fetched for it. Website bounce rate follows the [Google Analytics 4 definition](https://support.google.com/analytics/answer/12195621) of sessions that were not engaged.

Billing basis: all MailDeck prices are monthly list prices. Google Workspace Starter is $39 a month for 10 mailboxes, and Outlook tenants of 100 inboxes are $30 (Normal) or $40 (Premium).

Private SMTP is $0.50 per inbox with a 100-inbox minimum, and the Diversified Stack starts at $99 a month.

External references: [RFC 3463](https://datatracker.ietf.org/doc/html/rfc3463) for enhanced SMTP status codes, [Google's email sender guidelines](https://support.google.com/a/answer/81126) for the 0.3% spam rate ceiling, [Google Postmaster Tools](https://postmaster.google.com/) for domain reputation, and [Microsoft SNDS](https://sendersupport.olc.protection.outlook.com/snds/) for IP-level data on Outlook-bound mail.

Client cases are anonymized composites from 2026; inbox counts, domain counts, sending volumes, warm-up periods and pricing stay within the ranges published above. Limitations: per-domain bounce readings in the cases come from sequencer exports grouped by sending domain.

Platform statistics used on this page: 98% inbox placement across 833.9K+ managed inboxes sending 7.5M+ emails per day (Q4 2026); 10-20% of domains burned monthly at 100K+ emails a month (Q4 2026); domain replacement in 1-3 days with warmed reserves versus 7-10 days without (Q4 2026).

Last updated: November 2026.

Written by Pavel Stoletov, CTO at MailDeck, leading outbound infrastructure and deliverability engineering. Pavel built the infrastructure delivering 50M+ emails monthly across 1,200+ domains at 98% inbox placement, and sets the bounce and domain-burn thresholds MailDeck monitors in production. Read more at maildeck.co/authors/pavel-stoletov or connect on [LinkedIn](https://www.linkedin.com/in/pavel-stoletov-30b817292/).

Written by [Pavel Stoletov](https://maildeck.co/authors/pavel-stoletov)

CTO | Outbound Infrastructure & Deliverability Engineering

[LinkedIn](https://www.linkedin.com/in/pavel-stoletov-30b817292/)

[View Profile](https://maildeck.co/authors/pavel-stoletov)

## Ready to Scale Your Email Infrastructure?

Join top outbound teams using MailDeck for enterprise-grade deliverability.

[Get Started](https://app.maildeck.co)

## Continue Reading

[Guide](https://maildeck.co/blog/smtp-error-codes-cold-email)

### [SMTP Error Codes in Cold Email: What Each Code Means for Your Deliverability](https://maildeck.co/blog/smtp-error-codes-cold-email)

[We process 65M+ emails daily. Here's every SMTP error code you'll encounter in cold email, what each one means, and the ...](https://maildeck.co/blog/smtp-error-codes-cold-email)

[Guide](https://maildeck.co/blog/cold-email-domain-reputation)

### [Cold Email Domain Reputation: How to Build and Protect It](https://maildeck.co/blog/cold-email-domain-reputation)

[Domain reputation is the underlying asset that decides whether cold email reaches the inbox. From a DNS audit of 1,000+ ...](https://maildeck.co/blog/cold-email-domain-reputation)

[Guide](https://maildeck.co/blog/cold-email-domain-rotation)

### [Cold Email Domain Rotation: When and How to Rotate Sending Domains [2026]](https://maildeck.co/blog/cold-email-domain-rotation)

[10-20% of cold email domains burn monthly at scale. Complete domain rotation strategy with specific thresholds, timeline...](https://maildeck.co/blog/cold-email-domain-rotation)
