List hygiene is the ongoing practice of keeping a contact list free of invalid, decayed, or complaint-prone addresses through verification and removal, since even one repeated pattern of hard bounces reads as poor hygiene and drags down sender reputation.
List hygiene covers everything that keeps a contact list from quietly degrading a domain's sending reputation: verifying addresses before they get sent to, removing hard bounces immediately instead of retrying them, and pulling out anyone who's complained or unsubscribed so they never get mailed again. Every hard bounce tells the receiving server the sender tried an address that doesn't exist, and a repeated pattern of that reads as poor list hygiene, which factors directly into how sending reputation gets scored.
Contact lists decay on their own timeline, not on a schedule a team controls. People change jobs, mailboxes get shut down, role accounts get retired, and an address that verified cleanly two months ago can bounce today. Pre-send verification catches that drift before it shows up as a bounce instead of after, which matters more the more sources feed a list. Pulling contacts through a waterfall across several enrichment providers means each source's own staleness needs catching before any of it touches the sending domain's reputation.
Unverified data from three sources is worse than verified data from one. That reads backward until you factor in what a bounce actually costs: not just a wasted send, but a signal to the receiving server that the sending domain doesn't check its list, and that signal follows the domain into every inbox after it.
Treat list hygiene as a recurring pass, not a step that happens once when a list gets built. Re-verify before every real send, not just at import, and route bounces, complaints, and unsubscribes into a suppression list immediately so the same address doesn't get retried on the next campaign by accident.
Teams verify a list once, at the point they bought or scraped it, then treat it as clean indefinitely. A list is only as clean as its last verification pass, and one that was fine two months ago can already be stale by the time it's actually used, especially one assembled from multiple enrichment sources with different refresh schedules.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us