Question 1

What is a catch-all email verifier?

Accepted Answer

A catch-all email verifier judges addresses on catch-all (accept-all) domains — servers configured to accept mail for every recipient, so a standard SMTP probe never says no. Enrow's catch-all email verifier resolves these cases and returns a definitive valid or invalid qualification instead of leaving them unresolved.

Question 2

Can you actually verify an email on a catch-all domain?

Accepted Answer

Yes. A catch-all server accepts every recipient at the SMTP layer, so probing alone can't tell a real mailbox from one that will bounce. Enrow verifies the address through deterministic checks that go beyond the SMTP handshake and returns a clear valid or invalid verdict — never a 'risky' or 'accept-all' guess.

Question 3

Why do other tools mark catch-all addresses 'risky' or 'unknown'?

Accepted Answer

Most verifiers rely on the SMTP handshake alone. Because a catch-all domain answers yes to everything, they have no signal to act on and fall back to labels like 'risky', 'unknown' or 'accept-all'. Enrow is built to reach a definitive answer precisely where that handshake stays silent.

Question 4

Do I still need a debouncer after verification?

Accepted Answer

No. The result is a binary valid or invalid, so there is nothing ambiguous left to re-check. You can route the verified address straight into your sending flow without a second verification pass.

Question 5

How do I call the catch-all email verifier API?

Accepted Answer

POST the address to /email/verify/single, or send up to 5,000 at once to /email/verify/bulk. Authenticate with your x-api-key header. The endpoint returns an id immediately and the verdict arrives by webhook or the matching GET. Full reference at docs.enrow.io.

Question 6

How much does the catch-all email verifier cost?

Accepted Answer

0.25 credit per address checked, catch-all domains included — the price is the same whatever the domain type. Credits are shared across all Enrow APIs and start at $17, and you get 50 free credits to begin.

Question 7

Is the catch-all email verifier real-time or asynchronous?

Accepted Answer

It's asynchronous. Your POST returns an id right away, then Enrow delivers the valid or invalid result to the webhook you set in settings.webhook, or you fetch it later with the matching GET. Single and bulk requests work the same way.

Question 8

Is the catch-all email verifier GDPR compliant?

Accepted Answer

Yes. Enrow is GDPR and CCPA compliant, and a DPA is available on request. Verification runs only against the address you submit.

1	# 1. Launch a search
2
3	curl -X POST https://api.enrow.io/email/verify/single \
4	-H "x-api-key: YOUR_API_KEY" \
5	-H "Content-Type: application/json" \
6	-d '{
7	"email": "john.doe@acme.com",
8	"settings": {
9	"webhook": "https://yourapp.com/webhook"
10	}
11	}'

1	# 2. Webhook fires when ready:
2
3	{
4	"email": "john.doe@acme.com",
5	"qualification": "valid",
6	"credits_used": 0.25
7	}
8
9	# Or poll the result:
10
11	GET https://api.enrow.io/email/verify/single?id={search_id}

1	curl -X POST
2	https://api.enrow.io/email/find/single -H "Content-Type: application/json" -H "x-api-key: YOUR_API_KEY" -d '{
3	"fullname": "John Doe",
4	"company_domain": "example.com"
5	}'

The catch-all email verifier that returns a definitive verdict

One API. One endpoint. Single and Bulk.

catch-all email verifier

Async-first. Webhook-ready.

Async by default

Metadata passthrough

Webhooks

Deterministic verification

Track everything. Via API or in the dashboard.

Account endpoint

In-app dashboard

SDKs, native integrations, or raw HTTP

SDKs

Native integrations

HTTP from anywhere

Catch-all email verifier — everything you need to know

First request in under 10 minutes