Apify's Official Catch-All Email Verification Actor

Overview

Achieve definitive email verification for catch-all domains at scale. This actor provides a last-resort solution to confirm inbox existence for Google and Microsoft 365 accounts, bypassing traditional SMTP limitations and IP blocks. Ideal for enterprise lead generation and data enrichment where accuracy is non-negotiable.

Why Verify Catch-All Domains?

1. Enterprise Access Target Fortune 500/1000 companies that rely on Microsoft 365 and other catch-all environments. Reach decision-makers other tools miss.
2. Eliminate False Positives Go beyond basic SMTP checks. Our multi-signal analysis provides a single source of truth for inbox existence with high-confidence scoring.
3. Maximize Campaign ROI Clean your lists with 100% confidence. Protect your sender reputation and boost outreach open rates by verifying the hardest-to-reach emails.
4. Pay per successful result only Only pay for verified emails. No more wasted budget on false positives.

Automate Your Workflow

• Webhook Integration Push verified datasets to your CRM, marketing automation platform, or custom API via POST. Trigger enrichment pipelines or outreach sequences instantly.
• Scheduled Cleansing Use Apify's cron scheduler to automatically verify and update lead lists weekly or monthly.
• Dataset Filtering The actor automatically filters results to successful verifications only, delivering a clean, ready-to-use dataset.

Suggested Use

• Post-SMTP verification Use this to verify those emails that SMTP verification failed on. This is a last resort for catch-all domains and not intented to verify thousands of addresses at once (do it in batches). It can be lengthy and take time.
• Retry freely By default, failed results aren't included. It's likely if you retry eventually you'll get either a found or not found (with confidence) result as opposed to a failed one. Found and not found addresses are considered successes.

---

Input Example

{
    "emails": [
        "david.ulrich@davidulrichassociates.com",
        "scott@plan2placement.com",
        "jeremy@talenthubb.net"
    ]
}

Output Structure

[
    {
        "email": "rhagan@jarpec.com",
        "found": true,
        "success": true,
        "score": 100,
        "message": "High confidence: Account found on multiple sources",
        "response_time": 25.9,
        "verified_at": "2025-09-12T15:53:29.491633"
    },
    {
        "email": "rwoods@ihie.org",
        "found": true,
        "success": true,
        "score": 80,
        "message": "High confidence: Account is found",
        "response_time": 45.19,
        "verified_at": "2025-09-12T15:53:29.491585"
    },
    {
        "email": "george.gobin@gtginnovision.com",
        "found": false,
        "success": true,
        "score": 100,
        "message": "High confidence: Sources confirm email does not exist",
        "response_time": 47.8,
        "verified_at": "2025-09-12T15:53:29.491506"
    }
]

---

Supported Providers & Confidence Scoring

Provider	Support	Ideal For
Microsoft 365	Full Support	Enterprise targeting, Fortune 500/1000 companies
Google (All Types)	Full Support	Gmail, Google Workspace, and all business variants
Mimecast	Coming soon...	-

Confidence Score	Meaning
100	Highest confidence: Multiple signals confirm existence or non-existence.
80	High confidence: Account status is confirmed.
< 80	Uncertain: Will be reattempted for higher confidence. (Failed results aren't returned to dataset)

---

FAQ

Q: When should I use this actor? A: Use it as a last resort when traditional SMTP verification fails or returns false positives for catch-all domains.

Q: How long does verification take? A: Individual checks are fast, but large batches are processed as a job. Allow up to 20 minutes for completion as the system polls for definitive results.

Q: What's the cost? A: This method is more expensive than basic SMTP checks due to its advanced, multi-signal approach and higher accuracy, but is cost-effective for high-value enterprise leads.

Q: Can I verify thousands of emails? A: Yes. The actor is designed for scale, but batching and separating requests between 100-200 emails at a time is recommended.

---

Integration Code

curl "https://api.apify.com/v2/acts/codemaggot/catchall-verification/run-sync" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -d '{"emails":["email1@domain.com", "email2@domain.com"]}'

View Actor | Webhook Docs

---

Stop guessing. Start knowing. Verify with certainty.