Email Verification Terms, Explained in Plain English
Fifteen definitions covering the vocabulary behind every email validation result, from SMTP response codes to authentication records. The terms are grouped by how they relate to each other rather than alphabetically, so you can read them in an order that builds.
Almost every term on this page traces back to a single short conversation between two mail servers. A sender's server looks up where to deliver mail for a domain, opens a connection, names the recipient, and waits for a numeric reply. A 250 means the server accepts that address, a 550 means no such mailbox, and a 4xx means try again later. Email validation is the practice of having that conversation deliberately and stopping before a message is actually sent, SMTP verification is the name for the protocol-level exchange itself, and MX records are the DNS entries that tell you which server to talk to in the first place.
Those reply codes explain the two words you will meet most often in campaign reporting. A 550 is what produces a hard bounce, a permanent failure you should never retry and should remove from your list straight away. A 4xx produces a soft bounce, which usually means a full mailbox, a server under load, or greylisting, and which only becomes a real signal when the same address keeps failing across several separate sends. Neither code tells you whether your message reached the inbox or the spam folder, because that is deliverability — a separate measurement that only begins after the receiving server has agreed to accept the mail.
That distinction matters because verification and authentication answer different questions and cannot stand in for one another. Verification asks whether an address exists; authentication asks whether the receiving server should believe a message really came from you. SPF publishes which servers are allowed to send for your domain, DKIM adds a cryptographic signature proving the message was not altered in transit, and DMARC tells receivers what to do when those checks disagree with the visible From address. A perfectly clean list still lands in spam when these records are missing, and flawless authentication still bounces when the mailbox was deleted a year ago.
The hardest terms are the ones in between, where an address technically exists but sending to it is still a mistake. A catch-all domain answers 250 to every address you ask about, so verification cannot prove any individual mailbox is real; a disposable address is genuine today and abandoned next week; a role-based address such as info@ reaches several people who never individually agreed to hear from you; and a spam trap accepts your mail for the specific purpose of reporting you. Dealing with those categories consistently over time is what email hygiene describes, and the running score receivers keep on your sending behaviour is your sender reputation. If the subject is new to you, read in that sequence — the process, then the outcomes, then the awkward middle — rather than working down the list alphabetically.
How verification actually works
The mechanics of checking an address: the overall process, the SMTP exchange that does the real work, and the DNS lookup that has to succeed before any of it can start. Begin here if you want to understand what a verification tool is doing on your behalf when you paste in an address.
- What is Email Validation? Email validation process definition.
- What is SMTP Verification? SMTP-level email address verification definition.
- What is an MX Record? Mail Exchange DNS record definition.
Delivery outcomes and failure codes
What the receiving server tells you after you send, and how to interpret it. These three pages separate permanent failures from temporary ones and explain why an accepted message is still not the same thing as an inbox placement.
- What is a Hard Bounce? Permanent email delivery failure definition.
- What is a Soft Bounce? Temporary email delivery failure definition.
- What is Email Deliverability? Inbox placement rate definition.
Addresses that exist but carry risk
Each of these will usually sail through a basic syntax and domain check, which is precisely what makes them dangerous. Read them before you decide how your workflow should treat results flagged as accept-all, disposable, role-based or high-risk, and use the disposable email checker to test a single suspicious domain.
- What is a Catch-All Domain? Accept-all email server definition.
- What is a Disposable Email? Temporary email address definition.
- What is a Role-Based Email? Generic department email address definition.
- What is a Spam Trap? Honeypot email address definition.
Authentication records for your own domain
The three DNS records receiving servers consult to decide whether a message genuinely came from you. They live on the sending side rather than the list side, but a missing or misconfigured record quietly undermines whatever list cleaning you have done. You can test all three at once with the SPF, DKIM and DMARC checker.
- What is an SPF Record? Sender Policy Framework DNS record definition.
- What is DKIM? DomainKeys Identified Mail definition.
- What is DMARC? Domain-based Message Authentication definition.
List quality over the long run
Contact lists decay whether or not you send to them, and receiving servers keep score of how you handle that decay. These two pages cover the ongoing discipline and the reputation it protects, and the bulk email verifier is the practical tool for putting the first one into practice.
- What is Email Hygiene? Email list cleaning best practices.
- What is Sender Reputation? Sender score and IP reputation definition.
Definitions make far more sense once you have seen them applied, so run a real address through the free email verifier and read the result flags — accept-all, disposable, role-based — against the pages above.
Verify an email freeGlossary FAQ
Validation and verification are used interchangeably across the industry and on this site, and both describe checking whether an address is real and safe to send to, as set out on the email validation page. Email hygiene is broader and continuous: it includes verification but also covers deduplication, suppressing unengaged contacts, and re-checking a list on a schedule as it ages. The short version is that verification is an action you run, while hygiene is a habit you keep.
Not necessarily, and this is the single most common misreading of a verification report. A valid result means the mailbox exists and the receiving server accepted the recipient during the SMTP check, which rules out a hard bounce. Where that accepted message then lands is deliverability, which depends on your authentication records, your content, your sending history and your sender reputation. Verification removes one large obstacle rather than guaranteeing placement.
Because the two problems are almost always diagnosed together. When campaign results are poor, the cause is either the addresses you are sending to or the way receiving servers judge your domain, and you cannot tell which without examining both. SPF, DKIM and DMARC are the records that decide the second half, and you can inspect your own domain's configuration with the free authentication checker.