Blocklist operators publish addresses in places only a scraper would find them, then wait. Anyone who mails that address demonstrably built their list by harvesting rather than by consent. That is the whole mechanism, and it works because the address is otherwise unremarkable.
Probe one and the server accepts it, because it is a real mailbox on a real domain that is genuinely monitored. There is no field in the SMTP response that says trap. There cannot be, because the operator's entire purpose is to remain undetectable.
Recycled traps are a different animal. Those are addresses that belonged to a person, were abandoned, hard bounced for a period, and were then reactivated as traps. That history sometimes leaves a signal, and a verifier can flag an address that looks like it followed that path.
That is a heuristic. We call it one. Some vendors describe the same capability as spam trap removal, which converts a probability into a promise.
What actually protects you
Consent, documented. A list where every address opted in cannot contain a pristine trap, because nobody published one to a form and confirmed it.
Never buying lists. Purchased data is the main delivery vehicle for traps, and a clean verification result on purchased data tells you the addresses exist rather than that they are safe.
Removing hard bounces immediately. An address that bounces repeatedly and then starts accepting mail is the recycled trap pattern, and suppressing on first failure means you were never there to see it reactivate.
Sunsetting unengaged addresses. An address that has not opened anything in a year is the profile a recycled trap fits, whether or not it is one.
Where this argument costs us something
The short version
- Treat any spam trap removal claim as a sales line rather than a capability.
- Protect yourself through consent and sunsetting, which are the only defences that work.
- Understand that a clean verification result on a purchased list is not a safety certificate.
Questions people ask
Can any verifier detect a pristine spam trap?
No. It is an ordinary mailbox at the protocol level, and there is no signal to read. Products claiming to remove them are describing a recycled-trap heuristic in stronger language.
What is a recycled spam trap?
An abandoned address that hard bounced for a period and was then reactivated by a blocklist operator. The bounce history sometimes leaves a detectable pattern, which makes a heuristic flag possible.