Update frequency
update frequency
One verification pass a month. The 9th, 11th, or 13th.
Contact data decays whether or not anyone is watching. Ours gets a full verification pass every month, run on one of three dates, and any list is re-run through verification again before it is dispatched — so the age of the underlying record does not determine deliverability at the point you receive it.
the verification date sits on every single row
Pass per month
0
Possible dates
0
Checked before you get i
0
X
Per file, one time
$
0
the dates
The 9th, the 11th, or the 13th. Every month.
One full verification pass a month, run on one of three dates. Which of the three depends on provider queue capacity — we would rather name the window honestly than promise a date we then miss.
or
0
or
0
of each month
0
- what happens in a pass
01
The full catalogue is queued to the verification providers — ZeroBounce, NeverBounce and equivalents.
02
Each address goes through the seven checks; Invalid records are removed from the build entirely
03
Role and catch-all records are re-labelled, since a domain’s configuration can change between passes.
04
The verification date on every surviving row is updated, which is the date you see in your file.
why monthly
Monthly is what we actually run, so monthly is what we say.
Daily and real-time refresh claims are common in this category and mostly describe a lookup API rather than a verified file. We run one pass a month and re-verify on dispatch — and we would rather tell you that than sell a cadence we do not operate.
- the pass
Monthly, on one of three dates
A full pass over the catalogue. Which of the 9th, 11th or 13th depends on provider queue capacity that month.
- on dispatch
Re-verified before it ships
Whatever the date of the last pass, your specific list goes through verification again before delivery. This is the check that matters most to you.
- on the row
A date, not a claim
Every row carries the date it last passed. Drop anything older than you are comfortable with — for cold outreach, 60 days is a sensible ceiling.
- not offered
Real-time or daily refresh
We do not run it, so we do not sell it. If a live lookup is what you need, a platform API is the right product and we are not it.
- On request · 99% verified
Need 99% verified? Ask us on WhatsApp.
Our catalogue databases are verified up to 85%. When a campaign can’t carry that, we build the slice you need to 99% verified — re-checked against live mail servers before we hand it over. Tell us the country, industry and volume; we quote and turn it around by hand.
- 99% verified · custom build
Quoted per list
Reply within business hours, 7 days a week. English plus 8 other languages.
Whatsapp or Call Us : 17879704581
decay by field
Not every field ages at the same speed.
Worth knowing which columns go stale first when you decide how long to keep using a file. These are directional, based on how the underlying sources behave — not measured guarantees.
| field | ages | why |
|---|---|---|
| Work email | fastest | Dies the moment someone leaves. This is the field the monthly pass exists to protect, and the one dated on the row. |
| Job title | fast | Promotions and reorganisations. A marketing director row is the most volatile of the role groups. |
| Phone number | medium | Direct lines change with a move; company numbers persist much longer. |
| Company size / revenue | slow | Published annually at best, so it moves in bands rather than continuously. |
| Company name, domain, industry, location | slowest | Changes only on rebrand, relocation or acquisition. |
what you can do about decay
- practical
Use the date column. It is there for exactly this.
A file is not a subscription, so nothing auto-refreshes — which means the verification date is your control. Filter on it, send to the freshest rows first, and if your copy of a file has aged out, ask us for a re-verified copy rather than buying it again.
ask for a re-verified copy if your file has aged · [email protected]
every row
Carries the date it last passed verification
our advice
For cold outreach, drop rows older than 60 days
free
A re-verified copy if yours ages out — just ask
on request
A 99% verified build, if your domain is new
questions
Questions about update frequency
Which of the three dates is it?
It depends on provider queue capacity that month. Naming a window of three dates we hit is more useful than naming one date we would sometimes miss.
Does my file update after I buy it?
No — it is a file, not a subscription. That is the trade for paying once. If it ages out, ask and we will re-verify your copy.
So what does "verified before dispatch" mean?
Your specific list is put through verification again at the point of order, regardless of when the last monthly pass ran. It is the reason the date on your rows is recent even for an older record.
Do you offer a real-time API?
Not as a published product. For an OEM or licensing arrangement, delivery mechanism and refresh cadence are agreed in the terms.
the rest of quality
Five pages, no gates
Everything about how the data is built, measured, refreshed and removed. If a question here is not answered, ask on WhatsApp before you order rather than after.
3 streams
The three sourcing streams, the compilation pipeline, and the seven verification checks.
85% / 99%
What we measure, what we will not claim, and the four grades a record can carry.
gdpr / can-spam
Who is responsible for what, and the obligations that stay with the sender.
permanent
How to be removed, how suppression works, and what permanent actually means.
- ask before you buy, not after
Check the verification dates on 100 free rows before you commit.
Sales and service are reachable 24/7 on WhatsApp at +1 (315) 215-1563, or at [email protected].
