Deliverability

Spam Traps: Pristine, Recycled, Typo. How Dormant Lists Grow Them and What a Scan Can Actually Catch

By Artem KukharenkoPublished Updated 8 min read

Updated 1 November 2026.

three envelopes, one pristine white, one weathered, one with a misspelled address label
Original editorial diagram of the article’s subject; illustrations are conceptual rather than measured results.

Definitions (per Spamhaus)

Spam trap. An email address that has never opted into anything and is never revealed by its owner, used by blocklist operators, mailbox providers and researchers to detect senders who mail addresses they did not legitimately collect. Spamhaus's glossary says such addresses are never disclosed, and that it is a "questionable claim" when a company says it can find and remove them.

Pristine trap. An address created for the purpose, never used by a person, never published. Spamhaus notes these are typically used by researchers investigating specific abuse. The only way one enters your list is through scraping, purchasing or a compromised signup path; a legitimate signup form does not produce them.

Recycled trap. A once-valid address that went dormant. Spamhaus: ISPs turn off once-valid addresses, "and mail to them is rejected with a hard bounce for a period of time, often 12 months or more"; after that the addresses are "silently turned back on as spamtraps." Spamhaus calls these "an effective way for providers to judge list hygiene." Any sender who kept mailing through the bounce period and ignored the hard bounces, or who stopped mailing before the bounces and resumed after the reactivation, hits them.

