[ 01 ]
Reputation damage compounds fast
Once a domain starts landing in spam, continuing to send from it makes the problem worse, faster than a human is likely to notice and react.
CogniLead
ProductWarmed sender poolReputation circuit-breakerJurisdiction routingREST APIMCP serverDNS automationCompliance & suppression
SolutionsDevelopersAgenciesB2B SaaSRecruitersSales teamsSolo foundersSaaSRecruiting & staffingReal estateAgencies & consultingEcommerce & DTCB2B services
CompareAll 12 alternatives →vs. Instantly.aivs. Smartleadvs. Lemlistvs. Apollo.iovs. Woodpecker.coInstantly vs. SmartleadSmartlead vs. LemlistApollo vs. LemlistSee all 8 →
ResourcesBlogDocsMCP serverAPI referenceSPF checkerDMARC checkerBlacklist checkerSpam-word checkerStatus
PricingLog inReputation circuit-breaker
Your domains, watched continuously — paused before they burn.
Most cold-email tools tell you about a reputation problem after a batch has already gone out. CogniLead reads Google Postmaster Tools continuously and automatically pauses the specific sending domain the moment its spam rate or reputation drifts — before one bad send drags the rest of your sending down with it.
The problem
A drifting domain does not announce itself.
[ 02 ]
Manual monitoring means checking after the fact
Watching Postmaster Tools by hand means you find out about a problem after a batch has already gone out, not before.
[ 03 ]
One bad domain can put the whole operation in doubt
Without a safeguard scoped to the specific domain, a single reputation problem is hard to isolate — teams often respond by second-guessing every domain, not just the one that drifted.
[ 04 ]
No visibility into why a domain went quiet
A domain that stopped sending because it was throttled looks the same as one that is simply idle — without a recorded reason attached, you are left guessing which one you are looking at.
How it works
Watched, paused, and resumed — automatically.
A Postmaster-based monitor that auto-pauses a sending domain the moment its spam rate or reputation drifts — before one bad batch damages the rest of your sending.
Continuous, automatic Postmaster monitoring
Spam-rate and reputation signals are checked on an ongoing basis, not on a manual schedule someone has to remember to run.
Two real signals, either one can trip it
A domain reputation reading of LOW or BAD from Google Postmaster Tools, or a user-reported spam ratio above 0.3% — crossing either threshold is what the breaker is watching for.
Auto-pause on drift, not after damage
The moment a domain’s signals cross a safe threshold, sending from that specific domain pauses automatically — the goal is to catch it before it fully burns.
Resume only on a genuinely clean reading
A paused domain resumes once reputation reads HIGH or MEDIUM again with spam rate back under threshold — an unclear (UNKNOWN) reading is deliberately not enough to resume on.
The mechanism, live
One threshold breach, one domain paused.
An illustrative example: a single domain’s reported spam rate climbs toward the pause threshold, crosses it, and the domain is paused on its own — resuming only once a clean reading comes back.
cedarline.warmpool.example — spam rateIllustrative
Spam ratePaused0.3% threshold
[ 01 ]
Every 6 hours
Default poll cadence
[ 02 ]
Spam rate > 0.3%
Pause threshold
[ 03 ]
Reputation HIGH or MEDIUM
Resume requires
Always watching
A domain that drifts pauses itself.
Every sending domain is read against Google Postmaster Tools on a recurring cadence, not a schedule someone has to remember to run. The moment one domain’s signals cross a safe threshold, it pauses on its own — and resumes only once a genuinely clean reading comes back.
- Checked
- Every 6 hours
- Pauses on
- LOW/BAD reputation, or spam > 0.3%
- Resumes on
- A clean HIGH/MEDIUM reading
FAQ
Questions about the circuit-breaker.
Spam-rate and reputation signals from Google Postmaster Tools drifting past a safe threshold for that domain.
No — the circuit-breaker acts on the specific degrading domain. Other domains in the pool keep sending normally.
Yes — paused state is visible on the dashboard, along with the reason, so you know why a domain stopped sending.
No — bounce and complaint handling (suppression) is a separate mechanism; see /features/compliance-suppression. The circuit-breaker acts on aggregate reputation signals, not individual bounces.
The circuit-breaker works alongside the pool it protects: the warmed sender pool.
Your leads deserve to reach an inbox.
Every email you send without protection is a gamble on whether it reaches the inbox at all. Bring your leads — CogniLead handles the warmup, the safety checks, and the cleanup, so you don't have to think about deliverability again.
100 sends a month, free forever · no credit card · cancel any time