Email deliverability glossary: 40 terms every sender should know
Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
Gmail, Outlook and Yahoo addresses carry no company signal, so B2B teams segment them. When free addresses are legitimate, how the free and role flags route them, and bulk detection.
A free email provider is a consumer mailbox service anyone can sign up for without owning a domain: gmail.com, outlook.com, yahoo.com, icloud.com, proton.me and their regional equivalents. In B2B lists, addresses at these providers carry less company signal, cannot be enriched from the domain, and usually belong to a person rather than a role, so most teams segment them from business-domain addresses and route them differently. They are not junk: sole traders, small firms and whole markets run on Gmail, and the right rule depends on the form the address came from.
The obvious ones are the global consumer services: gmail.com and googlemail.com, outlook.com, hotmail.com and live.com, yahoo.com and its country variants, icloud.com and me.com, aol.com, proton.me and protonmail.com, gmx.com and gmx.de, mail.com, Zoho's free tier and yandex.com. Then there are the regional giants that dominate specific countries: web.de and t-online.de in Germany, orange.fr and free.fr in France, libero.it in Italy, mail.ru in Russia, qq.com and 163.com in China, naver.com in Korea, rediffmail.com in India. A useful list runs to several thousand domains once aliases and country variants are included.
What they share is that the domain says nothing about the person's employer. That is the whole reason B2B teams care.
None of this means ignore them. It means do not treat a Gmail lead and a company-domain lead as the same thing.
Often. Sole traders, freelancers, consultants and very small firms frequently never register a domain. In many markets, including large parts of Latin America, South Asia and Southeast Asia, Gmail is the default business address even at established companies. Trades, hospitality, property and healthcare practices lean on free mail everywhere. And plenty of decision-makers at large companies use a personal address for anything they do not want in a corporate inbox, including evaluating software.
If your product sells to small businesses, a rule that rejects free addresses will reject most of your market. If it sells to enterprise security teams, a free address on a demo request is a fair signal to qualify by other means before a rep spends time on it.
| Signal | Free provider address | Business domain address |
|---|---|---|
| Company enrichment | None from the domain | Company, size, industry, tech stack |
| Catch-all likelihood | Effectively zero | Common at mid-size and enterprise domains |
| Bounce behaviour | Firm 550 on unknown users, strict spam filtering | Varies; some domains accept everything |
| Verification verdict | Usually a clear deliverable or undeliverable | More risky and unknown results |
| Consent and PECR status | Individual subscriber | Corporate subscriber in the UK (sole traders excepted) |
| Typical demo-form conversion | Lower | Higher |
| Typical newsletter engagement | Often higher | Lower, more role addresses |
Read the bounce row twice. Free-provider addresses are easier to verify precisely because the providers are strict: they tell you straight away whether a mailbox exists. Business domains are where catch-all and greylisting make verification harder.
Every verification response carries a checks object, and two of its fields do the routing:
{
"email": "sam@gmail.com",
"status": "deliverable",
"score": 96,
"provider": "Gmail",
"checks": {
"syntax": true, "domain": true, "mx": true,
"smtp": true, "mailbox": true, "catch_all": false,
"disposable": false, "free": true, "role": false,
"spf": true, "dmarc": true
}
}
free: true means the domain is a consumer provider. role: true means the local part is a shared function such as info, sales or support; role-based addresses and deliverability covers why those complain more. The provider field names the service, which the email provider finder exposes on its own. A free address is deliverable in the normal way; the flag changes what you do with it, not whether you can mail it.
Upload the list to the free email detector and download it back with a free column added, or run it through bulk verification, where every row carries the free and role flags alongside the verdict. From the API, POST /api/v1/bulk accepts up to 50,000 addresses per job and the results endpoint returns the same checks object per address, so a short script can split a CSV into free, business and role segments in one pass. In Google Sheets, verifying a column and filtering on the provider name does the same job for smaller lists.
Only on forms where a business address is genuinely needed, such as enterprise demo requests. On newsletters and self-serve trials, blocking free addresses removes real customers.
No, they are easier. Gmail, Outlook and Yahoo reject unknown users with a firm 550 and do not run catch-all, so verdicts are rarely risky or unknown.
Generally not. A personal address at a free provider is treated as an individual subscriber, which carries consent requirements that corporate addresses do not. Sole traders are also individuals even on a business domain.
The verification response includes a provider field, and the email provider finder tool shows it for a single address along with the MX records behind it.
Related reading
@Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
@Real-time email validation checks an address as it is typed: syntax, typos, disposable domains, role accounts, MX and an optional mailbox check. Here is how it works.
@Role accounts like info@ and sales@ belong to a function, not a person. Why ESPs distrust them, the consent problem, when B2B senders can still use them and how to detect them.
Photos: Freepik