Business mail platform · Google Workspace
Verifying addresses at Google Workspace domains
Can you verify addresses at domains behind Google Workspace?
Depends on the domainIt depends on the company. Domains behind Google Workspace are probed like any other.
Google Workspace answers for the company's own mail rules, so the checker treats every domain on its own: it offers a random address first, and if that is accepted the domain is catch-all and results come back risky ("Accepts all addresses"). Otherwise your address gets a per-mailbox answer. It always checks the syntax, the domain's MX records, disposable domains and role addresses such as info@ first.
Mailbox existsMailbox not foundAccepts all addressesCheck one address
Five checks a minute, no account needed. Nothing is sent to the address — we ask its mail server whether the mailbox exists, then disconnect.
Company domains with MX records at aspmx.l.google.com or smtp.google.com run on Google Workspace. Workspace normally rejects unknown users during the SMTP conversation, so a mailbox check gives a clear answer, unless the admin has set up catch-all routing, which makes every address look deliverable.
Live DNS snapshot: google.com
Checked 21 October 2026, 07:25 UTCaspmx.l.google.com is an MX host suffix, not a mail domain, so this is google.com: a domain whose mail runs through Google Workspace. Read from DNS at the time shown and refreshed at most once a day.
- 10
smtp.google.comGoogle Workspace
First MX host belongs to Google Workspace.
v=spf1 include:_spf.google.com ~allp=reject: meets the requirement and enforces it.
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.comLook up any other domain with the MX lookup or the email provider lookup.
Google Workspace at a glance
| Operated by | Google, through Google WorkspaceSource: Google: set up MX records for Workspace |
|---|---|
| MX hosts | smtp.google.com for new setups; the older aspmx.l.google.com and alt1–alt4.aspmx.l.google.com values are still supportedSource: Google: set up MX records for Workspace |
| Address rule | Admins can add a catch-all routing rule so mail to non-existent addresses lands in one mailboxSource: Google: catch-all mailbox |
| Address rule | Routing rules can target non-recognised addresses: ones on a verified domain that belong to no userSource: Google: default routing |
Why Google Workspace domains can be catch-all or per-mailbox
Company domains whose MX points to smtp.google.com or the older aspmx.l.google.com hosts run on Google Workspace. Without extra routing, a RCPT TO check usually tells real users apart from unknown ones.
Admins can add a catch-all routing rule that delivers mail for non-recognised addresses to one mailbox. On those domains every address looks deliverable, so the honest result is catch-all, not a confirmed person.
What our checker does behind Google Workspace
SimpleVerifier doesn't skip or special-case Google Workspace. For each company domain it offers a random address that can't exist, then your address, and disconnects without sending. If the random address is accepted, the domain is catch-all and its results come back risky with "Accepts all addresses". If it is rejected, your address gets a real answer for that mailbox.
Consumer Gmail is not part of this count. gmail.com uses gmail-smtp-in.l.google.com and answers per mailbox; see the Gmail page. Dots also behave differently: Google says dots matter on Workspace addresses, so don't apply Gmail's dot rule to company domains.
Cleaning a list full of Google Workspace domains
Split the list by domain, not by platform. Two companies on Google Workspace can behave in opposite ways, so a catch-all result at one says nothing about the next. The bulk catch-all checker finds which domains in a list accept everything before you spend time on single addresses.
For catch-all domains, keep addresses with recent replies or sign-ups and send the rest in a small first batch, suppressing anything that hard-bounces. For per-mailbox domains, trust the verdict: invalid addresses will bounce, and valid ones were accepted by the company's own directory. Accept-all vs unknown results covers the difference.
Common questions
- Can you verify addresses at domains behind Google Workspace?
- It depends on the company. Domains behind Google Workspace are probed like any other. Google Workspace answers for the company's own mail rules, so the checker treats every domain on its own: it offers a random address first, and if that is accepted the domain is catch-all and results come back risky ("Accepts all addresses"). Otherwise your address gets a per-mailbox answer. It always checks the syntax, the domain's MX records, disposable domains and role addresses such as info@ first.
- How do I know if a company uses Google Workspace?
- Look up the domain's MX records. A first MX host ending in aspmx.l.google.com means mail goes through Google Workspace. The email provider lookup and MX lookup tools show it for any domain.
- Are domains behind Google Workspace catch-all?
- Some are and some aren't; it depends on how each company configured Google Workspace. A verifier can tell by offering a random address that can't exist: if the domain accepts it, the domain is catch-all and single addresses there can't be confirmed.
- Is smtp.google.com the same as aspmx.l.google.com?
- Both are Google Workspace MX values. Google tells new customers to use smtp.google.com and still supports the older aspmx.l.google.com set, so domains on either are on Workspace.
Related tools
Got a list with Google Workspace addresses?
Upload the CSV and see how it splits into valid, risky and invalid before you pay. Then clean it with a one-time pack: $9 for 2,500 emails, credits that never expire.