If you send cold email, the worst thing hiding in your list is not a typo. It is not a role inbox. It is not even a dead mailbox. It is a spam trap, and you cannot see it coming from the address alone.
A spam trap is an email address that no real person uses, planted by a deliverability watchdog or anti-abuse network specifically to catch senders with poor list hygiene. Hit a few and your sending domain lands on a blocklist that Gmail, Outlook, and Yahoo all consult. The fall from that ladder is fast. The climb back is slow.
Why traps are so hard to detect
Most traps look like ordinary, well-formed addresses on real-looking domains. They pass syntax. They pass MX. They often pass SMTP because the trap operator actually accepts the mail. The only way to know an address is a trap is to know which addresses are traps — and that means access to a maintained list.
That list does not exist publicly. The big anti-abuse networks keep their trap inventories private on purpose, because if spammers knew exactly which addresses to avoid, the traps would be useless. So the practical question is: how do we lean on that intelligence without buying our way into a multi-year enterprise contract?
The ninth check
We have added a ninth check to every verification, powered by Abusix Mail Intelligence. Abusix runs one of the largest abuse-intelligence networks in the world, and they expose their live blocklists through a fast DNS interface. For every address you send through us, we now ask Abusix four questions about the recipient's domain: is it on a known abuse blocklist, is it freshly registered with no reputation history, is it on a vetted whitelist, and is it tied to any known exploit campaigns?
The check sits between our MX lookup and our SMTP probe. If the domain is listed, we mark the verdict risky even if everything else checks out, and we name the signal in plain English on your results — 'Recipient domain listed as an abuse source' — so you can choose to skip it. If the domain is freshly registered (a common pattern for disposable services that pop up faster than we can list them), we flag it as newly observed.
What changes in your dashboard
Open any list and you will see a new Signals column on the results table. Trap and abuse-source hits appear as small purple badges next to the verdict. A new filter chip lets you isolate just the flagged rows so you can review them or suppress them in bulk. The Console (our single-email instant verify) returns the full Abusix detail in its JSON response, including which zones flagged the domain.
Nothing changes about your credits. The check is included in the per-address price you already pay, on every workspace, on every tier.
Where it goes from here
Trap detection is a moving target. Abusix is one feed; over the next quarter we are wiring up our own bounce-feedback loop so customers can post back actual ESP bounces and we can grow our own trap corpus on top of theirs. The combination — third-party live intelligence plus first-party customer signal — is how the best deliverability vendors quietly stay ahead. We will share results as the data builds.