What is a spam trap?

The three kinds, and what each one proves

Pristine traps are addresses created purely as bait - published quietly where only automated harvesting will find them, never used by a human, never subscribed to anything. Mail arriving at one proves the sender scraped or bought data. This is the most damaging kind to hit, because there is no innocent explanation.

Recycled traps are real addresses that died - an employee left, a domain lapsed - and were reactivated as traps after a long period of returning hard bounces. Mail arriving at one proves the sender ignored bounces or is using data old enough to predate the address's death. It convicts your hygiene rather than your sourcing.

Typo traps are registrations of common misspellings - the gmial.com family - that catch mail whose addresses were never checked. In B2B cold email they mostly indicate pattern-guessed addresses built without verification.

How traps get into a cold email list

Nobody adds a trap deliberately; they arrive with the sourcing shortcuts. Purchased bulk lists are the classic carrier, because the sellers harvested at scale years ago and resell the same decaying file. Scraped lists inherit whatever bait was planted where the scraper looked. Old exports recycled from a previous company or campaign carry addresses that have since died and been reborn as traps. And pattern-guessing addresses from names, without live verification, manufactures typo-class risk directly. This is one reason list building is a process question rather than a shopping question.

What hitting one costs

A single trap hit is not a death sentence, but it is never free. Trap operators feed blocklists and provider reputation systems; enough hits, or hits on high-value pristine traps, and your sending domain or IP range appears on lists that receiving servers consult before accepting mail. The visible symptoms are the generic ones - placement quietly degrading, more mail landing in spam, gateway rejections rising - which is exactly why traps are hard to diagnose from the outside: they look like every other reputation problem. What makes them distinctive is the cause of death recorded on the receiving side, which you never get to read.

Why you cannot reliably clean traps out

The uncomfortable fact: a pristine trap verifies as deliverable. It is a real, working mailbox that accepts mail - that is its job. Verification removes dead addresses, which protects you from recycled traps' precursor state, but it cannot flag a live mailbox as bait. Vendors selling trap-removal are selling confidence, not certainty. The honest defences are structural:

• Never send to purchased bulk lists. This single rule removes the majority of trap exposure, and it is a rule we treat as absolute.
• Build lists from primary evidence - people demonstrably in the role at the company today - rather than from aged aggregate files.
• Verify live, immediately before sending, so recycled-trap precursors (dead addresses) are caught while they are still catchable.
• Honour every bounce. Recycled traps punish senders who keep mailing addresses that hard-bounced. Suppression discipline is trap defence.
• Watch recency. Data about who works where decays continuously; the older the row, the higher the odds its address has died since. Fresh evidence beats big archives.

Traps, complaints and the reputation ledger

Traps sit alongside spam complaints and bounces in the ledger receiving providers keep on every sender. Google's published expectation for bulk senders is a complaint rate below 0.3%, with 0.10% as the recommended operating level - and trap hits are weighted more heavily than either, because they cannot be explained by an annoyed but real recipient. A programme that keeps per-mailbox volume conservative, verifies live and builds from primary evidence rarely meets a trap at all; a programme built on bought data meets them guaranteed, and usually learns it from a blocklist notice.

Common questions

How do you know if you hit a spam trap?

Directly, you usually do not - trap operators do not notify senders. The indirect evidence is a reputation decline you cannot explain with bounces or complaints, or a blocklist entry naming your domain or IP. By the time either is visible, the fix is list-source surgery, not address removal.

Can email verification detect spam traps?

It reliably catches the dead addresses that become recycled traps, which is valuable. It cannot flag pristine traps, because they are live mailboxes that accept mail. Verification is necessary and insufficient; sourcing discipline does the rest.

Do spam traps ever reply?

No. A trap only receives. Any address that replies to you is by definition not a trap - which is one more reason reply-focused, low-volume, verified outbound is structurally safer than volume spraying.

Are spam traps a problem for legitimate B2B cold email?

Only through bad sourcing. Traps punish scraped, purchased and stale data. A list built from primary evidence and verified live has very little surface area for them - which is the design, not an accident.