What a catch-all domain is, why the mail server's answer cannot confirm a mailbox behind one, what PricklyMails returns instead, and what to do with those addresses.
You verify a business address, and the result is neither valid nor invalid: it says "catch-all domain".
That is not the tool failing: the domain's mail server gives the same answer for every address.
Understanding why helps you decide what to do with those addresses.
A catch-all domain, also called an accept-all domain, is set up to accept email sent to any address, including addresses that do not exist.
On such a domain, jane.doe@example.com and anything.at.all@example.com are accepted in exactly the same way.
Companies do this for good reasons:
Never lose a message. A misspelled name, a former employee's address, an address a customer guessed: everything lands somewhere.
Route everything to one place. Mail sent to mailboxes that do not exist goes to a shared inbox, read by the front desk or by nobody.
Hide who works there. A domain that accepts everything does not reveal which addresses are real, which frustrates anyone trying to guess them.
It is common on company domains, and sometimes it is simply the mail host's default setting.
On a catch-all domain, the mail server accepts every address, real or made up.
Its answer therefore tells you nothing about the mailbox you care about.
Sending a real email does not always settle it either.
Depending on the setup, the message may be accepted and then routed to a shared inbox, silently dropped, or bounced later.
A message that does not bounce has not necessarily been read.
Some tools try to settle part of these addresses through other methods.
We chose not to: PricklyMails reports only what the mail server's answer supports, and tells you when that answer cannot tell a real mailbox from the rest.
Google, Microsoft, and Yahoo raise a related but different problem.
Their servers do not reliably answer whether a mailbox exists, to protect their users from people guessing addresses.
The difference is the domain.
A Gmail or Outlook address lives at a real mail provider with an active domain; only the individual mailbox cannot be confirmed.
PricklyMails returns it as valid, with a capped score, the reason "accept-all provider", and a "send" recommendation.
A catch-all company domain also accepts addresses that do not exist, and that is what you need to know before you send.
Two details, so you know exactly what you are looking at:
If the server gives no clear answer, we do not conclude. The domain is not flagged as catch-all, but its score stays lower than a confirmed mailbox's.
Catch-all detection is a separate check, available from the Pro plan up, costing 4 tokens on top of the mailbox test. Without it (Free and Starter plans), an address on a catch-all domain comes back valid with a "send" recommendation, because the verification does not say whether the domain accepts everything: no extra probe is sent, and the score does not hint at it either.
And if the server does not answer at all, the verdict is "not verifiable", and the tests that got no answer, this one included, are refunded.
Removing them all would be a mistake: plenty of addresses behind catch-all domains are perfectly real, starting with your customers'.
Sending to all of them without a second thought is the opposite mistake.
Put them in their own segment. Mixed into the rest of the list, they blur how you read your results.
Keep the ones you know. A customer, a recent signup, a contact who has replied before: the history of the relationship beats any verification.
Send to a small group first. Watch bounces and replies before rolling out to the rest of the segment.
Remove the ones that bounce, like any other address.
Be careful with cold outreach. A guessed address (first.last@company.com) on a catch-all domain may never bounce, and still never be read.
For a signup on your own site, let the address through and confirm it by email: a click on the confirmation link proves the mailbox exists, which the server's answer cannot do on this kind of domain.
No.
It is a configuration choice, common among companies, and it says nothing about the person behind the address.
It only says that the server's answer cannot settle whether that specific mailbox exists.
Because "valid" has to mean something.
From the Pro plan up, catch-all detection is included: an address on a domain identified as catch-all comes back "review", never valid, since the server confirmed nothing.
On the Free and Starter plans, that detection is not included, so such an address can come back valid, like any other accepted mailbox on those plans.
If some of your valid addresses actually reach nobody, you can no longer trust your sorting, or your campaign stats.
Curious how much of your list sits behind catch-all domains? Detection is part of the Pro plan; to try the other checks first, create an account: free tokens on signup, no credit card required.
A practical method for cleaning an email list before a send: gather it, drop what you already know, verify every address, sort by recommendation, decide on the doubtful ones, and send in stages.
PricklyMails and ZeroBounce compared on verifiable points: pricing model, price per 1,000 addresses, free tier, credit expiry, unknown results, catch-all handling, data retention and hosting, API, and MCP.
Most email tools stop billing an address once it bounces. The real cost is elsewhere: a suspended account, a tier paid until renewal, and your sender reputation.
Check your list before your next send.
1,000 tokens free when you sign up, no credit card. After that, you only pay for answers.