Catch-all, or accept-all, domains
A catch-all domain accepts every address presented to it, whether it exists or not: the server answers favourably in every case. YesWeCheck detects these domains during the same verification, flags this explicitly, returns an unknown status rather than a guessed verdict, and charges nothing for that address.
What a catch-all domain is
A catch-all domain, also called accept-all, accepts every address presented to it, including those that match no mailbox. The server answers favourably in both cases, which makes the existence of a mailbox undecidable from the outside. The configuration is deliberate and perfectly legitimate: it avoids losing a message sent to a misspelled mailbox.
The configuration is deliberate and perfectly legitimate. An organisation may want to receive everything that arrives on its domain rather than lose a message addressed to a misspelled mailbox. Sorting happens afterwards, on the inside, under rules the outside world never sees.
Accept-all means exactly the same thing. Both words circulate: the second insists on what the server does, the first on what it does next.
How the detection works
To find out whether a domain accepts everything, the probe presents a second address, drawn at random, on the same session as the requested address. If the server also accepts that address, which does not exist, the domain accepts everything. The randomly drawn local part carries no recognisable marker.
| Element | Value | What it changes |
|---|---|---|
| Control address | Drawn at random, with no recognisable marker | The server cannot tell it apart from an ordinary address: the measurement stays reliable. |
| Session used | The same as the requested address | No extra dialogue is opened with the receiving server. |
What we observe
The domains already analysed by YesWeCheck show it: on organisation domains, the case is common. That is precisely where detection makes the difference, by sparing you from counting as valid addresses that nobody can confirm.
As of 7 September 2026, we have analysed more than 7,800 domains, of which more than 1,600 answer to every address. In other words, on the organisation domains our customers submit, the case is far from marginal.
A clear signal rather than a guess
On a domain that accepts everything, YesWeCheck never sells you a guess. The address is returned as unknown, the accept-all reason is written in plain text in the response, and no credit is charged: you keep the decision, and you only pay for real answers.
This is a point on which verification tools set themselves apart. Returning such an address as valid would be more flattering, but it would be a guess. YesWeCheck returns unknown, names the accept-all reason, and lets you decide with accurate information.
Which decision to take
The right course of action depends on the use, not on the domain. A catch-all address met at sign-up is handled differently from a catch-all address found in a purchased prospecting file. In the first case, refusing costs a customer. In the second, sending costs sender reputation.
| Situation | Course of action |
|---|---|
| Signing up to a service, in real time | Accept. Refusing an address because its domain accepts everything would mean discarding entire companies whose mail is correctly configured. |
| Acquisition campaign on a cold list | Discard, or handle separately. These addresses inflate the bounce rate unpredictably, and they are not charged, so removing them costs nothing. |
| Cleaning a base of existing customers | Keep. An address already used on an accept-all domain is probably still valid: sending history says more than the probe. |
| Named prospecting on an identified account | Cross check with another source. The domain will not decide, verification has to come from elsewhere, for instance from a human confirmation. |
What it costs
An address whose domain answers to everything uses no credit. The billing rule is the same everywhere: a credit is charged only if the verification reached a conclusion. An accept-all domain does not allow a conclusion, so nothing is charged, even though the probe did talk to the server.
A credit is charged if and only if SMTP verification was requested and the final status is not "unknown".
This rule has a practical effect: cleaning a list full of accept-all domains does not drain the credit balance. The report isolates these addresses, and they cost nothing.
Frequently asked questions
- What is a catch-all domain?
- A catch-all domain, also called accept-all, accepts every address presented to it, including those that match no mailbox. The server answers favourably in both cases, which makes the existence of a mailbox undecidable from the outside. The configuration is deliberate and perfectly legitimate: it avoids losing a message sent to a misspelled mailbox.
- How does YesWeCheck handle an address on a catch-all domain?
- On a domain that accepts everything, YesWeCheck never sells you a guess. The address is returned as unknown, the accept-all reason is written in plain text in the response, and no credit is charged: you keep the decision, and you only pay for real answers.
- Is a catch-all address charged?
- No. The status returned is unknown, and an unknown status is never charged. The information that the domain answers to everything therefore comes to you free of charge.
- Why does YesWeCheck not return these addresses as valid?
- Because a valid verdict on a domain that accepts everything would be a guess. YesWeCheck flags the accept-all domain for you: you keep control of the decision, and you avoid the bounces that a guessed verdict would not have announced.
Go further
Batch processing makes a second pass over the addresses left unknown to catch up with temporary deferrals, and its report isolates accept-all domains so that you can handle them separately, according to your use.
Content updated on 7 September 2026.