Email identity verification confirms that an email address is real, belongs to an active mailbox, and is owned by the person or business that provided it. It is not the same as email authentication — SPF, DKIM, and DMARC verify the sender's domain reputation, not whether the contact on your list actually exists or is who they claim to be.
Marketers and sales teams use email identity verification before sending campaigns, importing contacts into a CRM, or processing sign-up forms. The goal is to separate real addresses from fake ones, mistyped entries, disposable inboxes, and role accounts that inflate list size without delivering real engagement.
What does email identity verification actually check?
A complete verification run works through several layers, each catching a different type of bad address.
Syntax check — Confirms the address follows valid format ([email protected]). Catches typos like "user@gmailcom" or "user@@domain.com." Fast, runs first, but only eliminates the most obvious errors.
Domain check — Queries DNS to confirm the domain exists and has active mail exchange (MX) records. An address at a domain with no MX record cannot receive email. Catches fake domains, expired domains, and misspelled domain names.
SMTP verification — Connects to the mail server and probes the specific mailbox without sending a message. The server responds with whether the mailbox exists. This is the layer that separates real addresses from invented ones at real domains.
Catch-all detection — Some domains accept all incoming SMTP probes regardless of whether the mailbox exists (catch-all configuration). EmailAddress.ai resolves catch-all domains using active inbox signal data rather than marking every address as "unknown." This matters because 30-40% of B2B email lists contain catch-all domain addresses that standard verifiers cannot resolve.
Disposable and temporary address detection — Identifies addresses from services like Mailinator, Guerrilla Mail, and thousands of similar providers. These addresses exist temporarily for sign-up purposes and are useless for follow-up.
Role account detection — Flags addresses like info@, support@, admin@, noreply@, and team@ that route to shared inboxes or ticketing systems. Role accounts rarely represent a real decision-maker and typically generate high spam complaint rates when mailed.
What does email identity verification miss?
Verification confirms an address exists and can receive mail. It does not confirm that the person who gave you the address is who they say they are. Someone can provide a real, active email address that belongs to a different person. Verification passes. The address is deliverable. But the contact data is still wrong.
For this reason, high-intent B2B campaigns use double opt-in alongside verification — the contact has to click a confirmation link from the address they provided, proving they own and control it. Verification alone cannot replicate that ownership signal.
Verification also does not catch addresses that have gone inactive since the last check. B2B email addresses decay at roughly 22% per year as employees change roles, leave companies, or get reassigned. A list verified six months ago may have a materially different bounce rate today. How often you should re-validate depends on list size and campaign frequency.
How does EmailAddress.ai handle catch-all verification?
Standard SMTP verification returns "catch-all" for any address at a domain that accepts all probes. Most verifiers mark these addresses as risky and exclude them from sending. For B2B lists, this means suppressing a large portion of potentially deliverable contacts.
EmailAddress.ai resolves catch-all addresses by connecting a sending inbox to the platform and using active signal data to determine whether the specific mailbox receives real mail. The result is a confidence score: addresses scoring 70 or above are safe to send to, 40-69 warrant selective use, and below 40 should be suppressed. This approach recovers contacts that blanket suppression would have discarded.
When should you run email identity verification?
- Before a campaign send — Run verification if the list is older than 90 days or sourced from a third party
- On sign-up form submissions — Real-time API verification catches fake and disposable addresses at the point of entry
- Before CRM import — Prevents bad data from entering your system at the source
- After list purchase or enrichment — Third-party data degrades in transit; verify before use
- When bounce rate exceeds 2% — A bounce rate above 2% at most ESPs triggers account review or suspension
Frequently asked questions about email identity verification
What is the difference between email identity verification and email authentication?
Email identity verification checks whether a contact address is real and deliverable. Email authentication (SPF, DKIM, DMARC) protects your sending domain's reputation by proving messages come from an authorized server. They solve different problems: verification is about the recipient address, authentication is about the sender domain.
Can email identity verification detect fake sign-ups?
It catches disposable addresses, role accounts, and non-existent mailboxes. It cannot confirm the person giving you the address actually owns it. For that, double opt-in is the only reliable signal. Verification and double opt-in work together: verification catches the address-level problems, double opt-in confirms ownership.
How accurate is SMTP verification for B2B email addresses?
For non-catch-all domains, SMTP verification is reliable. For catch-all domains, which make up a significant portion of B2B lists, standard SMTP probes cannot determine whether a specific mailbox exists. EmailAddress.ai resolves this using active inbox signal data, returning a deliverability confidence score rather than a binary valid/invalid result.
How often should I verify my email list?
B2B lists should be verified every 60 to 90 days for active senders. Lists that have not been emailed in six months or longer should be fully reverified before any send. Data decay in B2B contacts runs at roughly 22% annually, meaning a quarter of your list may have changed in a year.
What happens if I send to unverified lists?
Hard bounces above 2-5% (thresholds vary by ESP) trigger account review or suspension at most email service providers. Spam complaint rates above 0.1% at Gmail or 0.3% at most other providers trigger deliverability penalties. Unverified lists accelerate both outcomes. See bounce rate benchmarks by ESP for specific thresholds.
Get email addresses your campaigns can actually reach
EmailAddress.ai verifies email addresses at the syntax, domain, SMTP, and catch-all level — and resolves the catch-all domains that other verifiers mark as unknown. Run a bulk verification on your list or use the real-time API to verify at the point of capture.