Article

How to Read an Email Verification Results File: A Step-by-Step Guide

By Unlimited Verifier Team ·

Diagram showing the steps to read an email verification results file, starting with the status column and reason fields.

Summary

To read an email verification results file, start with the status column, which sorts each address into Valid, Invalid or Risky. Then check the reason fields to see how much to trust each verdict, and reconcile your row counts before sending anything.

To read an email verification results file, start with the status column, which sorts every address into one of three verdicts: Valid (safe to mail), Invalid (suppress) or Risky (decide before sending). Then read the reason fields, because they show how far to trust each verdict.

Most list-cleaning mistakes start with someone counting the status column and stopping there. The file records how confident the verifier is about each address, and how you handle the uncertain rows decides whether your next campaign reaches the inbox or builds complaints. This guide covers each column, what the categories mean at the SMTP level, a step-by-step spreadsheet read, a worked example with arithmetic, and the mistakes that cost teams the most. For the full process around the file, see our bulk email list verification workflow. If you are still choosing a provider, our guide to best email verification tools compares options, and how to choose an email verifier explains the criteria. The reading skills below apply to any verifier's output.

Quick answer

What is in an email verification results file?

A results file is your original list with verification output added. Expect your original email column, any custom fields you uploaded, a status column, and columns for the individual checks: syntax, domain and MX records, the SMTP mailbox result, and flags for catch-all, disposable and role-based addresses. Column names vary between tools and export formats, so read the header row before you write any formulas.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, flags disposable and role-based addresses, and sorts results into Valid, Risky and Invalid. Results export as CSV, Excel or JSON, and each format calls for a different habit.

Format Best for Watch out for
CSV Re-importing into an ESP or CRM, scripts, and your master copy Double-clicking a CSV in Excel can strip leading zeros from ID fields and garble accented characters. Use the import wizard and set those columns to text.
Excel Filtering, pivot tables, and sharing with non-technical colleagues Excel rewrites numbers and dates on save. Keep the CSV as the source of truth.
JSON API pipelines and automated routing Not spreadsheet-friendly. Let a script read it, or flatten it into a table.

For how format rules apply when you upload, see what file formats email verifiers accept.

Bottom line: Treat the CSV as your master file, and use Excel only to look at it.

What do Valid, Risky and Invalid actually mean?

Valid means the verifier found a deliverable route to a mailbox. Invalid means it found a definite failure. Risky means it could not confirm either outcome, or found a condition that makes sending a gamble. These are verdicts on deliverability, not on whether the person wants your mail. For a deeper walk-through of the three buckets, read valid vs risky vs invalid email results explained.

The categories trace back to SMTP reply codes. RFC 5321 defines the first digit of each reply: a 4yz code is a transient negative reply ("try again later"), and a 5yz code is a permanent negative reply. A 5xx response is strong evidence of failure. A 4xx response is a postponement, which is why a temporary error should never be treated like a rejection.

Valid still isn't consent. An address can pass every check and belong to someone who left the company two years ago and never reads that inbox. Verification answers "can this mail arrive?", not "does this person want it?"

Bottom line: Read the categories as deliverability verdicts. The file cannot answer the consent question.

How do you read the reason behind an Invalid result?

Read the reason before you suppress, because the reason tells you whether a row is permanently dead or worth a second look. Most Invalid rows fall into three groups.

  1. Syntax failure. The address is malformed: a missing @, a space, consecutive dots or illegal characters. These usually come from typing errors on forms or from broken concatenation during import. Suppress them, and fix the form that let them in. If your Invalid share is far higher than expected, see what to do if 30 percent of your list is invalid.
  2. Domain or MX failure. The domain has no mail exchanger record. This is often a misspelled provider name, an expired domain, or a company that moved its mail hosting. Suppress consumer addresses. For B2B contacts, check the company domain once before deleting, because a misconfigured domain is recoverable and the contact may not be.
  3. Mailbox rejection. The receiving server said the mailbox does not exist, typically with a 550 reply and enhanced status code 5.1.1. RFC 3463 defines 5.1.1 as "bad destination mailbox address." This is the strongest evidence in the file. Suppress these permanently. For what to do with the rest of the Invalid rows, see what to do with invalid emails after list cleaning.

The mailbox-rejection group also works as a diagnostic. If it clusters in one import batch or one old source, you have found where the data went bad.

Bottom line: Suppress syntax and mailbox rejections without hesitation, and check B2B domain failures once before deleting.

Why are Risky addresses the hardest rows to read?

Risky rows are hard because the verifier cannot prove either outcome, and each sub-type needs a different action. Split the bucket before you decide anything.

For a single doubtful address, such as a key account that came back Risky, a free email checker lets you spot-check it before you decide.

Bottom line: Break Risky into its four sub-types. Each needs its own action, and only unresolved checks should wait for a re-run.

What should you check before you act on the file?

