Verification results
Catch-all email
A catch-all email domain accepts mail sent to any address on it, even names that do not exist. Because the server says yes to everything, a normal email check cannot tell whether a specific mailbox is real.
What is a catch-all email?
A catch-all email domain accepts mail sent to any address on it. The address does not need to exist.
Most domains reject email sent to a name they do not have. A catch-all domain does not. It accepts the email and puts it into one shared mailbox, or sometimes deletes it without telling anyone.
Other names for the same setting are accept-all and catch-all domain. Many verification tools label these addresses "catch-all", "accept-all" or "risky".
A simple example
- Acme sets up a catch-all. Acme is a small company with the domain acme.example. Its office manager turns on catch-all so no customer email gets lost.
- Sara writes to a real person. She emails jon@acme.example. Jon works there. He gets the email.
- Sara makes a typo. Next time she types jonn@acme.example. There is no such person.
- The server still says yes. The email does not bounce. It lands in the shared mailbox, and nobody may read it.
Sara sees no error, so she thinks both emails arrived. Only one reached Jon.
Why companies use catch-all
Companies turn on catch-all so they do not miss email. Customers make typos. Old staff names keep receiving mail. A catch-all keeps all of it in one place.
Why catch-all is a problem for email verification
A normal email check asks the server one question: "Do you accept mail for this address?" On a catch-all domain, the answer is always yes. A real person and a made-up name get the same answer.
So a basic check cannot confirm the mailbox. It can only report that the domain accepts everything.
This matters most for B2B lists. In one published test of 10,000 real business emails, 28% were on catch-all domains. The test was run by LeadMagic, a company that sells email verification, so treat it as a vendor test.
What to do with catch-all addresses
You have three choices:
| Choice | What happens |
|---|---|
| Remove them | No risk, but you lose real contacts too |
| Send to them | Some will reach real people, some will be lost or bounce later |
| Check them deeper | A verifier that tests beyond the basic check sorts the real from the fake |
How a verifier helps
Giggal.ai runs catch-all verification as part of every check. It uses extra signals to return a real result, deliverable or undeliverable, instead of a "risky" label. For a longer guide with more examples, read what a catch-all email address is.
Related terms
- MX recordAn MX record is a setting on a domain that says which server receives email for that domain. When you send to name@example.com, your mail server looks up the MX record for example.com to find where to deliver the email.
- SMTPSMTP stands for Simple Mail Transfer Protocol. It is the set of rules that email servers use to send email to each other. Every email you send travels from server to server using SMTP.
- Hard bounceA hard bounce is an email that the receiving server refused for good. The address does not exist, the domain does not exist, or the server blocked your email. If you send the same email again, it will fail again.
- GreylistingGreylisting is a spam defence. A mail server rejects the first email from a sender it does not know, then accepts the same email when the sender tries again a few minutes later. Real mail servers retry, but most spam software does not.
- Secure email gateway (SEG)A secure email gateway, or SEG, is a filter that sits in front of a company's mailboxes. It checks every incoming email for spam, phishing and harmful files before anyone receives it. Common examples are Mimecast, Proofpoint and Barracuda.
- Email blacklistAn email blacklist is a public list of IP addresses or domains known to send spam. Receiving mail servers check these lists and block or filter email from senders on them. Spamhaus runs some of the best-known lists.