Most deliverability troubleshooting starts in the wrong place.
A campaign slows down, replies drop, and the team rewrites the subject line. Or they switch sequencers. Or they buy more domains. Or they assume Gmail changed something.
Sometimes copy is the issue. Often, it is not the first place to look.
Cold email deliverability is a system problem. The sending path, domains, authentication, volume, list quality, recipient feedback, placement, bounces, and reply operations all interact.
The fastest way to diagnose the problem is to move through the system in order.
Step 1: Define The Symptom
Start with the exact failure.
"Deliverability is bad" is not a diagnosis.
Useful symptoms are specific:
- Gmail placement dropped.
- Microsoft is deferring messages.
- One domain has high hard bounces.
- Replies dropped after a volume increase.
- One sender is landing in spam.
- A new campaign is blocked while older campaigns are stable.
- Opens changed but replies did not.
The narrower the symptom, the easier it is to investigate.
Step 2: Separate Provider Problems
Deliverability is provider-specific.
Gmail, Microsoft, Yahoo, and private business domains do not behave identically. A campaign can look healthy overall while one provider family is degrading.
Break the problem down by provider:
- Gmail or Google Workspace
- Microsoft 365 or Outlook
- Yahoo and AOL
- Private domains
- Regional or industry-specific domains
If only one provider is weak, the issue may be provider-specific reputation, throttling, authentication interpretation, content filtering, or recipient behavior. If every provider is weak, the problem may be broader: infrastructure, DNS, list quality, volume, or campaign fit.
Inbox placement testing is useful here. For the basics, read What Is Inbox Placement Testing for Cold Email?.
Step 3: Check DNS And Authentication
Before analyzing copy, check identity.
Cold email infrastructure depends on DNS and authentication. At minimum, inspect:
- SPF
- DKIM
- DMARC
- MX records for receiving domains
- A or AAAA records for hostnames
- PTR records for reverse DNS on sending IPs
- Tracking and redirect domains
Google's sender guidelines require SPF or DKIM for all senders to Gmail accounts and require SPF, DKIM, and DMARC for bulk senders above 5,000 messages per day to Gmail accounts. Google also calls out valid forward and reverse DNS records for sending domains or IPs.
If the technical identity is broken, downstream analysis is noise.
Step 4: Check What Changed
Deliverability problems often follow a change.
Look for:
- New domains
- New senders
- New dedicated IPs
- New SMTP or relay paths
- New tracking domains
- DNS changes
- Volume increases
- List source changes
- Template changes
- Different recipient segment
- New links or attachments
The change may not be obvious to the person looking at campaign performance. It may live in infrastructure, data, or operations.
Build a change log for outbound. It saves time when performance moves.
Step 5: Inspect Volume And Pacing
Sending volume is a reputation signal.
Sudden jumps can create throttling, deferrals, spam placement, or reputation drops. This is especially true for new domains, new IPs, and new sender identities.
Google advises senders to start with low sending volume, increase slowly, avoid bursts, and monitor server responses when increasing volume. That guidance applies directly to cold outbound.
Check:
- Daily sends per sender
- Daily sends per domain
- Daily sends per IP or server
- Provider-specific volume
- Time-of-day bursts
- New sender ramp schedules
- Campaign overlap across senders
If volume changed before performance dropped, diagnose pacing before copy.
Step 6: Read Bounce And Deferral Patterns
Bounces are not all the same.
Separate:
- Hard bounces
- Soft bounces
- Blocks
- Deferrals
- Mailbox full
- Invalid domain
- Policy rejection
- Authentication failure
- Rate limiting
A high hard-bounce rate points toward list quality. Provider deferrals can point toward throttling or reputation. Authentication failures point toward DNS or setup. Blocks may point toward policy, complaints, reputation, or content.
For a deeper operator view, see Bounce Rate Benchmarks for Cold Email.
Step 7: Compare Placement And Bounce Data
Placement testing and bounce data answer different questions.
Placement tests show where controlled messages land. Bounces show whether real recipient servers accepted, delayed, or rejected campaign mail.
Use them together:
- Poor placement plus provider deferrals suggests path or reputation risk.
- Good placement plus high hard bounces suggests list quality.
- Poor placement on one provider suggests provider-level diagnosis.
- Good placement plus weak replies may point toward offer, targeting, or copy.
This prevents the team from treating one metric as the entire truth.
Step 8: Decide Whether To Pause, Reduce, Or Continue
Diagnosis should change behavior.
If a provider is deferring mail, a sender is bouncing heavily, or placement has dropped across a domain, the team should not keep sending at the same pace while "monitoring." That turns diagnosis into observation.
Use a simple decision model:
- Continue when signals are stable and the issue is isolated to a low-risk campaign variable.
- Reduce when volume appears to be part of the problem but infrastructure is not failing outright.
- Pause when a sender, domain, IP, or provider path shows clear degradation.
- Isolate when one list source, sender, provider, or domain is materially worse than the rest.
The goal is to protect the rest of the sending system while the weak point is fixed.
This is where dedicated infrastructure and clean campaign routing help. If every path is mixed together, pausing the right thing is harder. If the team knows which domains, senders, IPs, and campaigns are involved, the response can be surgical.
Step 9: Inspect List Quality
Infrastructure cannot save bad inputs.
If a new list source creates more invalid addresses, low-fit recipients, role accounts, stale contacts, or poor targeting, deliverability and revenue both suffer.
Check:
- Validation status
- Data age
- Source quality
- Persona fit
- Company fit
- Role addresses
- Duplicate contacts
- Prior negative engagement
Validation helps, but it does not prove fit. A valid address can still be a bad prospect.
Step 10: Check Domain And Sender Health Together
A domain can look acceptable while one sender is failing. A sender can look acceptable while the domain is carrying too much total volume.
Diagnose both levels:
- Is one sender driving the issue?
- Is one domain weaker than the others?
- Did the domain recently add senders?
- Did the sender recently change lists or campaigns?
- Is the domain sharing volume across too many motions?
- Are tracking or redirect domains aligned with the sending domain?
This is why a single account-level deliverability number is not enough. The operating unit is often a combination of sender, domain, provider, IP, and campaign.
For the domain-level view, read Domain Health for Cold Email.
Step 11: Review Copy After The System Checks
Copy still matters.
But it should be reviewed after the technical and operational checks above.
Look for:
- Misleading subject lines
- Heavy image or link use
- Unclear sender identity
- Spammy claims
- Repetitive templates across high volume
- Bad personalization tokens
- Poor offer fit
- Missing unsubscribe or opt-out handling where required
If infrastructure is healthy and list quality is reasonable, copy and offer become more likely suspects.
Step 12: Check Reply Operations
Reply handling affects deliverability too.
If unsubscribes, negative replies, and interested replies are scattered across many inboxes, the team can keep sending to people who should be suppressed or prioritized differently.
At scale, reply operations become part of deliverability operations.
Super Inbox-style centralization matters because interested replies, out-of-office messages, negative replies, and unsubscribe signals need to be processed quickly.
Where SuperSend Fits
SuperSend helps teams diagnose cold email deliverability problems across the operating system, not just the campaign calendar.
Dedicated infrastructure gives cleaner boundaries. Placement testing shows provider-level risk. Bounce intelligence helps separate rejection types. Domain and sender health make weak points visible. Super Inbox keeps reply signals from scattering. REST API and webhooks let technical teams connect these signals into their own workflows.
Deliverability diagnosis is not one button. It is a sequence of questions. The faster you ask them in the right order, the less volume you waste.
Further reading
Free playbook · 11 pages
Want the full cold email infrastructure playbook?
Get the founder breakdown on why rented mailbox stacks are breaking and what dedicated cold email infrastructure looks like now.
