---
title: "What is a spam trap? Types and verification limits - Emvero"
description: "Learn what pristine and recycled spam traps are, why a working address can be a trap, and what email verification can and cannot establish."
url: https://emvero.io/glossary/spam-trap/
language: en
updated: 2026-10-07
---

All terms

Glossary

# Spam trap

A spam trap is an address used to observe unwanted mail and assess sending practices. It may accept mail normally, so technical verification cannot identify it reliably.

## What incoming mail reveals

Mail providers and anti-abuse operators use spam traps to assess sending practices and inform reputation systems. Mail arriving at a trap can reveal a problem with address collection or list maintenance. The [Spamhaus definition of a spamtrap](https://www.spamhaus.org/glossary/) explains this purpose. A trap can have ordinary address syntax, so its spelling offers no reliable way to identify it.

## Pristine and recycled addresses

A pristine trap was never assigned to an ordinary user. A recycled trap uses an address that previously belonged to one. These are common forms; [Spamhaus describes several trap designs](https://www.spamhaus.com/resource-center/spamtraps-fix-the-problem-not-the-symptom/). A recycled address may have rejected mail for a period before becoming a trap.

This history does not reveal which addresses are traps now. A trap may accept mail as an ordinary mailbox would. A refusal may have an unrelated cause. Emvero cannot predict whether sending to an address will lead to a blocklist entry.

## What verification can establish

Emvero checks syntax, domain information and, when available, the receiving server’s SMTP response. It does not identify spam traps, and its probe sends no email. A `deliverable` result supports technical acceptance. It cannot establish permission to send, the presence of a human reader or the absence of a trap.

You can use a supported technical failure in your sending rules, but that finding is not evidence of a spam trap. Routine verification cannot remove every address that is, or may later become, a trap.

## Review the address’s collection history

Keep the collection source, subscription request and any exclusions alongside the verification result. Resolve unclear collection history or intended use before adding the address to a campaign. The [list-cleaning guide](https://emvero.io/guides/cleaning-an-email-list/) explains this review, and [verification versus list hygiene](https://emvero.io/compare/verification-vs-list-hygiene/) shows which decisions require your sending history.

## Related reason codes

Emvero does not identify spam traps, so there is no reason code for this finding.

## Related terms

### Hard bounce and soft bounce

Permanent and temporary delivery failures describe a sending attempt. Learn how they differ from verification evidence.

### Role account

An address for a team or function, such as support@. It can receive mail; its suitability depends on the purpose.

### Disposable email address

An address at a temporary-mail provider. The domain signal concerns durability and policy, rather than proving delivery failure.

## Compared side by side

### Email verification vs list hygiene

Technical address evidence and ongoing subscription, suppression and engagement records answer different sending questions.

[All terms](https://emvero.io/glossary/)

## Try a check in your account.

Choose the check that fits your question and inspect the result.

Start for free