Catch-All emails 🤨 This term sometimes sounds a bit barbaric to you and yet ...
A domain configured in Catch-All resides in the fact that email addresses from that domain are not verifiable .
No email verification solution can validate the existence of an email address on a domain in Catch-All.
An email verification test is different from a test of the actual sending of the email.
If you send emails to a domain in Catch-All, you will sometimes get non-existent email returns, this is called a bounce.
💡 A bounce is the return of an email that you have sent and which has not been temporarily or permanently delivered to its recipient. You then receive an error message informing you of this. Everything is explained in thearticle dedicated to bounces.
Beyond the "technical" settings detailed in this article, a mailbox can be configured to specify the way to receive the emails that are intended for it.
👇🏻 In the examples below, we will take the case of a person who wants to send an email email@example.com, but makes a mistake and send it to firstname.lastname@example.org - without the "s".
Illustration of a default configured domain
Generally, an email domain can only receive emails addressed to an existing address. 💡Dans in this case the verification solutions can validate an email address on average 90% of the time (98% for Dropcontact).
If you send an email to email@example.com when the address is firstname.lastname@example.org, your email will bounce, so it will never reach its recipient.
Domain configured in Catch-All
Conversely, a domain configured in Catch-All does not return any information during a validity check. It becomes impossible to check if the address actually exists or not.
Most of the time, large companies configure their domain in Catch-All.
If the @example.com domain is configured to capture all e-mail addresses of the example.com domain, then all e-mail sent to undefined addresses of this domain will be redirected to a "catch-all" address.
Illustration of a domain configured in Catch-All
Generally, a domain in Catch-All accepts all emails. 💡Le domain does not send any bounce messages if the email address does not exist. The email is sent, but without any certainty that it reaches the target person => undetectable in tests
There's something even more subtle...
Domain configured as Catch-All with bounce
Since Catch-Alls are not identifiable, email sales and enrichment companies market invalid or obsolete email addresses... 👀 without being aware that nobody will receive the email.
In the last 4-5 years, a new domain configuration has appeared: the Catch-All that bounce.
Illustration of a domain configured in Catch-All with bounce
💡 The particularity of the Catch-All is that these addresses are not verifiable during testing and will not return an error message. But in the configuration of a domain in Catch-All, when an email is actually sent if the email address of the recipient does not exist, there is a return of bounced email => undetectable during the sending test.
In any case, it is impossible today to verify the existence of an email address whose domain is configured in Catch-All.
There are therefore 3 domain configurations
- Domain configured as standard: testable and verifiable
- Bounce-free Catch-All configured domain: undetectable
- Domain configured as Catch-All with bounce: undetectable in upload tests
Adapt your strategy for Catch-All domains
Approximately 30% of B2B email servers are configured with Catch-All, so it's important to understand the impact Catch-All can have on your cold email strategy.
If you are on the sender's side, there are also advantages (for real!) and disadvantages.
👎🏻 The disadvantages of Catch-All
- Before actually sending the email, you can't know (and no one can now) whether the Catch-All email address will bounce or not.
- Even if the email has been sent, you can't be 100% sure that it was received by the right service, the right person.
Catch-All emails are therefore uncertain but without any real risk.
You can possibly expect less efficient results than personal emails, but don't focus too much on KPIs, analyse the final result 🤓
👍🏻 The benefits of Catch-All
- Who doesn't try anything has nothing: even if a domain is set up in Catch-All, sending an email to one of these addresses opens a door, a chance to reach a person interested in your message.
- If you are addressing someone who has left the company, your email will not be lost and will be properly delivered; and possibly opened by the new person in the position.
Catch-Alls are not the enemies of your Cold Email campaigns!
Even if they bounce, they won't affect your sender domain reputation as long as you do real Cold Emaile (less than 100/200 emails per day).
It'd be a shame to miss it. Everything is explained in the article and the webinar of the same name: "Cold Email, emails are bouncing... is it serious doctor 🚑?”
Detecting email addresses in Catch-All
To integrate Catch-All into your strategy and live well with it, it is important to check all your email addresses before sending cold email campaigns.
Here are a few tools that allow you to check the email addresses of your contacts:
To go further, see the comparison on the effectiveness of each of these solutions.
👉🏻 Our recommendation: Shoot the Catch-All!
Rather than removing entire companies from your prospecting target for a pseudo risk of bad domain reputation, open doors to clients who are often high-potential.
The bounce rate should not be a performance indicator: We advise you to analyze the final result of your campaign, namely the conversionrate.