Document Where an Email List Came From Before You Verify or Send It
Before you verify or send to a list, write down where it came from, how the people on it joined, when you got it and who holds the file. Verification answers whether an address has a mailbox. It cannot answer why that person is on your list, and that is the question a sending platform or a recipient will ask.
Why a list loses its history
A list changes hands. A file made for one campaign becomes "the newsletter list". A purchased file is renamed "leads". A list arrives with an acquired business and nobody asks what its people agreed to. A year later no one remembers, and the file is sent to as if it were all customers.
A one-page record, made when the list arrives, stops that. The free email list provenance log builds one in your browser from six answers and the list itself.
What to record
| Field | Why it matters |
|---|---|
| List name | So two files are not confused |
| Date of the log | The list changes; the log is a snapshot |
| Source | Form, customer export, event, purchased, inherited, scraped, partner |
| When you got it | Old lists hold more dead addresses and older permissions |
| How the people came to be on it | Signed up, customers, business contacts, or not known |
| Who holds the file | A team or role, not a person, so the record outlives job changes |
| Rows, unique addresses, domains | The numbers before any cleaning |
| Mailbox check | Done or not done, and when |
| Notes | Anything the next person should know |
Row counts before cleaning matter more than they seem. If a vendor says a file has 50,000 contacts and 38,000 unique addresses remain after de-duplication, the log shows it.
What the source tells you to do
A list you collected on a form or checkout. The cleanest case. The risks are typos at entry and old addresses. Run the check and use the pre-send checklist.
A customer or CRM export. People bought from you, but contact data decays. Check the list, and read how often to re-verify.
An event or webinar list. People gave an address for one purpose. The next message should relate to it. Event attendee list cleaning covers the clean-up.
A purchased or rented list. Read the rules of your sending platform and of the countries involved first, because some platforms ban purchased lists outright. Verification does not change that. How to verify a purchased email list covers it, and the purchased email list checker shows each rule with its source.
An inherited or acquired list. Ask the seller or previous owner what the people agreed to and keep the answer with the log. How to verify an inherited or acquired email database has the routine.
A scraped list. Scraped addresses carry no sign-up. Expect more invalid rows than on a collected list, and read how to verify scraped emails.
A list shared by a partner or client. Get in writing what their contacts agreed to and who may send to them.
When the answer is "I do not know"
Record that, honestly. The log then says to find out before you send and to treat the list as not sendable if you cannot. That is a better outcome than a list sent to with a guess about its origin. A list with an unknown origin is the likeliest to produce complaints, and complaints cost more than a smaller list does.
Keep it alive
A log is only worth having if it is still true when someone reads it a year from now.
The log is not a one-off. Add a line each time the list is cleaned, merged with another, exported to a new tool or sent to:
- Date and what was done (verified, de-duplicated, merged with another list)
- Rows before and after
- Who did it
When the mailbox check is finished, change that line in the log from "not done yet" to the date. When you merge two lists, record both sources, because the merged file inherits the weaker one.
Where the log helps in practice
- A sending platform asks about an import. Platforms such as Mailchimp, Klaviyo and ActiveCampaign can review accounts after a large import. A log that says "customer export, March, 12,400 rows, checked on 13 November" is the answer they are looking for.
- A recipient asks why they got your email. You can say which list it was and how addresses got on it, and take them off.
- A teammate inherits the file. They can see in a minute what it is and whether it has been cleaned.
- You plan a clean-up. You know which lists are old, which are unknown, and which have never been checked.
What a log does not do
It records what you tell it. It does not check consent or the law, and it is not legal advice. Rules on consent differ by country, and the FTC's CAN-SPAM guide and the GDPR describe different duties. The log's job is to make sure you know the facts when you read them.
Check the list
Once the log is written, do the one step it cannot: upload the list on the verify page to see which addresses exist. 100 free checks, Google sign-in, no card.
Related: Partner and swap lists and volunteer-kept community lists.
Common questions
What is list provenance?
The history of a list: where it came from, when and how the people on it came to be there, who has handled it and what has been done to it. It is a record you keep, not a check a tool runs.
Why would anyone ask where my list came from?
Sending platforms can ask when a new account imports a large list or when complaints rise, and a recipient can ask why they were emailed. An answer you wrote down at the time is more convincing than one you reconstruct.
Does a provenance log prove consent?
No. It records what you know and what you were told. If the honest answer is that you do not know how people came to be on the list, the log says so and the list should not be sent to.
Should I verify before or after writing the log?
Write the log first. It takes a few minutes, it tells you whether the list is one you should send to, and it records the row count before cleaning changes it.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.