The Email Deliverability and Verification Glossary: 50+ Terms That Actually Matter

Email infrastructure has a vocabulary problem: the same handful of terms get used loosely and interchangeably, and the confusion causes real mistakes, like deleting catch-all contacts because someone read unknown as bad, or retrying hard bounces because an ESP relabeled them as blocks. This is the reference page: 50+ terms defined precisely, grouped the way practitioners actually use them, with the most-confused pairs flagged.

Verification Statuses and Signals

Email verification. Confirming whether an address can receive mail, without sending a message, via syntax checks, DNS and MX lookups, and a live SMTP mailbox probe. Syntax validation. Checking only that an address is well-formed per the RFC grammar; a syntactically perfect address can still be dead. Mailbox probe. The SMTP conversation (connect, HELO, MAIL FROM, RCPT TO) that asks the receiving server whether a specific mailbox exists, disconnecting before any message is sent.

Passed. The server confirmed the mailbox accepts mail. Failed. The server confirmed it does not (user unknown, dead domain, malformed address). Unknown. The mailbox could not be confirmed either way, almost always because of catch-all acceptance or persistent greylisting; unknown is unconfirmable, not invalid, and treating it as failed deletes real contacts. Catch-all (accept-all). A domain configured to accept mail for every address at that domain, common at 20-30 percent of business domains, which makes mailbox-level confirmation impossible from the outside.

Greylisting. An anti-spam tactic where a server temporarily rejects first contact from an unfamiliar sender and accepts the retry; verification engines wait out the window and retry, which is why some results take minutes. Disposable address. A throwaway mailbox from a temporary-email service, deliverable today and worthless tomorrow. Role account. A function-owned address (info@, sales@, support@) read by teams rather than one person. Gibberish detection. Pattern scoring that flags local parts shaped like keyboard mashes rather than human identities. Typo suggestion (did-you-mean). A model-proposed correction for a likely misspelling, such as gmial.com to gmail.com, surfaced for user confirmation rather than silent rewriting. Free-service flag. Marks addresses at legitimate free providers like Gmail; distinct from disposable, and never a reason to block. Each of these arrives as a field or event in a verification response; the complete schema lives in the email verification API documentation, and any single address can be inspected against it with the instant email checker.

Bounce and SMTP Mechanics

Bounce. A delivery failure reported back to the sender. Hard bounce. A permanent failure (mailbox or domain does not exist, permanent block), signaled by 5xx SMTP codes; remove on first occurrence and never retry. Soft bounce. A temporary failure (mailbox full, server busy, message too large), signaled by 4xx codes; retry within limits, and treat an address soft-bouncing across 3+ campaigns as hard. Deferral. A polite temporary rejection asking the sender to retry later, greylisting being the most common cause.

SMTP reply code. The three-digit response a receiving server returns for each command, where the first digit carries the verdict: 2xx success, 4xx temporary failure, 5xx permanent failure. Enhanced status code. The dotted X.X.X code accompanying modern replies (5.1.1 user unknown, 5.2.2 mailbox full) that pins down the specific reason. Silent discard. The failure that never reports itself: a server accepts the message and drops it without delivery or bounce, common at some catch-all and heavily filtered domains, and the reason accepted does not mean delivered. Bounce rate. Bounced messages as a share of sent, with sustained rates above roughly 2 percent triggering provider scrutiny.

List Hygiene and Acquisition

List decay. The natural death of addresses over time (job changes, abandonment, domain expiry) at roughly 22-30 percent per year, which is why verification is a cadence rather than an event. List hygiene. The ongoing practice of removing invalid, risky, and unengaged addresses, anchored by periodic passes through a bulk email verifier. Sunset policy. The systematic retirement of long-unengaged subscribers: verify the segment, win back the live ones, suppress the silent. Suppression list. The do-not-send record of unsubscribes, complaints, hard bounces, and sunset non-responders, kept permanently so re-imports cannot resurrect them.

