A server says “yes” for many reasons: the mailbox might belong to a real person, or it might be a catch-all domain (accepts all email, even fake — Full guide), a role-based address (shared inbox like info@ — Full guide), or a disposable email provider account (temporary emails like someone@mailinator.com — Full guide).
The 28-point gap between “90% valid” and “62% safe to send” is where your metrics go wrong, your ESP costs inflate, and your sender reputation (the trustworthiness score that Gmail, Outlook, and Yahoo assign to your domain) erodes. That gap is what this entire guide series is about.
| Category | Risk | Typical % | Action |
|---|---|---|---|
| Safe to Send | ● Safe | 55–76% | Send confidently |
| Catch-All | ● High | 5–20% | Skip, or separate into a different send |
| Role-Based | ● Medium | 3–8% | Remove from marketing |
| Disposable | ● High | 0.5–5% | Remove. Catch at signup. |
| Free Provider | ● Low | 3–20% | Keep, but separate from business contacts |
| Invalid | ● Critical | 5–9% | Remove. Never retry. |
| Did you mean? | ● Recoverable | 1-3% | Review QEV’s suggested correction. Update as appropriate. |
| Unknown | ● Medium | 2–8% | Retry later |
How many catch-all, role-based, and invalid addresses are hiding in YOUR list?
See your actual category breakdown — not estimates.
Your content isn’t underperforming. Your list composition is the problem. The 9-point gap isn’t your subject lines — it’s catch-all and role addresses producing zeros in your denominator. Full open rate breakdown →
Every verification tool — QEV, ZeroBounce, NeverBounce, any of them — categorizes emails. The problem isn’t which tool — it’s ignoring the categories. QEV simplifies this by adding a single label to every email in your results — a safe_to_send label: true (safe to email) or false (risky — don’t include in your main send).
Whatever tool you use, the principle is the same: separate safe from risky before you send.