What are spam traps
A spam trap is an email address that belongs to no one. It exists for one reason: to catch senders who mail to lists they did not build carefully.
Providers like Spamhaus and SpamCop seed them across the web. Hit even one and your domain reputation drops, pushing mail into spam folders for every recipient, not just that address.
Three types of traps
Pristine traps were created for detection from day one. No real person ever used them or opted in to anything. Sending to one means you scraped it or bought a list. Providers treat this as the clearest possible signal of poor list hygiene.
Recycled traps start as real mailboxes. An employee leaves, the inbox goes dark, the server kicks back bounces for months. Then, quietly, the address becomes a trap. If you are still mailing it, you have not cleaned your list.
Typo traps catch what you did not validate: gmial.com, yaho.com, hotmial.com. The user mistyped on your signup form, you did not catch it, and now you hit a trap on every send.
How they reach your list
Buying lists is the fastest route. Scraping sites is the second. The third is subtler: a legitimate list left unvalidated for two or three years. Addresses you gathered properly may have become traps since, and you would never know without revalidation.
How to protect yourself
Double opt-in at signup stops typos and fake addresses before they enter your system. Removing subscribers with no opens in six months eliminates recycled trap risk before it compounds. Run a validation pass before any large send to catch what slipped through in between.
uChecker strips dead addresses and domains on public blocklists out of your list. Recycled traps are built on abandoned mailboxes, so cleaning the list removes most of the exposure before you ever hit send.
Two kinds of trap
Pristine traps are created by a provider from scratch and never given to anyone. There is exactly one way to acquire one: scraping it off a page where it was placed as bait. A pristine trap in your list is direct evidence the list was not built from opt-ins.
Recycled traps are former real mailboxes that their owner abandoned. The provider bounces mail to them for a year or so, then repurposes the address as a trap. One of these lands in an honestly built list simply because a subscriber stopped using that mailbox.
Why validation cannot find them
A trap is technically healthy: the MX is in place, SMTP answers 250, the syntax is correct. Any validator calls it deliverable, because it is deliverable. The only difference is that nobody is behind it.
The only defence is preventing accumulation: double opt-in at signup, regular pruning by engagement, removing addresses with no opens in a year. Validation removes dead addresses and slows the future supply of recycled traps, but will not spot a trap that already exists.