Compared
Verification vs. list hygiene
Verification is a fact about an address at a moment. List hygiene is a practice about engagement over time. Neither substitutes for the other.
| What you want to know | Verification | List hygiene |
|---|---|---|
| The question being answered | Can mail be delivered here? | Is this mail wanted here? |
| Where the evidence comes from | DNS and the receiving mail server | Opens, clicks, complaints, age, source |
| A mailbox that stopped working | Caught before the send | Caught after it, by the bounce |
| A subscriber who stopped caring | Invisible. The address works perfectly | This is exactly what it is for |
| A recycled spam trap | Caught only while it is still bouncing | Caught by removing the long-disengaged |
| How often to do it | At collection, and again before a send | Continuously — it is a practice, not a job |
These get treated as the same job and they are not, which is how a list with a 99% deliverable rate still lands in the promotions tab — or worse.
Verification answers a mechanical question: can mail be delivered to this address right now? It is checkable from outside, it produces evidence, and it is true or false at the moment you ask. That is the whole of what this service does, and it is deliberately the whole of it.
List hygiene answers a question about people: does this person want the mail? Nothing in DNS or SMTP knows that. It shows up in opens, clicks, complaints, how the address was collected and how long ago somebody last did anything — signals that live in your sending platform, not in a verification result.
The two fail in opposite directions, which is why running one is not covering for the other. A perfectly verified list of people who never asked to hear from you will generate complaints, and complaints are weighted more heavily by mailbox providers than bounces are. A well-engaged list that has not been verified in a year will accumulate addresses that quietly stopped working, and hard bounces are the clearest negative signal there is.
They do overlap in one place worth knowing: a recycled spam trap is an address that hard-bounced for a while before it was reactivated. Verification catches it during that window and never again — which makes regular verification part of hygiene, rather than a replacement for it.
Related terms
Spam trap
An address that exists only to catch senders who mail people who never asked to hear from them.
Hard bounce and soft bounce
The difference between mail that will never be delivered and mail that failed this time.
Role account
An address that reaches a function rather than a person — info@, support@, sales@.
Run one and see the difference.
The free checker returns the whole result — every stage, every reason code, nothing held back.