/ Glossary — Reputation & Bounces
What is a spam trap?
An email address used to catch senders with poor list hygiene. Here's how pristine, recycled, and typo traps work, why hitting one is so damaging, and how clean sending avoids them entirely.
/ Definition
A spam trap is an email address that exists specifically to catch senders with poor list hygiene or non-consensual list-building. Run by mailbox providers and blocklist operators, a spam trap never belongs to a real person actively signing up for mail — so any message it receives is evidence that the sender acquired the address improperly, whether by scraping, buying a list, or failing to remove dead addresses. Hitting one damages your reputation directly, because the organizations that run traps are the same ones that decide whether your mail reaches the inbox.
Spam traps are deliberately invisible. You can't detect them by looking at your list, because a trap address looks like any other — which is the entire point. The only reliable defence is the practice of clean, consent-based sending that keeps traps out of your list in the first place, since by the time a trap reveals itself through a blocklist listing, the damage is already done.
/ The three types
Pristine, recycled, and typo traps
A pristine trap is an address created only to catch spam — never used, never subscribed to anything. Because there's no legitimate way for it to be on your list, a pristine-trap hit is the most damaging kind: it proves non-consensual acquisition, and a single one can trigger a blocklist listing. A recycled trap was once a real person's address, then abandoned and left to hard bounce for months before the provider reactivated it as a trap — it catches senders who don't remove long-inactive addresses. A typo trap is a misspelling of a popular domain, like "gmial.com," that catches senders who don't validate addresses at the point of signup.
How do you avoid them?
You can't remove traps you can't see, so the answer is prevention through hygiene. Use double opt-in so every address proves it's a consenting human; validate addresses at signup to catch typos before they enter your list; never buy or scrape lists, which is how pristine traps get in; and apply a sunset policy that retires long-inactive addresses before they can become recycled traps. These practices are exactly what separates a sender who rarely hits a trap from one whose reputation is quietly eroded by them, and they're a core part of the list management that modern bulk sender rules effectively require.
/ Related terms
You can't see a trap. You can build sending that avoids them.
Consent-based list-building, validation, and sunset policies keep traps out before they cost you — the hygiene discipline we operate as standard. Bring us your list practices and we'll close the gaps.
Book infrastructure reviewRelated capabilities