Catch-All Verifier · Enrichment
When “catch-all” isn’t a useful answer.
Run a deeper check on catch-all addresses and see which ones you can act on.
- IN
- Catch-all emails (CSV)
- OUT
- Verified CSV
| After deeper check | |
|---|---|
| d.okafor@northwind.example | Valid |
| j.keller@talwerk.example | Invalid |
| m.vogt@nordstern.example | Valid |
| a.richter@weidenhof.example | Still uncertain |
Swipe for more columns
- Valid
d.okafor@northwind.example
- Invalid
j.keller@talwerk.example
- Valid
m.vogt@nordstern.example
- Still uncertain
a.richter@weidenhof.example
Send the catch-all rows, or the whole list.
You bring
| status | |
|---|---|
| d.okafor@northwind.example | catch-all |
| j.keller@talwerk.example | catch-all |
- Accepted: A file of catch-all addresses
You get back
Verified CSV
- Status
- + your columns
What is a catch-all email address?
A catch-all domain accepts mail for any address, even ones that don’t exist. Standard verification asks the server whether a mailbox exists. A catch-all server says yes to everything, so the answer tells you nothing. Those addresses are labelled catch-all or risky, which leaves you guessing whether to send.
Why catch-all creates uncertainty.
You check an address
A standard check asks the mail server if the mailbox exists.
The server accepts everything
A catch-all domain answers yes for any address.
A standard check can’t tell
Real and made-up addresses look the same.
See what a deeper check changes.
Standard check
| Status | |
|---|---|
| d.okafor@northwind.example | Catch-all |
| j.keller@talwerk.example | Catch-all |
| m.vogt@nordstern.example | Catch-all |
| a.richter@weidenhof.example | Unknown |
| l.brandt@hafenlicht.example | Catch-all |
| f.hartmann@brueckner.example | Catch-all |
Swipe for more columns
- Catch-all
d.okafor@northwind.example
- Catch-all
j.keller@talwerk.example
- Catch-all
m.vogt@nordstern.example
- Unknown
a.richter@weidenhof.example
- Catch-all
l.brandt@hafenlicht.example
- Catch-all
f.hartmann@brueckner.example
After Catch-All Verifier
| Status | |
|---|---|
| d.okafor@northwind.example | Valid |
| j.keller@talwerk.example | Invalid |
| m.vogt@nordstern.example | Valid |
| a.richter@weidenhof.example | Still uncertain |
| l.brandt@hafenlicht.example | Invalid |
| f.hartmann@brueckner.example | Valid |
Swipe for more columns
- Valid
d.okafor@northwind.example
- Invalid
j.keller@talwerk.example
- Valid
m.vogt@nordstern.example
- Still uncertain
a.richter@weidenhof.example
- Invalid
l.brandt@hafenlicht.example
- Valid
f.hartmann@brueckner.example
Illustrative rows · fictional data · column names confirmed by engineering
A decision, not a promise.
- Resolved valid
Send
- Resolved invalid
Remove
- Still uncertain
Send slowly or skip
What this tool cannot guarantee.
What to expect
- DATASome addresses stay uncertain after the deeper check.
- DATASend to resolved addresses gradually and watch your bounces.
Questions before your first run?
A domain whose mail server accepts mail for any address, so a standard check can’t confirm that a specific mailbox exists.
Some servers give no usable signal even to a deeper check. Those addresses are marked Still uncertain rather than guessed.
Only delivered rows use credits. A row that isn’t delivered in your file doesn’t count.
Run next on this file.
Start with the first pass: Email Verify
Decide on catch-all addresses with more than a guess.
Already have an account? Log in
Prefer us to do it? Tell us about your project