Before acting, reconcile the totals and look for duplicates. A summary can look clean while the underlying file has problems. This is the six-pass read I recommend.

  1. Reconcile row counts. Output rows should equal input rows minus any you removed. A mismatch usually means a parsing problem, such as commas inside unquoted fields. Fix the source file and re-run. See how to clean a messy CSV of emails before upload.
  2. Check the totals. Valid + Risky + Invalid must equal the total you uploaded.
  3. Deduplicate on a normalised address. Lowercase the address. For gmail.com, remove dots and anything after a + sign, because Gmail delivers those variants to the same mailbox. Don't apply Gmail's rules to other providers.
  4. Group by source. Calculate the Valid share for each import batch, form or event. This step usually reveals the most actionable finding in the file.
  5. Review the Risky sub-flags. Confirm the catch-all, disposable and role counts make sense for your audience.
  6. Archive everything. Export all three buckets and the summary counts with a date and list name before the results expire.

The source check matters because data quality is rarely uniform. A trade-show import with a 60% Valid share sitting inside a list with an 89% Valid share is a finding in itself. You can isolate it, segment by verification status, and decide whether to re-source or retire it. Teams in email verification for ecommerce and saas often find that signup-form and import sources differ sharply. Keep the source field through verification. Our guide to keeping custom fields shows how.

Bottom line: Reconcile first, deduplicate second, then group by source, because that is where the story usually sits.

How do you read a results file step by step in a spreadsheet?

Follow these steps on your own export. The formulas assume a status column with the labels Valid, Risky and Invalid. Replace the column letters and labels with the exact headers in your file.

  1. Keep an untouched copy. Save the original CSV with a name that includes the list name and date, such as crm-import-2024-06-12-results.csv. Work on a duplicate.
  2. Open the CSV with the import tool, not by double-clicking. In Excel, use Data > From Text/CSV. In Google Sheets, use File > Import. Set ID, phone and ZIP columns to text so leading zeros survive.
  3. Read the header row. Note the column letters for the email, status, reason, source and any Risky sub-flag columns.
  4. Count the total. In a summary cell, enter =COUNTA(A:A)-1 (the minus one excludes the header, and A is your email column).
  5. Count each status. Enter =COUNTIF(C:C,"Valid"), then the same for Risky and Invalid, changing the label each time.
  6. Reconcile. Add the three counts and compare them with step 4. If they differ, stop and find the parsing problem before you go further.
  7. Calculate the Valid share by source. Use =COUNTIFS(B:B,"Trade show",C:C,"Valid")/COUNTIF(B:B,"Trade show"), changing the source label. Or insert a pivot table with source as rows and status as columns.
  8. Save a summary tab. Record the date, list name, the three counts, the per-source Valid shares and the file name, then export the archive within the retention window: 24 hours on Free and 30 days on Pro.

Bottom line: Five formulas and one pivot table will tell you more than the headline percentage.

What does a real results file look like in numbers?

The figures below are illustrative. The plan limits are real. Here is a SaaS company's 38,400-row export, read end to end.

Step 1: Deduplicate. 38,400 − 1,488 duplicates = 36,912 unique addresses.

Step 2: Respect the list cap. Pro allows lists of up to 25,000 emails each, so split the file into 25,000 + 11,912. Both fit under the cap. Keep a row ID so you can merge the two result files back together. The split a large CSV guide covers the mechanics.

Step 3: Read the totals (hypothetical results).

Status Count Share of 36,912
Valid 31,200 84.5%
Risky 3,900 10.6%
Invalid 1,812 4.9%
Total 36,912 100%

Step 4: Break down the non-Valid rows.

Step 5: Group by source. The trade-show import contributed 5,400 unique addresses, of which 3,240 were Valid (60.0%). Everything else gave 27,960 Valid out of 31,512 (88.7%). The trade-show import is 14.6% of rows (5,400 ÷ 36,912), but it accounts for 2,160 of the 5,712 non-Valid rows, or 37.8%. That one batch is where the problem sits.

Step 6: Plan the re-check. Re-running the 3,900 Risky rows with deep verification uses 3,900 of the 25,000 monthly deep verifications, leaving 21,100. Standard verification is unlimited on every plan, so there is no per-email fee for re-checks at that level.

Step 7: Price the work. Pro is $29 a month, or $25 a month billed annually. Spread over this one file, monthly billing works out to about $0.79 per 1,000 addresses ($29 ÷ 36.912), and annual billing to about $0.68. For how to compare costs more broadly, see email verification pricing.

Why the plan matters: On Free, a list of 36,912 needs 247 lists of 150 (36,912 ÷ 150 = 246.08, rounded up). Free allows 25 lists a month, or 3,750 emails, so this file would take roughly ten months. Free suits small lists and tests. A list this size belongs on Pro, and you can upload and verify a list directly once the file is split.

Bottom line: The headline is 84.5% Valid, but the useful finding is that one source produces 38% of the problems, and that is where to act.

How do you read results when using the API?

Read API output the same way: status first, reason second, and log both. Pro includes API access, with up to 100,000 emails a month, and bulk batches of up to 10,000 emails per request. Single-email checks suit signup forms. The email verification API page explains how to generate keys, and email verification API and automation covers common workflow patterns.

