TL;DR
- Consumer Gmail (gmail.com) is not a catch-all. A message to a Gmail address that does not exist is returned as undeliverable.
- The usual refusal is
550 5.1.1, "the email account that you tried to reach does not exist". We map that to undeliverable:rejected_email. - Google gives no public statement of how it treats high-volume address probing, so we pace our sessions to Google and treat a deferral as unknown, never as valid.
The direct answer
gmail.com is Google's own consumer domain. Individuals cannot turn on a catch-all for it: the catch-all setting Google documents is a routing rule that a Google Workspace administrator creates for a company domain (Google Workspace admin help, checked 2026-10-18). Because gmail.com has no administrator doing that, it is not a catch-all domain in the sense our catch-all glossary page describes. If you are asking about a company address that happens to use Gmail for mail, see Is Google Workspace a catch-all?
How Gmail answers a check for an address that doesn't exist
Google's own Gmail help lists "the recipient's email address doesn't exist" as a reason a message bounces (Gmail help: fix bounced or rejected messages, checked 2026-10-18). The bounce text most senders see is 550 5.1.1 The email account that you tried to reach does not exist. That wording comes up widely in forum reports and sender guides; the Google page we could read does not print it, so treat the exact string as common rather than guaranteed.
RCPT TO:<[email protected]> → 250 OK
RCPT TO:<[email protected]> → 550 5.1.1 ... account ... does not existIf the real address is accepted and the random one is refused, the "yes" means something. That is the pattern we expect from Gmail, and it is why Gmail addresses are among the easier ones to verify.
What we can and can't say
- Documented: Gmail returns a "does not exist" bounce for missing recipients, and a catch-all is a Workspace admin feature.
- Not documented: whether Google refuses the address during the SMTP conversation in every case, how many checks it tolerates from one IP, and whether it ever answers differently to a probe than to real mail. We found no Google source for these, so we don't claim an answer.
- Our own data: our 2026-10-17 test used only five addresses, and those were Google-hosted addresses in general, not gmail.com alone. It is too small to quote a rate, so we don't.
What you will typically see
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 |
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 |
In practice, expect gmail.com results to land in deliverable or undeliverable, with only a small unknown share when Google defers or limits us. Unknowns are refunded and credits never expire (pricing).
Sources
- Gmail help, bounced messages: checked 2026-10-18
- Google Workspace admin help, catch-all mailbox: checked 2026-10-18
Common questions
Is Gmail a catch-all?
No. Consumer gmail.com is not a catch-all domain. Mail to a Gmail address that does not exist is returned as undeliverable.
What does 550 5.1.1 mean on Gmail?
It is the permanent bounce for a recipient that doesn't exist. We count it as undeliverable (rejected_email).
Can you verify a Gmail address without emailing it?
Yes. We ask Gmail's mail server whether it would accept the address and never send a message. How that works.