How we verify
Seven checks, run by someone other than us.
Verification runs through established third-party engines — ZeroBounce, NeverBounce and equivalent providers — not in-house scripts. Two reasons: they maintain continuously updated trap and blocklist intelligence, and the mailbox probing happens on their infrastructure rather than ours, so it never touches a sending reputation.
Every address passes these, in this order.
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 such as info@, sales@, admin@ and 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
Where the records come from, and what happens before a single check runs.
- stream 01
Permission-based collection
- stream 02
Public web and business directories
- stream 03
Licensed data partners
- 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.
- On request · 99% verified
Need 99% verified? Ask us on WhatsApp.
- 99% verified · custom build
Quoted per list
Whatsapp or Call Us : 17879704581
Who is responsible for what.
- emailproleads is responsible for
Recording and retaining the source of each record
Running the verification pipeline above
Maintaining the global suppression file
Honouring access and erasure requests received directly
Contractual warranties from licensed partners
- the buyer is responsible for
Establishing a lawful basis for the campaign in each market
Accurate sender identity, subject lines and physical address
A working unsubscribe mechanism, honoured promptly
Applying your own suppression and complaint handling
Sending domain warm-up and sensible send volumes
- four grades
Records leave verification in one of four states.
verification runs monthly on the 9th, 11th or 13th · lists are re-run before dispatch
Valid
All seven checks passed. This is what a standard order contains
accept-all
The domain accepts anything, so the mailbox cannot be individually confirmed. Labelled, on request
Role
Generic mailbox — info@, sales@, admin@. Segmented separately, on request
Invalid
Removed. Not sold, not counted, not held back for a cheaper tier
Questions about verification
How often is verification run?
Why use third-party engines instead of your own?
Do you claim 100% accuracy?
What is the global suppression file?
Where do I send an erasure request?
Everything else you can check before you pay
Five pages, no gates. If something here does not answer your question, ask us on WhatsApp before you order rather than after.
no card
100 real rows from any file, in the same 11 columns as the paid version. No card, no call.
11 columns
Every column named, with what it holds and how often it is populated.
Standard lists are up to 85% verified. A 99% build is available — ask on WhatsApp first.
7 days
Bounce log above 5% inside 7 days and the file is refunded in full. In writing.
- ask before you buy, not after
