Gmail Username Checker

📬 Gmail username checker for bulk availability

Gmail Username Checker helps you check Gmail username availability in bulk before you choose a new @gmail.com address. Paste usernames such as brandname2026, full Gmail addresses such as launch.team@gmail.com, or copied comma/newline-separated text. The Actor returns one clean dataset row per final Gmail username result: available, taken, or invalid.

Use it when you are naming a brand inbox, checking personal handle ideas, monitoring Gmail address options, or preparing a list of possible Gmail usernames before a launch. The Actor checks Gmail registration availability only. It does not create accounts, reserve names, log in to Google, ask for Google credentials, or verify inbox ownership.

For a quick first run, keep the prefilled examples or paste 5-10 username ideas. Results are saved to the Apify dataset, where you can export JSON, CSV, Excel, or connect the output to the Apify API, schedules, webhooks, or your own workflow.

✅ What this Gmail username availability checker does

• Checks Gmail usernames in bulk.
• Accepts plain usernames, full @gmail.com addresses, and pasted comma/newline-separated text.
• Normalizes each valid input into a username and full Gmail email.
• Returns final usable available, taken, or invalid results.
• Adds a plain-English reason when Gmail returns a username-level validation message.
• Saves a checkedAt timestamp for each emitted row.
• Skips malformed inputs and temporary source failures instead of saving placeholder rows.

This Actor is focused only on Gmail registration availability for @gmail.com. It does not check Google Workspace domains, custom email domains, SMTP delivery, inbox access, account recovery, or whether an existing mailbox can receive mail.

📊 What data you get

Each output row represents one requested Gmail username after normalization:

Field	Description
input	Original username or Gmail address you entered.
username	Normalized Gmail username.
email	Full normalized @gmail.com address.
validUsername	Whether the input matched the supported Gmail username format.
availabilityStatus	available, taken, or invalid.
available	true when available, false when taken, otherwise null.
reason	Gmail validation message when the username is invalid, otherwise null.
sourceProvider	Always gmail.
sourceQueryType	Always registration_availability.
runStatus	Always ok for emitted final results.
checkedAt	UTC timestamp when the username was checked.

The dataset is built for filtering and exports. You can sort by availabilityStatus, keep only available usernames, review invalid reasons, or join results back to your source list with input.

🧭 Common use cases

• Check brand email ideas before choosing a public contact address.
• Compare Gmail handle options for a personal project, product, or launch.
• Monitor whether a short list of Gmail usernames remains available over time.
• Clean a spreadsheet of Gmail address ideas before sharing it with a team.
• Feed availability results into an API, webhook, spreadsheet, or scheduled Apify workflow.

🚀 How to run it

1. Open the Actor input.
2. Add Gmail usernames or full @gmail.com addresses in Gmail usernames.
3. Choose Proxy country only if your workflow needs a listed source-access region.
4. Start the Actor and open the dataset when it finishes.

For the clearest first run, use a short list of real ideas. Large generated lists are fine later, but a smaller first run makes it easier to confirm the output fields and pricing behavior.

🧾 Input example

{
	"targets": [
		"brandname2026",
		"launch.team@gmail.com",
		"newproductideas"
	],
	"country": "US"
}

Gmail usernames

Enter one username or Gmail address per line. You can also paste comma-separated or mixed copied text. The Actor supports Gmail usernames from 6 to 30 characters using letters, numbers, and periods.

Proxy country

United States is the best default for most runs. Choose another listed country only when your workflow needs that source-access region.

📤 Output example

{
	"input": "brandname2026",
	"username": "brandname2026",
	"email": "brandname2026@gmail.com",
	"validUsername": true,
	"availabilityStatus": "available",
	"available": true,
	"reason": null,
	"sourceProvider": "gmail",
	"sourceQueryType": "registration_availability",
	"runStatus": "ok",
	"checkedAt": "2026-06-15T21:36:54.744Z"
}

💳 Pricing

This Actor uses pay-per-event pricing:

• A small Actor start charge applies when a run starts.
• Each valid Gmail username availability result saved to the dataset is charged as one gmail-username-checked event.
• Malformed inputs and temporary source failures are skipped and are not charged as username checks.

Use a short username list for your first run, then paste larger batches when the output matches your workflow.

⚠️ Limits and caveats

• Only Gmail @gmail.com usernames are supported.
• Usernames must be 6-30 characters and can use letters, numbers, and periods.
• Gmail availability can change after a run if someone registers a username later.
• If Gmail does not return a clear availability result at that moment, the Actor skips that username instead of saving a non-final row.
• The Actor checks availability only. It does not create, reserve, or manage Google accounts.

❓ FAQ

Does this Gmail username checker create accounts?

No. It only checks whether Gmail reports a username as available for registration. It does not create accounts, reserve usernames, or ask for Google login details.

Can I paste full Gmail addresses?

Yes. You can paste name@gmail.com or just name. The output normalizes valid inputs into both username and email.

Does it check Google Workspace or custom domains?

No. This Actor checks Gmail username availability for @gmail.com registration only.

Is this the same as email verification?

No. Email verification checks whether an address or domain may receive email. This Actor checks whether Gmail reports a username as available for new Gmail registration.

Why did a row return invalid?

The username passed the Actor's basic format check, but Gmail returned a username-level validation message. The reason field shows that message when Gmail provides it.

Can I schedule repeat checks?

Yes. You can schedule the Actor on Apify and compare datasets over time. Remember that availability reflects the moment each run was checked.

📝 Changelog

• 0.1: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• SMTP Email Verifier ↗ - Check email syntax, MX records, SMTP mailbox response, catch-all behavior, and delivery risk.
• Email MX Verifier ↗ - Check email syntax, MX records, disposable domains, role addresses, and free-provider signals.
• Unicode Text Inspector ↗ - Find hidden Unicode characters, zero-width spaces, bidi controls, and homoglyph risks in text.
• Profanity Checker ↗ - Check text snippets for blocked words and export cleaned text with match evidence.
• Website Emails Scraper ↗ - Find public contact emails from company websites for lead and outreach workflows.

Made with ❤️ by Maxime Dupré