Cold emails going to spam
Replies thin out while every dashboard says fine. Spam placement rarely has one cause, so start with what is configured and where your mail actually lands.
- 213K mailboxes under management
| 9/28 | 9/29 | 9/30 | 10/1 | 10/2 | 10/3 | 10/4 | 10/5 | 10/6 | 10/7 | |
|---|---|---|---|---|---|---|---|---|---|---|
| Authentication | ||||||||||
| DKIM | ||||||||||
| DMARC | ||||||||||
| SPF | ||||||||||
| Infrastructure | ||||||||||
| Outbound IP | ||||||||||
| Placement | ||||||||||
| Microsoft placement | ||||||||||
| Blacklists | ||||||||||
| Spamhaus DBL | ||||||||||
| SURBL | ||||||||||
What broke: Placement at Microsoft is falling on try-outreach.co. Authentication and blocklists are clear.
Do: Slow sends to Microsoft recipients and move volume to a warmed domain.
Spam placement has several contributing factors
Spam, while every dashboard says fine
The campaign is running, bounces are low, nothing is red. The replies are what tell you something is off, and they tell you late.
Configuration and reputation both count
A missing DMARC policy, a blocklist listing, a redirect that ties the domain to another, a warm-up pool that sends where your leads are not. Each can contribute, and several often overlap.
Each guess costs a send cycle
Rewrite the copy, rotate domains, change the warm-up. Without placement per provider, each change takes a full sequence to judge, and the leads it reaches are spent.
One missing record, two different weeks
An example weekFixing by guesswork
try-outreach.co has no DKIM record and its mail starts landing in spam.
You rewrite the copy. Replies stay flat.
You rotate domains. Still flat, and a send cycle is spent.
The missing record is still missing.
The DNS check shows no DKIM record for try-outreach.co.
You publish the record from your admin panel and rerun the check.
Placement per provider shows where the mail lands now.
Copy, list and domains never had to change.
Check the setup, then measure where mail lands
Start with the records
SPF, DKIM, DMARC and MX decide whether a provider trusts the domain at all. On sending.ac, these records are written per domain and verified before the first send.
- Written per domain
- Verified before the first send
- Checked again in the audit
| Domain | SPF | DKIM | DMARC | MX |
|---|---|---|---|---|
| get-outreach.co | ||||
| outreach-hq.co | ||||
| try-outreach.co | Missing |
What broke: No DKIM record found for the selector try-outreach.co signs with.
Do: Publish the DKIM record from your admin panel, then rerun the check.
Then audit placement and blocklists
The deliverability audit looks at authentication, blocklists and placement, then recommends what to change. On sending.ac, placement is measured hourly from inside real inboxes across every major provider, with Microsoft spam score checked daily.
- Recommends the fix, you decide
- Hourly placement from real inboxes
- Microsoft spam score, daily
- Your sending domainsThe ones where placement slipped
- Checks and placementAuthentication, blocklists, inbox placement per provider
- RecommendationsWhat broke, why it can matter, what to do next
Teams running outbound on sending.ac
Can confirm. We actually tested them, and performed next to Winnr the best. Good on Yannic Schwock
Setup was fast, DNS and DKIM handled automatically, and each domain runs on its own isolated tenant so a burned domain stays contained.
Btw, you guys have the smoothest UX/UI of all the inbox resellers I’ve purchased from. And I’ve worked with ALL of them.
Find the cause in three steps
Check the records
The audit starts with SPF, DKIM, DMARC and MX on each sending domain.
Audit placement and blocklists
The deliverability audit looks at authentication, blocklists and inbox placement per provider.
Fix what it found
Each finding comes with what broke, why it can matter and what to do next. You decide what to change.
Questions about spam placement
Most of these are faster on a 15-minute call with someone who already knows the answer.
Talk to an advisorIs the deliverability audit free?
Yes. It is a 15-minute call where we look at your actual sending data.
What does the deliverability audit look at?
Authentication, blocklists and inbox placement per provider. It recommends what to change, and you decide.
Why does only one provider put me in spam?
Placement can fall at one provider while the others hold, which is why it helps to see placement per provider instead of one number.
Can a redirect hurt placement?
A redirect that ties a sending domain to another domain can contribute. On sending.ac, every outreach domain can serve its own site instead.
Does warm-up affect where I land?
It can. A warm-up pool that sends mostly where your leads are not builds reputation in the wrong place. sending.ac compares the pool’s provider mix to where your campaign sends, measured from outside the pool.
How does sending.ac keep this from happening?
Records are written per domain and verified before the first send. Placement is measured hourly from inside real inboxes, and Microsoft spam score is checked daily.
Start with the records
Book the audit for the domain that worries you, and we look at the rest of the fleet on the same call.
- SPF, DKIM, DMARC and MX on each domain
- 15 minutes, on your sending data
- Audit of authentication, blocklists and placement
- Recommends the fix, you decide
- Hourly placement from real inboxes on sending.ac
- Microsoft spam score, checked daily