What does “quality-first deliverability” mean?

We verify email addresses before export using a multi-layer pipeline (4-Layer). In recent production samples sent through an independent ESP, exports achieved 100% delivered with 0% bounces. Results depend on sender reputation, warm-up, content, and compliance.

Are undeliverable emails charged?

No. Undeliverable emails are excluded automatically during export and do not count toward your quota.

Data Quality

Clear quality rules that protect customers, reduce bounce, and keep exports fair.

Quality-first deliverability

Our verification is quality-first and powered by 4-Layer multi-step checks. Exports are validated before download to reduce hard-bounce risk versus basic list validation.

Note: results can vary by country, niche, mailbox provider, and sender reputation.

4-Layer

Multi-layer verification

Checked before export

Bad emails charged

Excluded automatically

Live

Verification at export

Fast browse, strict export

Country datasets

Global on request

Real-world delivery proof

📁 Source: MyCQL Export (CSV)
📊 Test: Real Cold Email Campaign
🗓 Date: Q1 2026
We don’t rely on theoretical scores alone. We validate quality using live delivery tests through independent ESPs.

613 emails

Sent via Brevo (live SMTP)

100% delivered

0% bounced / 0% blocked

0% complaints

Mixed providers (Gmail, Outlook, Yahoo & more)

Brevo statistics showing 100% delivered — Brevo statistics (live campaign): 100% delivered, 0% bounces.

Brevo real-time events showing opens — Brevo real-time events: opens and unsubscribe events confirm real inbox delivery.

View full proof

Results shown are real production samples. Deliverability depends on sender reputation, warm-up, content, and compliance.

Why MyCQL is different

✅ MyCQL verified data

Email verification before export
Undeliverable emails excluded automatically
Country-specific datasets
Consistent structure & fields
Quota-based fair usage
Designed for professional outreach

❌ Typical scraped lists

No verification or outdated checks
High bounce & spam risk
Mixed or unknown sources
Inconsistent formats
Pay for unusable emails
Often resold without quality control

Note: No email list can guarantee opens or replies. MyCQL focuses on deliverability, structure, and fair charging — not unrealistic promises.

What “verified emails” means

MyCQL does not sell generic or static email lists. “Verified” refers to technical deliverability checks performed close to export time (syntax, domain, mailbox-level signals), allowing users to filter and evaluate datasets before use.

Verification categories

Category	What it means	Export rule	Charged?
Deliverable	Mailbox likely accepts mail at SMTP level.	Included in export (when selected).	Yes (only if exported)
Undeliverable	Temporary Unreachable / Rejected / disabled / invalid format or domain.	Excluded automatically from export.	No
Unknown	Timeout / no-connect / catch-all. Can be temporary or provider-limited.	Handled conservatively; may be excluded depending on rules.	Only if exported

“Deliverable” does not guarantee opens, replies, or sales. Outcomes depend on your offer, copy, sending setup, and compliance.

Our commitment

Undeliverable emails are not charged (excluded automatically during export)
Verification runs before export (browsing stays fast, export stays strict)
Known invalid formats/domains are filtered
Cached verification improves speed and consistency
Only exported rows count toward your quota

Fair charging & credits

We charge by exported rows only. During export, undeliverable rows are excluded and do not count. If a mailbox changes later, bounces can still happen anywhere in email marketing — but we design the system to minimize it.

Reliability & rare downtime

In rare cases of temporary verification downtime, exports may use the latest cached verification available to avoid blocking customers. We don’t intentionally overcharge, and we refresh verification results when services recover.

Best practices (recommended)

Warm up domains and keep good sending reputation
Use proper unsubscribe handling and comply with local rules
Start small, monitor bounce/complaint rates, then scale