Bulk Email Verification

Bulk email verification is mass-validating a list of addresses in one operation. You upload a file with thousands or millions of rows, the system checks each address, and returns a status-tagged output file.

How the process works

It starts with a file, typically CSV or TXT, occasionally XLSX. The system parses it, pulls out the email column, and queues the addresses for processing.

Each address goes through the same checks as a single-address lookup: syntax analysis, DNS/MX query, SMTP connection, and additional checks for catch-all domains, disposable mailboxes, and role-based addresses. The difference is scale and how the system handles it.

In batch mode, the validator groups addresses by domain. Instead of issuing a separate DNS query for every gmail.com address, it queries the MX record once and reuses the result for all addresses on that domain. SMTP connections get the same treatment: multiple addresses from the same domain go through a single connection.

Processing speed

Professional services handle 10,000 to 100,000 addresses per hour. What slows things down: mail server response times, greylisting, rate limiting from large providers, and the number of unique domains in the list.

A 50,000-address list dominated by Gmail and Yahoo runs in 20-40 minutes. The same size list with hundreds of different corporate domains can take several hours — each new domain needs its own DNS query and SMTP handshake.

Output statuses

The output file assigns a status to each address. Typical breakdown:

• Valid — the address exists and the server confirmed receipt.
• Invalid — the address does not exist or the domain has no mail server.
• Risky — catch-all domain, role-based address, or disposable mailbox. May work, but carries delivery risk.
• Unknown — the server did not respond, timed out, or returned a temporary error. Worth retrying.

Better services also return a rejection reason for each address, not just a valid/invalid split. The mail server response, code and text together, separates deleted mailboxes from full ones and from domains that take no mail at all, and each of those calls for a different decision about the segment.

When to use it

Before any send to an old list. If it has not been checked in a few months, dead addresses have piled up: people changed mailboxes, domains expired, corporate accounts closed when employees left.

When migrating between ESPs. A new provider starts your sender reputation from scratch, and a high bounce rate on early campaigns can permanently damage it. Since May 2025, Google and Yahoo enforce hard limits for bulk senders: bounce rate under 2%, spam complaints under 0.3%. Exceeding either threshold gets your mail throttled or blocked.

As routine hygiene every 3-6 months, even with real-time validation on signup. Addresses go stale: corporate mailboxes close when employees leave, free accounts expire after long inactivity.

Input file requirements

One email per line is the simplest format. CSVs with multiple columns work too — the validator identifies the email column automatically or asks you to point to it.

Use UTF-8 encoding. Files in CP1251 or ISO-8859-1 can trip up on addresses with non-Latin characters. Most services detect encoding automatically, but converting the file beforehand removes the uncertainty.