Spam traps are the usual reason one campaign takes a domain down. Below: the trap types that blocklist operators describe, how a cold-email list ends up containing them, why a sender cannot spot them in advance, and how isolating domains limits the damage when one is hit.
What is a spam trap?
A spam trap is an address run by a blocklist operator, a mailbox provider or an anti-abuse organisation to measure who sends unwanted mail. It belongs to no person and never asks for mail. When a message arrives, the operator learns that the sender's list includes addresses nobody gave with consent.
The consequence depends on who runs the trap. A hit can lower the sender's reputation at one provider, or put the domain on a shared blocklist that gateways and mail servers query everywhere. Either way the cost lands on the sending domain, not on the one message.
Which types of spam traps exist?
Spamhaus groups traps by how the address became a trap. M3AAWG adds the timing rule that matters most for old lists.
| Type | How it comes about | What a hit signals | How to avoid it |
|---|---|---|---|
| Pristine | Created as a trap and never used by a person | The list was bought or harvested | No bought or scraped lists |
| Seeded | Planted where harvesters collect addresses | Addresses were scraped | Source contacts you can trace |
| Dead address (recycled) | A real mailbox, abandoned and turned into a trap after at least 12 months of rejecting mail | The list is old and not cleaned | Drop hard bounces; verify before each campaign |
| Dead domain | An expired domain taken over to collect mail | Old data | Verify domains, not only addresses |
| Typo | A misspelled domain, such as g-mail.com | Addresses were not checked at entry | Verify syntax and domain |
| Role | A generic role address that the operator monitors | Addresses were guessed or scraped | Write to named people, not role inboxes |
Types as described by Spamhaus; the 12-month rule is from M3AAWG.
How does a cold-email list hit a trap?
Through its source and its age. Pristine and seeded traps enter a list when contacts are bought in bulk or scraped from the web, because that is where trap operators place them. M3AAWG treats a pristine hit as a sign of a purchased list. Dead-address and dead-domain traps enter when a list sits for a year or more: people leave companies, mailboxes close, and some closed addresses later become traps.
Cold outreach meets both risks. It writes to people who did not opt in, and B2B contact data ages as people change jobs. Spamhaus is explicit on a point cold senders often miss: verification lowers bounces, but it does not turn a list into a consented one. A pristine trap accepts mail like any working mailbox, so verification cannot flag it.
Spamhaus describes the trap types (pristine, seeded, typo, dead address, dead domain and role) and advises fixing the list source rather than the symptom. M3AAWG's Help! I Hit a Spam Trap sets the recycled-trap rule at a minimum of 12 months of inactivity and treats pristine hits as a sign of purchased lists. M3AAWG's spamtrap operations best practices ask operators to reject mail to a repurposed address with a 5xx error for at least 12 months before it becomes a trap, so a sender who removes hard bounces never reaches it. Microsoft's email policies state that spam traps cannot be identified by the sender.
Can you detect a trap before sending?
No. Microsoft states plainly that spam traps cannot be identified by the sender. Operators keep their addresses secret, because a known trap stops measuring anything. What you can do is lower the odds.
- Source: use contacts you can trace to a data source, not bulk lists of unknown origin.
- Recency: enrich and verify close to the send date, not months earlier.
- Verification: drop invalid and risky results. It removes typos and dead domains; it does not find pristine traps.
- Bounces: never write again to an address that hard-bounced. Recycled traps start as addresses that rejected mail for a year.
- Exclusions: keep a blacklist of bounced and opted-out contacts that applies across every campaign.
What limits the damage when a domain is caught?
Isolation. If all outreach runs from one domain, a trap hit there takes the whole programme down. If it runs across several separate domains, the hit damages one, and you take that domain out of the rotation while the others keep sending. Reputation lives at the domain level, so mailboxes on the same domain share its fate.
Leadspicker's guidance is to rotate more domains rather than more mailboxes on one domain, with 2 to 3 mailboxes per domain. Each domain bought through Custom Domains runs in its own isolated workspace, so a spam trap on one domain affects nothing else.
This is also where cold practice and standards part. M3AAWG advises against lookalike domains, and separate outreach domains are often exactly that. Isolation limits the cost of a trap. It does not answer the consent question the trap was set to ask; only a better list source does.
Each domain bought through Custom Domains in Leadspicker runs in its own isolated workspace. When one domain hits a spam trap, it is dropped from the rotation and the other domains keep sending.
Frequently asked questions
What happens if I hit a spam trap?
The sending domain's reputation drops, and it can be listed on a blocklist that receivers check. Stop sending from that domain, take it out of the rotation and find the list source that carried the trap.
Can email verification remove spam traps?
Partly. It removes typo addresses and dead domains, but a pristine trap accepts mail like a working mailbox, and Microsoft states that traps cannot be identified by the sender.
How long before an abandoned address becomes a trap?
M3AAWG sets a minimum of 12 months, during which the address rejects mail with an error. A sender who removes hard bounces stops writing to it long before that.
- Spamhaus, Spamtraps: fix the problem, not the symptom (2022)
- M3AAWG, Help! I hit a spam trap
- M3AAWG, Best Common Practices for Building and Operating a Spamtrap (2016)
- Microsoft Learn, Email policies and suspension standards
- GTM playbook for 2026 by Leadspicker, chapters: Buying domains and mailboxes; Sending volume and domain rotation
