TL;DR
- Google Workspace is not a catch-all by default. The domain owner must create a catch-all routing rule.
- Domains differ: some Workspace domains refuse unknown mailboxes, some accept everything. You have to test each domain.
- We mark a Workspace address deliverable if it is accepted and a random address is refused, risky:
low_deliverabilityif both are accepted.
The direct answer
Workspace is a service, not a single mail policy. Each customer domain behaves according to its admin settings. Google's help page for the feature describes a routing rule that uses Modify message → Change envelope recipient → Replace recipient, applied to "All inactive and unrecognized accounts", so that mail for non-existent addresses goes to one chosen mailbox instead of bouncing (Google Workspace admin help, checked 2026-10-18). The page also says changes can take up to 24 hours.
So a Workspace domain is a catch-all if and only if somebody configured that rule (or an equivalent). Google's page does not say what happens to unknown addresses when no rule exists. In practice senders see the standard "does not exist" bounce, but that is the behaviour we could not confirm from Google's text.
How a Workspace domain answers a check
It depends on the domain:
| What the server says | Our result |
|---|---|
| No catch-all rule, mailbox exists | deliverable |
No catch-all rule, mailbox missing (refused, typically 550 5.1.1) | undeliverable: rejected_email |
| Catch-all rule in place | risky: low_deliverability |
Our 2026-10-17 test sent five addresses to Google's mail servers. The results matched Emailable's on four of four, and between them they included deliverable, rejected and catch-all outcomes. Five addresses is far too few to say how common each is, but it shows why a domain-by-domain test matters.
Why you can't assume
Google also documents a known problem where a catch-all address was assigned to every domain on an account with no mailbox behind it, so mail to those addresses bounces (Google Workspace admin help, checked 2026-10-18). That means a catch-all can be half-configured: the domain may look catch-all at one level and still bounce later. Only a bounce or a reply settles it.
The MX records for Workspace domains point to Google's mail servers, which is how we know a domain is on Google. The catch-all setting is not visible in DNS.
What to do with the results
- Send deliverable Workspace addresses normally.
- Treat catch-all Workspace domains as a separate, lower-volume segment (guide).
- Re-verify unknowns later. Google may defer or limit sessions, and we pace our sessions to Google for that reason.
Sources
- Get misaddressed email in a catch-all mailbox: checked 2026-10-18
- Google Workspace admin help on the catch-all migration issue: checked 2026-10-18
Common questions
Is Google Workspace a catch-all?
Not by default. It becomes a catch-all only if the domain's administrator adds a routing rule for unrecognized addresses.
How do I know if a Workspace domain is catch-all?
Test it: ask the mail server about a random address that can't exist. If it is accepted along with the real one, the domain is catch-all.
Is Gmail the same as Google Workspace?
No. gmail.com is Google's consumer domain. Workspace is Google's mail service for company domains. See Is Gmail a catch-all?