how we build the data

Three streams in, seven checks out.

Every record in the catalogue arrives through one of three sourcing streams, passes a compilation pipeline that removes far more than it keeps, and only then goes through seven verification checks run by third-party engines. Every record carries a source tag, so its origin can be traced after delivery.
Request 100 free rows
Accuracy reporting
verification runs monthly on the 9th, 11th or 13th
Sourcing streams
0
Verification checks
0
Records held
0 M
Verified, standard
0 %
the seven checks

Five checks remove a record. Two label it.

Verification runs through ZeroBounce, NeverBounce and equivalent providers rather than in-house scripts — they maintain continuously updated trap and blocklist intelligence, and the mailbox probing happens on their infrastructure rather than ours.

01

Syntax validation

The address conforms to RFC 5322 — no illegal characters, stray whitespace, or malformed local and domain parts.

removed

02

Domain and MX check

The domain resolves and publishes a reachable mail exchanger record.

removed

03

Disposable domain screening

The address does not belong to a throwaway or temporary-inbox provider.

removed

04

Spam trap and honeypot screening

The address does not match known trap patterns, recycled-trap intelligence or provider blocklists.

removed

05

SMTP mailbox verification

A handshake with the receiving server confirms the mailbox exists and accepts mail, without delivering a message.

removed

06

Role account detection

Generic mailboxes — info@, sales@, admin@, support@ — are identified and segmented separately.

flagged

07

Catch-all classification

Domains that accept mail to any address cannot be individually confirmed, so they are labelled accept-all rather than presented as verified.

flagged

before verification

Where records come from, and what happens before a single check runs.

Verification costs money per address, so the pool is cleaned first — there is no point probing a mailbox on a record that should never have been in the file.
  • stream 01
Permission-based collection
Newsletter and subscription forms, gated content downloads, webinar and event registrations, preference-centre signups. Double opt-in where the collecting property supports it.
  • stream 02
Public web and business directories
Company websites, published directories, corporate and trade registries, and professional listings where contact details are published for the purpose of being contacted.
  • stream 03

Licensed data partners

Records acquired under written agreement from vetted providers. Each agreement requires the partner to warrant it holds the right to license the data onward.
  • then
Compilation and standardisation
Normalisation of casing and field mapping; exact dedupe on email then fuzzy matching on name plus domain; malformed and placeholder records dropped; completeness scoring; indexing by country, industry, company size and role seniority.
the four grades
  • outcomes

Records leave verification in one of four states.

Standard orders contain Valid records only. Accept-all and Role records are available on request, in clearly labelled segments, so you decide whether to mail them and at what volume. Invalid records are removed — not resold, not held back for a cheaper tier.

every record carries a source tag and a verification date

valid

All seven checks passed. What a standard order contains

accept-all

Domain accepts anything; mailbox unconfirmable. Labelled, on request

role

Generic mailbox. Segmented separately, on request

invalid

Removed. Not sold, not counted

Request 100 free rows
questions

Questions about how the data is built

Why outsource verification instead of building it?
Trap and blocklist intelligence has to be continuously updated to be worth anything, and mailbox probing at volume can damage the reputation of whoever runs it. Outsourcing both is the honest engineering choice, not a shortcut.
A large proportion — duplicates across directories, malformed rows, and placeholder records. We do not publish a single percentage because it varies enormously by source, and a made-up figure would be worse than none.
Yes. Every record carries a source tag; query a row and we will tell you which stream it came from.
No, and you should distrust anyone who does. Standard lists are up to 85% verified, with a 99% build available on request.
  • 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

WhatsApp Us
Call Us
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.

Accuracy reporting

85% / 99%

What we measure, what we will not claim, and the four grades a record can carry.

Update frequency

9th · 11th · 13th

One verification pass a month, on one of three dates, plus a re-run before dispatch.

Compliance center

gdpr / can-spam

Who is responsible for what, and the obligations that stay with the sender.

Opt-out & removal

permanent

How to be removed, how suppression works, and what permanent actually means.

  • ask before you buy, not after

The pipeline is only worth as much as the rows it produces. Test 100.

Sales and service are reachable 24/7 on WhatsApp at +1 (315) 215-1563, or at [email protected].
Download 100 free rows
Message us on WhatsApp