For the 36,912-row example, 10,000 per request means four requests: 10,000 + 10,000 + 10,000 + 6,912. Store each response with its reason fields rather than only the verdict, so you can rebuild the source breakdown later. For wiring checks into signup flows, see real-time email validation.

Unlimited Verifier has no native ESP, CRM or Zapier integrations. Automated routing therefore means calling the API from your own scripts, or exporting, verifying and re-importing manually.

Bottom line: Log the reason with every verdict, because you will need it when you audit the file later.

What should you do with each result?

Use the status and reason together. This table is the decision layer.

Status Typical reason What it means Action
Valid Syntax, MX and mailbox checks pass Deliverable route confirmed Send, starting with the most engaged contacts
Invalid Syntax error Typed incorrectly at source Suppress, then fix the form
Invalid No mail route Domain dead or misconfigured Suppress. For B2B, check the domain once
Invalid Mailbox rejected (5.1.1) Mailbox does not exist Suppress permanently
Risky Catch-all Server accepts everything; mailbox unprovable Hold back. Send last, in a small test
Risky Disposable Throwaway domain Suppress from marketing sends
Risky Role-based Shared inbox Exclude from promotional sends
Risky Unresolved (4xx or timeout) Temporary or throttled Re-check later. Don't suppress

Once the file is read, use how to segment a list by verification status to build your sending segments.

Bottom line: Pair every status with a reason and an action. A status alone can't tell you what to do.

What are the most common mistakes when reading the file?

Bottom line: Most of these mistakes come from reading one column in isolation. Read status, reason and source together.

Why does reading the file correctly matter?

Reading the file correctly protects both deliverability and compliance. Mailbox providers track complaints closely. Google's sender guidelines set 0.3% as the spam-rate level bulk senders must stay below, and Google's Postmaster Tools guidance recommends staying under 0.1%. Where the two figures differ, plan to the stricter 0.1%. Sending to addresses that don't belong to engaged recipients is a common route to complaints. Yahoo's sender requirements point the same way.

A clear audit trail also supports your email verification compliance and hygiene practice if a regulator or a platform asks how you built your list. Keeping the dated results file, the summary counts and the source breakdown is the simplest version of that record.

Bottom line: A file read carefully becomes evidence of good list practice, not just a count.

How we compared (and limitations)

This article is based on public documentation: RFC 5321 for SMTP reply codes, RFC 3463 for enhanced status codes, and Google's and Yahoo's published sender guidelines. We have not benchmarked any vendor's output. Status labels and column names differ between verifiers, so the categories here describe common patterns, and the header row of your own file is authoritative. Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's stated number, not an independent benchmark. The worked-example percentages and counts are illustrative. Plan limits reflect Unlimited Verifier's published facts at the time of writing. For broader guidance on sender practice, the M3AAWG website hosts industry best-practice documents.

Bottom line: Use status, reason and source together, and check your own file's headers before trusting any formula.

Worked reconciliation example

Item Count
Uploaded 10,000
Removed duplicates 400
Processed rows 9,600
Valid 7,200
Risky 1,500
Invalid 900
Check: 7,200 + 1,500 + 900 9,600 (matches)
Valid share by source A 91%
Valid share by source B 58% (investigate)

Frequently asked questions

What does Valid mean in an email verification results file?

Valid means the verifier found a deliverable mailbox, with the domain, MX records and SMTP check all passing. It is generally safe to send to. Valid results still carry some uncertainty, so keep an eye on bounce rates after your first send.

What does Invalid mean in email verification?

Invalid means a definite failure, such as a permanent 'mailbox does not exist' response or a malformed address. Suppress these addresses from every campaign, since mailing them raises bounce rates and can hurt sender reputation.

What is a Risky email address?

Risky is the uncertain bucket. It usually covers catch-all domains that accept any address, disposable or role-based addresses, and mailboxes the check could not confirm. Decide on these separately rather than mailing them in your first campaign.

What is a catch-all domain?

A catch-all domain is a mail server set up to accept email for any address on that domain, whether or not the mailbox exists. Verifiers cannot confirm individual mailboxes there, so those addresses appear as Risky.

Why does my Valid + Risky + Invalid total not match my upload?

Rows may have been removed during processing, such as duplicates or blank lines, or the file may have been split across exports. Compare the output row count with your input count and account for each difference before using the results.

Should I send to Risky email addresses?

Usually not in your first campaign. Send to Risky addresses only after you have assessed them, for example by segmenting by engagement history or sending a small, low-stakes test first.

Why should I group results by source?

A single source with a much lower Valid share often points to a dirty import, such as scraped or old lists. Grouping by source shows which acquisition channel is producing poor data so you can fix it at the origin.

How long are verification results kept?

Retention depends on the plan. Per the article, results are kept 24 hours on the Free plan and 30 days on Pro, so export and archive the file the same day you run it.

Should I open the CSV directly in Excel?

Be careful. Double-clicking a CSV in Excel can strip leading zeros from ID fields and garble accented characters. Use the import wizard and set those columns to text, and keep the CSV as your master copy.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.