Re-engagement (win-back) campaign. A short sequence attempting to reactivate dormant subscribers before suppression. Single opt-in. Subscribing an address the moment it is submitted. Double opt-in. Requiring a click on a confirmation email before the address is subscribed, proving both deliverability and intent at the cost of some conversion. Spam trap. An address maintained by providers or anti-spam organizations to identify senders with poor hygiene. Pristine trap. A trap address that never belonged to a real person, reachable only by scraping or purchased data. Recycled trap. An abandoned real mailbox converted into a trap after a dormancy period, which is what makes mailing old unengaged segments dangerous. Purchased list. Acquired contact data with no consent relationship; dense with traps and dead addresses, and no verification pass fixes the missing consent.

Authentication and Identity

SPF (Sender Policy Framework). A DNS record listing the servers authorized to send mail for a domain. DKIM (DomainKeys Identified Mail). A cryptographic signature on each message proving it was authorized by the signing domain and unaltered in transit. DMARC. The policy layer telling receivers what to do when SPF and DKIM checks fail (none, quarantine, reject) and where to send reports. Alignment. The DMARC requirement that the domain a recipient sees matches the domain that passed SPF or DKIM, closing the gap spoofers exploit. BIMI. The standard that displays a sender's verified logo in supporting inboxes, available only to domains with enforcing DMARC. Spoofing. Forging a sender identity, which the authentication stack exists to defeat.

Reputation and Filtering

Sender reputation. The trust grade mailbox providers maintain on your sending identity, built from bounces, complaints, engagement, and trap hits; it decides placement more than content does. Domain reputation. The portion attached to your domain, which follows you across infrastructure changes. IP reputation. The portion attached to sending IP addresses, shared with neighbors on shared IPs. Engagement signals. The recipient behaviors (opens, clicks, replies, deletes without reading, spam reports) providers weigh when grading senders.

Complaint (spam) rate. The share of delivered mail recipients mark as spam, with modern provider thresholds sitting near 0.3 percent and safe operation well under 0.1. Feedback loop (FBL). A provider mechanism reporting complaints back to senders so the complainer can be suppressed. Blocklist (blacklist). A published list of IPs or domains associated with spam, consulted by receivers during filtering. Inbox placement. Where accepted mail actually lands (inbox, spam, promotions), the thing deliverability names. Deliverability. The practice and measure of reaching the inbox, as distinct from delivery, which only means the receiving server accepted the message.

Sending Infrastructure

MX record. The DNS entry naming the servers that receive mail for a domain; no resolvable MX (or fallback A record) means no delivery, which is why domain verification is the first semantic check in any pipeline. ESP. Email service provider, the platform that sends on your behalf. Dedicated IP. A sending address used only by you, whose reputation is entirely your own doing. Shared IP. A sending address pooled across many senders, where reputation is communal. IP warming. Gradually ramping volume on new sending infrastructure so providers can build a reputation history before full load.

Subdomain separation. Sending different mail streams (marketing vs transactional) from different subdomains so one stream's problems cannot contaminate the other's reputation. Seed testing. Sending to a panel of monitored addresses across providers to measure actual placement. Postmaster tools. Provider-operated dashboards (Google Postmaster Tools, Microsoft SNDS) exposing how that provider grades your sending. Real-time verification. Checking an address at the moment of capture through a real-time email verification API, so bad data never enters the system, as opposed to batch verification, which cleans data already collected.

The Five Confusions That Cost Money

Most deliverability arguments are vocabulary arguments in disguise. Agree on what unknown, bounce, and reputation actually mean, and the strategy debate usually settles itself.

Frequently Asked Questions

The Bottom Line

Precision in this vocabulary is not pedantry; every term above attaches to a decision, and the confusions attach to expensive ones. Unknown decides whether contacts live or die, deferral decides what gets retried, reputation decides where everything lands, and the difference between validation and verification decides whether your pipeline catches problems before or after they bounce.

Keep the page handy, settle arguments with definitions, and spend the recovered energy on the two numbers that summarize the whole field: bounces under 2, complaints under 0.3.