Typo trap. Addresses on domains a few characters away from popular ones (Spamhaus's examples: yaaho.com, homail.com). They collect mistyped signups. Spamhaus notes these "are not 'pure' spam traps, can contain a lot of real mail, and are generally weighted accordingly," and that Spamhaus itself has not used typo domains as a data source.

Definitions (per Spamhaus)Spam trapPristine trapRecycled trapTypo trap
Definitions (per Spamhaus). Read the full qualifications and dated sources in the accompanying table.

How a dormant list grows recycled traps

The sequence is mechanical:

  1. A subscriber abandons a mailbox (changes jobs, changes providers, stops using an old account).
  2. The provider eventually disables it. Mail now hard-bounces.
  3. If you are sending regularly, your ESP sees the hard bounce and suppresses the address (Klaviyo on the first hard bounce; Mailchimp "cleans" it). The address leaves your active list before it can become a trap.
  4. If you are not sending (a dormant list), nobody sees the bounce. The address sits in your file through the bounce period.
  5. After "12 months or more," the provider silently reactivates it as a trap. It now accepts mail and reports the sender.
  6. You "revive" the list with one big send. The trap accepts the message. Your domain or IP shows up in a blocklist feed as a sender mailing addresses no person has used in over a year.

This is why the age of a list matters more than its size, and why the first send to a dormant segment is the dangerous one. Vendor scans of dormant files report 15–30% invalid or risky addresses (EmailListValidation, vendor figure); a share of the "risky" portion is this process in progress.

What a trap hit does

  • Blocklists. A pristine-trap hit can trigger a listing on its own; recycled-trap hits accumulate as evidence of poor hygiene. Spamhaus's guidance ties "lack of sunset policy combined with poor bounce management" to inclusion on its blocklist (SBL).
  • Provider rejections. Yahoo's permanent rejections (553/554) explicitly include "an IP listed by Spamhaus" among the causes. Gmail does not publish its use of trap data; the effect shows up as spam placement and, for authenticated senders, as a complaint-rate and engagement problem rather than a named reason.
  • Reputation. Trap data feeds mailbox providers' and filtering vendors' reputation systems. The consequence is the same as a complaint spike: placement falls for engaged recipients too.

What a scan can and cannot catch

Scroll for more → On small screens, choose cards for wide tables.

Address type Detectable by a verification scan? How
Invalid syntax, nonexistent domain, no MX record Yes DNS and syntax checks
Mailbox does not exist (on providers that answer) Usually SMTP probe; catch-all domains return "unknown"
Disposable and temporary-mail domains Yes Known-domain lists
Role accounts (info@, admin@, sales@) Yes Pattern match
Typo domains (gmial.com, homail.com) Mostly Known typo-domain lists; new ones appear
Recycled traps Not reliably They accept mail and look valid; some vendors flag "trap-like" patterns by domain history, which is inference, not detection
Pristine traps No Never disclosed; by definition indistinguishable from a valid, silent mailbox

So a scan removes the addresses that would bounce or that signal scraping, which is a large share of the risk. It cannot certify a list trap-free, and anyone who says their scan does is making the claim Spamhaus calls questionable. The remaining risk is handled by how you send, not by what you remove.

Get the scan, and the dormancy map that goes with it. The free List Health Audit returns the bounce, trap-pattern and dead-domain scan, a dormancy map by tier and a domain risk score within 72 hours, so the first send to a dormant segment is small and informed. Get the free audit →

How to mail a dormant list without feeding traps

  1. Eligibility first. Addresses with no documented consent source, or consent older than 24 months with no relationship evidence, are held. Pristine traps come from bad acquisition; this is where you stop them.
  2. Scan. Suppress everything undeliverable, dead-domain, disposable, role-based and typo-domain. Hold catch-all addresses for the last cohorts.
  3. Order by evidence. Send first to addresses with a purchase or click in the last 18 months. The older the last engagement, the later the cohort and the smaller the exposure.
  4. Stream, don't blast. One-thirtieth of the sendable segment per day. If cohort 12 contains a trap, you have exposed 3% of the list, not 100%.
  5. Stop conditions. Hard bounces above 2% of a cohort: stop and re-scan. Any provider rejection citing a blocklist: stop. Complaints at 0.1%: pause; 0.3%: stop.
  6. Sunset forever after. The reason recycled traps exist is addresses kept past their life. A sunset policy with suppression (not deletion) prevents the next accumulation.

The full procedure, with the tier table and the daily schedule, is in the reactivation playbook.

If you have already been hit

  • Find the send. Blocklist notices and provider rejections carry dates; match them to the campaign and the segment.
  • Suppress the segment, not just the one address. Spamhaus's point is that the address is a symptom; the segment is the cause.
  • Request delisting only after the cause is fixed. Blocklist operators publish removal procedures; a listing that recurs is treated more severely than a first one.
  • Expect provider effects to lag. Yahoo rejections stop when the listing clears; Gmail placement recovers on the timeline in the domain-reputation guide.
  • Audit acquisition. If the hit was pristine, a signup form, an integration or a purchased file is feeding you addresses that were never real. Confirmed opt-in on the suspect path is the usual fix.

FAQ

What is a spam trap? An email address never used by a real person, or abandoned and later reactivated, that is monitored to catch senders mailing addresses they did not legitimately collect. Operators never disclose them.

What are the three types of spam traps? Pristine (created for the purpose, never a user), recycled (a real address abandoned, bounced for 12+ months, then reactivated as a trap), and typo (addresses on domains a few characters off a popular one). Definitions follow Spamhaus.

Can email verification tools remove spam traps? They remove invalid, dead-domain, disposable, role and typo-domain addresses, which cuts most of the risk. They cannot identify pristine traps and cannot reliably identify recycled ones. Spamhaus calls "find and remove spam traps" a questionable claim.

Why do old email lists hit spam traps? Because abandoned addresses bounce for a year or more before being turned into traps, and a list nobody mails during that year never sees the bounces. The first send after a long gap reaches the reactivated traps.

What happens if I hit a spam trap? Blocklist listings (Spamhaus and others), provider rejections (Yahoo cites Spamhaus listings in its 553/554 errors) and reputation loss that lowers placement for your engaged recipients too. Severity depends on trap type and how many you hit.

How do I avoid spam traps? Confirmed opt-in on acquisition, a sunset policy with suppression, bounce handling on every send, a scan before any dormant send, and daily micro-cohorts with stop conditions instead of a single send.

Already seeing blocklist notices or Yahoo 554s? The Data & Deliverability Audit finds the segment and the acquisition path behind them and gives you the suppression and delisting order. Request the audit →

Sources

Cite this page

Spam Traps: Pristine, Recycled, Typo. How Dormant Lists Grow Them and What a Scan Can Actually Catch. Artem Kukharenko. EngageMKTG. 2026-11-02. https://engagemktg.com/knowledge/spam-traps-dormant-lists

Related articles