How to Check if a Gmail Address Exists (Without Emailing It)

Yes, you can check whether a Gmail address exists without sending it anything. Gmail's mail servers reject unknown accounts during the SMTP conversation with 550 5.1.1 The email account that you tried to reach does not exist, before any message is sent. A verifier asks at the RCPT TO step, reads that code, and disconnects. Normalise dots and plus signs first.

That makes Gmail one of the easier providers to verify, and the reason our own verifier failing on a made-up Gmail address was such a clear signal of a bug. The difficulty with Gmail is not the check itself. It is everything around it: duplicate addresses that look different, inactive accounts, and company domains that look like ordinary businesses but run on the same servers.

How Gmail answers a mailbox check

Gmail tells you the truth at the RCPT TO step, and its reply codes are documented. Google publishes its SMTP replies in the Gmail SMTP errors and codes reference. The ones a verifier meets when checking a mailbox:

Code	Google's message text	What it means for verification
250 2.1.5 OK	(accepted)	The account exists
550 5.1.1	"The email account that you tried to reach does not exist."	Invalid. Remove it
550 5.2.1	"The email account that you tried to reach is inactive."	Treat as invalid. Google reports the account as inactive
452 4.2.2	"The recipient's inbox is out of storage space."	Temporary. The account exists but cannot receive right now
552 5.2.2	"The recipient's inbox is out of storage space and inactive."	Treat as invalid. Full and abandoned
421 4.7.0	Several variants, e.g. connection, TLS or IP reputation problems	A problem with the checking server, not the mailbox. Retry

The distinction between the third and fourth rows matters. An out-of-storage account (452 4.2.2) belongs to a person who may clear space tomorrow. An out-of-storage and inactive account (552 5.2.2) belongs to nobody who is reading.

The conversation itself looks like this. Nothing is transmitted because DATA is never sent:

> MAIL FROM: <check@yourdomain.com>
< 250 2.1.0 OK
> RCPT TO: <definitely-not-real-xyz9987661@gmail.com>
< 550-5.1.1 The email account that you tried to reach does not exist.
> QUIT

You can only run this from a network that allows outbound port 25, which most home and cloud connections do not. We measured that in cloud providers block port 25.

Step 1: normalise the address before you check it

Gmail treats many different-looking strings as one inbox, so normalise before verifying or you will double-count and double-send. Three rules apply to gmail.com addresses.

Dots are ignored

Google's help page on dots says "Dots don't matter in Gmail addresses", giving the example that johnsmith@gmail.com receives mail sent to john.smith@gmail.com and j.o.h.n.s.m.i.t.h@gmail.com. All three are one person.

Anything after a plus sign is ignored

Google's filtering help shows that mail to janedoe+school@gmail.com and janedoe+notes@gmail.com "will all go to janedoe@gmail.com". Plus addressing is legitimate and used deliberately, so keep the original string for sending but use the base address for deduplication.

googlemail.com is the same service

googlemail.com publishes exactly the same five MX hosts as gmail.com (we checked both with dig on 1 October 2026). Treat jane@googlemail.com and jane@gmail.com as the same person when de-duplicating.

Raw address on your list	Normalised for de-duplication
J.Smith@Gmail.com	jsmith@gmail.com
j.smith+promo@gmail.com	jsmith@gmail.com
jsmith@googlemail.com	jsmith@gmail.com
j.smith@company.com (Workspace)	unchanged: dots matter here

That last row is the trap. The same Google help page says: "If you use Gmail through work, school, or other organization ... dots do change your address." Apply the dot rule only to consumer Gmail domains. For more on this as a fraud problem, see plus addressing, Gmail dots and free-trial abuse.

Step 2: pre-filter impossible usernames

New Gmail usernames follow published rules, so some addresses can be rejected before any network call. Google's username rules say usernames are "6–30 characters long", contain "letters (a-z), numbers (0-9), and periods (.)", and cannot contain an underscore, dash, apostrophe, ampersand, equals sign or plus sign (the plus sign is fine in the address you send to, as above, but cannot be part of the username itself).

So jo_smith@gmail.com and abc@gmail.com cannot be newly created Gmail accounts. Those are creation rules for new usernames, so treat a failure as a strong hint to check rather than an automatic delete, and let the SMTP check give the final answer.

Step 3: run the SMTP check

After normalising and pre-filtering, the RCPT TO reply decides. If you do not have port 25 access, a verification service does this for you. The free single email checker runs it on one address at a time.

Read the result against the table above. A 250 means the account exists today. It does not mean anyone reads it, which brings us to the part that verification alone cannot solve.

Why Gmail addresses still decay

Gmail accounts disappear over time through inactivity and through users changing address, and these two effects pull in opposite directions.

Inactive accounts get deleted

Google's inactive account policy defines an inactive account as one "that has not been used within a 2-year period", and states that "December 1, 2023 is the earliest a Google Account will be deleted due to this policy." The same page says the policy "doesn't apply to any Google Account that was set up for you through your work, school, or other organization."

In practical terms: a personal Gmail address collected years ago and never engaged with may now return 550 5.1.1, even though it was perfectly real when it signed up. That is the case for re-verifying old consumer lists before mailing them. See how often to re-verify your email list.

Changed addresses keep working

In 2026 Google began letting users change a gmail.com address (reported by TechCrunch in March for US users). Google's own help page on changing your account email says emails sent to "both your old or your new Google Account emails that end in @gmail.com will appear in your Gmail inbox", and that "no one else can use it. Even if you delete your Google Account, no one can use your old Google Account email."

Two consequences:

• An old Gmail address that verifies as valid may now be a secondary address for someone who has moved on. It is real, but it is no longer the address they think of as theirs.
• A dead Gmail address is not reassigned to a stranger, according to Google. That is a meaningful difference from providers that recycle addresses, where an old address can come back as someone else's inbox.

The Workspace exception

Many companies run on Google's servers, and some of them are configured as catch-all. You can spot Google-hosted domains by their MX records. On 1 October 2026, spotify.com, airbnb.com and shopify.com all published aspmx.l.google.com as their primary MX. Google's MX setup guide now tells new customers to use smtp.google.com and says domains set up before 2023 may still use values starting with "aspmx". Check any domain with the MX lookup tool.

Workspace admins can send misaddressed mail to a catch-all mailbox, described by Google as a way to "get and save incoming messages sent to non-existent or incorrect email addresses in your domain." When that is on, Google's servers accept every address at the domain, and the check that works so cleanly on gmail.com proves nothing. A competent verifier detects this by testing a random address first and returns risky. See what is a catch-all domain.

Methods that do not work, or should not be used

Method	Problem
Sending a test email	You find out by bouncing, which is the thing you were trying to avoid, and it reaches the person if the address is real
Typing the address into Google's sign-in or recovery page	Not built for this, rate-limited, and checking third parties' accounts this way is not something Google offers as a service
Searching the address on the web	Tells you it was published once, not that it works now
A regex or syntax check	asdkjhaslkdjh@gmail.com passes. See syntax vs MX vs SMTP

Practical takeaway

For any list with Gmail addresses on it:

1. Normalise gmail.com and googlemail.com addresses (strip dots and plus tags) to remove duplicates. Leave company domains alone.
2. Drop usernames that break Google's creation rules into a "check" pile rather than deleting them.
3. Run an SMTP check and act on Google's own codes: 550 5.1.1 and 550 5.2.1 go, 452 4.2.2 gets retried.
4. For company domains on Google's MX, expect some to be catch-all and handle those as risky.
5. Re-verify any consumer list older than a couple of years before mailing it.