To validate an email list from a CSV you need three things: a column with the addresses, a file the dashboard can read, and a rule for how you will use the results. This guide walks through the real ByeBouncer dashboard flow, limits included, and ends on the step people forget most: getting the results back into your system without losing contacts.
What list validation does and does not do
Validating a list means checking each address on its own: whether the format is correct, whether the domain can receive mail and, when the server allows it, what the mailbox responded. It is not a delivery guarantee. A server accepting an address does not mean the message reaches the inbox or gets read, and an undetermined result does not mean the address is invalid.
It does not decide for you either. The dashboard gives you data per address; you decide what to do with each group based on the kind of sending you do and how much bounce you can tolerate.
How to validate an email list from a CSV: prepare the column
The dashboard accepts CSV, TXT or XLSX files up to 20 MB. A few minutes of preparation prevent most problems:
- Keep one column with the addresses and, if you can, give it a header such as “email”, “correo” or “mail”. With a header, the dashboard uses it to pick the column; without one, it picks the column with the most email-shaped cells.
- Use a comma as the separator. The dashboard reader does not interpret the semicolon that some localized Excel versions produce on export. If your file comes out that way, save it again as a standard comma-separated CSV.
- Do not delete odd-looking rows by hand. Catching mistyped addresses is part of validation, so the dashboard does not filter them out before checking. Leave them in and review them in the results.
- Remove columns you do not need only if it makes your job easier; it is not required. You choose the email column and can change it in the preview.
CSV has a public specification (RFC 4180): fields containing commas must be wrapped in quotes. If names or company fields contain commas, make sure your exporter quotes them.
Upload the file and review the preview
In the dashboard, open the bulk verification section and drop in the file. Before anything is charged you will see a preview with the first five rows, the chosen column highlighted, and a summary with total rows, unique emails and credits to be debited.
Two rules are worth keeping in mind here:
- The dashboard removes duplicates and lowercases addresses before creating the job. You are charged only for unique emails, and that is the number shown in the summary.
- Each job accepts up to 5,000 unique emails. If your file has more, the dashboard tells you and does not create the job: split the list into parts and upload them as separate jobs.
Check the column before confirming. If the selector points at the wrong column, the summary changes and you will notice it in the unique count. When it adds up, queue the job.
While the job runs
The job is processed in the background, so you can close the tab and come back. The detail page shows progress, counters per result and, once there is enough data, an estimated finish time that is recalculated from what has been observed. It is an estimate: it depends on the domains in your list and how their servers respond, so do not treat it as a deadline.
If the service cannot check some addresses because of a temporary limit, the detail page counts them separately as unverified queries. They are not charged and their credits are included in the job refund. You can retry them later in another job.
Reading the results: valid, invalid and the rest
When it finishes, the dashboard shows five counters: valid, invalid, with traits to review, unknown and unprocessed. A cautious reading of each group:
- Valid: passed the available checks. Still no delivery guarantee, but this is the group with the best signal to start with.
- Invalid: the address has a verifiable problem, such as a wrong format or a domain that cannot receive mail. These are usually the ones to remove or correct.
- With traits to review: not an error, but the address has traits you may want to handle differently, such as a shared mailbox or a domain that accepts any address. A trait is not a blocking rule; it depends on your own criteria.
- Unknown: the server did not give a clear answer. A timeout, a temporary limit or a catch-all domain leaves the question open. It is not the same as invalid.
Do not delete the unknown group. Put it in its own segment and check it again later. Some cases resolve on a second attempt; others will stay unanswered, and you will have to decide whether to use them in small sends, confirm them with a confirmation email, or drop them.
Download and bring the results back to your system
Once the job is done, the “Download CSV” button generates a temporary link. Download the file and keep it: the job also has an expiry date, visible on its detail page.
The CSV includes, for each email, these columns: input_index, input, normalized, deliverability, checks_json, attributes_json, observed_at and result_format. Two details change how you match it against your own data:
- input_index is the position within the list that was sent, already deduplicated and lowercased, not the row number of your original file. To join results back to your system, use the lowercase address, not the index.
- The detail of each check travels in checks_json and attributes_json. If you import into a spreadsheet or CRM, keep those columns alongside deliverability and observed_at: that way you will know why an address landed in each group and when it was checked.
A simple way to do it: add a result column to your original list by looking up each lowercase address. Then filter by group and define an action for each one: send, correct, review later or exclude.
What to store and what not to promise
Store the result with its date. An address that is valid today may stop being valid in a few months, so a list validated long ago needs another pass before a large send. And do not present validation as proof of interest or consent: it states technically what could be checked, nothing more.
If you need to validate from a form or from your own system, the dashboard is not the only route: the API accepts single addresses or batches, and your technical team decides how to connect it. For lists over 5,000 unique emails, the procedure is the same, repeated in parts.
See what email verification checks →
Have a list ready to try? Create an account, upload a small file and compare the output against addresses you already know before processing the full list.