Check If a Gmail Address Is Available

There are two different questions hiding under "check if a Gmail address is available":

1. Can I register this address as a new Gmail account? — answered at the Google signup form
2. Does this Gmail address already exist (is it deliverable)? — answered by an SMTP RCPT TO probe

For consumers picking a personal address, question 1 matters. For senders cleaning lists, investigating impersonation, or confirming customer signups, question 2 is the relevant one. This guide covers both, but the sender angle is where the practical depth lives.

Question 1: Can I register this address?

The only authoritative source is Google. Go to accounts.google.com/signup, enter the desired username, and Google tells you in real time. Three possible outcomes:

• Available — green check, you can complete signup
• Taken — red error, suggested alternatives offered
• Reserved — error without suggestions, typically because the local-part conflicts with a Google-reserved name (admin, support, noreply, etc.)

No third-party tool does this better. The wrappers that exist either proxy Google's signup endpoint or just guess.

Question 2: Does this address exist (is it deliverable)?

This is the sender-side question and the answer involves SMTP.

When a mail server receives an attempt to send to [email protected], it issues RCPT TO:<[email protected]>. Gmail's MX responds:

• 250 2.1.5 OK — the mailbox accepts mail (exists)
• 550 5.1.1 The email account that you tried to reach does not exist — does not exist
• 421 4.7.0 Temporary failure — rate limited or greylisted, retry later

Verification tools automate this. You feed them the address, they run the probe through their IP pools, they return the result. No mail is delivered.

$ telnet gmail-smtp-in.l.google.com 25
EHLO yourdomain.com
MAIL FROM:<[email protected]>
RCPT TO:<[email protected]>
550-5.1.1 The email account that you tried to reach does not exist.

Practitioner note: Gmail rate-limits SMTP verification probes aggressively. Running 10,000 RCPT TO probes from a single IP will get that IP throttled or blocked within hours. This is why commercial verifiers rotate across large IP pools and pace requests. If you try to roll your own Gmail verifier from a single VPS, you'll burn the IP fast.

Sender use cases for Gmail address checking

Cleaning a list before sending

If your list has stale Gmail addresses (signups from years ago, imported leads, lapsed customers), some will have been closed or deleted. Sending to a deleted Gmail address returns a 550 hard bounce, which counts against your sender reputation.

Standard practice: run the list through a verifier before a major send. Drop the 550s. Keep the 250s. See our list cleaning guide for the full workflow.

Confirming a single signup or lead

When a customer submits a Gmail address through your signup form and you want to confirm it before sending welcome email, a single SMTP probe via Kickbox, ZeroBounce, or Clearout API takes ~500ms. Cheap, reliable, prevents bounces.

Investigating brand impersonation

If someone reports a phishing email from [email protected], you want to know:

1. Does that address actually exist? (RCPT TO probe)
2. Is it active? (DMARC reports if they tried to spoof your domain)
3. Can you get it taken down?

The probe answers question 1. Question 2 requires DMARC reporting infrastructure — see our DMARC setup guide. Question 3 means filing an abuse report with Google.

What Gmail's address rules look like

Google enforces specific rules for new Gmail accounts:

Rule	Constraint
Length	6-30 characters
Allowed characters	a-z, 0-9, periods
Cannot start with	Period
Cannot end with	Period
Cannot contain	Consecutive periods
Periods	Ignored — user.name and username are the same mailbox
Plus addressing	Supported — [email protected] routes to [email protected]
Case sensitivity	None — [email protected] and [email protected] are the same

For senders, the dot-ignoring rule matters: [email protected] and [email protected] deliver to the same person. Some users register variants intentionally to track signups. Treat them as one address in your list-deduplication logic.

Practitioner note: Plus addressing on Gmail ([email protected]) is RFC-compliant but some ESPs and signup forms incorrectly reject it. If you accept user signups, your form validation must permit + in the local-part. Rejecting plus addresses is a frequent compliance complaint and breaks legitimate users who use plus tags for filtering.

Google Workspace addresses are different

Custom-domain addresses hosted on Google Workspace ([email protected] via Google) follow tenant-admin rules, not Gmail rules. Length, character, and reserved-name policies vary by domain. Availability is checked in the Workspace admin console, not the public signup page.

For senders, this matters because Google Workspace addresses behave like any other domain for verification purposes — run them through your standard verifier, no Gmail-specific tricks.

What to do with availability data

You found	Action
Address available to register	Decide if you want it for outreach (use Workspace instead)
Address exists, is on your list	Keep it, monitor engagement
Address does not exist (550)	Remove from list
Address temporarily failing (421)	Retry, then quarantine if persistent
Brand-aligned address registered to someone else	Investigate for impersonation, file abuse report if active

For sender-side reputation and authentication context, see Gmail deliverability deep dive and Gmail/Yahoo bulk sender requirements.

If you need help verifying a large set of Gmail addresses, investigating brand impersonation on Gmail, or cleaning a list that has accumulated stale Gmail addresses over years, book a consultation. I run list audits and brand-protection work weekly for senders dealing with these exact questions.

Sources

• Google Account Help: Choose a Gmail username
• Google Email Sender Guidelines
• RFC 5321 — SMTP
• RFC 5233 — Sieve Email Filtering: Subaddress Extension
• Kickbox: Email Verification API
• Google Workspace Admin: Add users

---

v1.0 · May 2026