TL;DR
- Proton's own domains are not catch-all. Only custom domains on paid plans can have a catch-all.
- Without one, Proton says the sender gets "a bounce-back message" saying the address "does not exist". Existing addresses always win over the catch-all.
- Proton does not say whether that bounce is an SMTP refusal or a later message, so we don't claim a code.
The direct answer
Proton's support page says a catch-all lets a custom domain "receive all mail sent to their domain" even when the address was never created, and that it requires a paid plan. Existing addresses take priority: mail to them "won't be delivered to the catch-all address". Without a catch-all, Proton says mail to an unrecognised address is rejected and the sender receives a bounce-back that the address does not exist (Proton support: catch-all, checked 2026-10-18).
The setup path is in the organisation's domain settings, where an admin chooses "Set catch-all" and enters an address on the domain. Since that needs a custom domain, @proton.me and @protonmail.com addresses are not covered by it.
What this means for verification
The method is the same everywhere: we open an SMTP session with the domain's mail server, ask whether it will take mail for the address, ask the same about a random address that cannot exist, and never send the message (how it works).
| What the server says | Our result |
|---|---|
| Accepts the address, refuses the random test address | deliverable (risky: low_quality for role addresses such as info@) |
Refuses the address (550 5.1.1 or similar) | undeliverable: rejected_email |
| Accepts the address and the random test address | risky: low_deliverability (catch-all) |
Temporary 4xx answer (deferral, rate limit, greylisting) | unknown: unavailable_smtp after a later retry |
Refuses us for who we are (5.7.x, blocklist or policy text) | unknown: blocked_by_server |
Proton-hosted custom domains are found by their MX records, and then the usual random-address test tells us whether a catch-all is on.
Privacy and probing
Proton is a privacy-focused provider, and people expect it to resist address probing. We found no Proton page saying it does, so we don't claim it. If Proton defers or refuses our sessions, you get unknown (refunded) and not a guess.
What we couldn't confirm
- Whether "rejected" in Proton's wording means a
550during the SMTP session. It is the natural reading but the page doesn't print a code. - How Proton treats repeated checks from one IP.
For the general method see how to verify without sending, and for how a verifier reports each case see verification statuses.
Sources
- Proton support, catch-all address: checked 2026-10-18
Common questions
Is Proton Mail a catch-all?
proton.me and protonmail.com are not. A custom domain on a paid plan can be, if the admin sets a catch-all address.
What happens to mail for a missing Proton address?
Proton says the sender gets a bounce-back saying the address does not exist, unless a catch-all is set.
Can I verify Proton addresses?
Yes. If Proton refuses or defers the check you get unknown, which is refunded.