Catch-all Email Detection

What are catch-all email addresses?

A catch-all server (also known as an "accept-all" server) is configured to accept any email sent to its domain, regardless of whether a specific mailbox exists. For example, if a domain has a catch-all setup, emails sent to [email protected] will be accepted, even if "anything" isn't a real user.

This creates a challenge for traditional email validation because the server always responds with a "success" (250 OK) status during the SMTP handshake.

How EasyEmailAPI detects catch-all servers

When SMTP checks are enabled and a usable MX host is available, the validation engine checks mail-server responses:

• SMTP connection: Connect to the domain's mail server and begin an SMTP handshake.
• Probe address: Test recipient acceptance for a randomly generated address without sending a message.
• Response analysis: If that recipient is accepted, flag the server as catch-all. Server-level results may be cached.
• Mailbox check: If the server is not detected as catch-all, test the requested recipient. For a catch-all result, individual inbox existence remains unconfirmed.

Why catch-all detection matters

A server accepting a recipient is not the same as confirming an inbox. Catch-all detection helps you keep that distinction in your workflow:

• Separate uncertain results: Review catch-all contacts instead of labeling every accepted recipient as a verified mailbox.
• Interpret scoring: Catch-all results contribute to the validation score, but the score is not a delivery probability.
• Apply your policy: Decide whether to require confirmation, review a contact, or exclude it from a particular campaign.

Business use cases

Catch-all detection is essential for:

• High-volume Outreach: Sales teams can avoid wasting effort on risky domains.
• Newsletter Hygiene: Maintain a clean subscriber list with high engagement.
• Database Enrichment: Flag contacts that might need additional verification.

How to handle catch-all addresses in signup forms

Do not automatically reject a signup just because catch_all is true. A real customer may use an accept-all domain. Ask them to confirm their address by email before enabling features that require a reachable inbox.

First inspect inbox_check_enabled. When SMTP checks are disabled, catch_all: false is not proof that the server rejects unknown recipients. Even with checks enabled, a timeout or skipped server can leave inbox existence unconfirmed.

See the developer integration guide for response fields and failure handling.

Should you keep catch-all emails in a marketing list?

Keep catch-all results in a separate review segment. Consider consent, past engagement, and confirmed ownership before sending; catch-all detection alone cannot tell you whether an individual recipient is reachable.

Combine this signal with MX record verification and your email-list cleanup policy. SMTP inbox and catch-all checks require Pro; the free plan covers other validation signals.