Gmail address verification: what you can actually check
A Gmail address can have valid formatting while its mailbox status remains unknown. Start with the address and domain, then treat any mailbox response as limited evidence. Gmail ownership can only be established through a flow that the user completes with access to the account.
Open the relevant free tool →Provider recognition is only the first check
Confirm the domain before the username
Check the spelling after @. A domain that resembles gmail.com may be a typo or a separate domain controlled by someone else. Do not silently fix it in a customer record. Present the suspected correction and ask the user to confirm. If the address uses a company’s domain with Google-hosted mail, it is not a consumer @gmail.com address and should not inherit every consumer Gmail rule.
Understand dots and plus tags
For consumer Gmail addresses, dots do not update the destination. Google explicitly distinguishes this from some work or school addresses. Plus tags are another reason a punctuation-heavy local part should not be rejected just for looking unusual. Keep the supplied address for correspondence and make any deduplication rule provider-specific rather than applying Gmail assumptions across an entire list.
Do not use account-discovery tricks
A login or recovery screen is not an email verification API. Do not build a workflow around trying to identify someone’s account through authentication screens. Use the technical checks available to your application and preserve uncertainty. A checker should never claim to show an account’s owner, activity or private details from the address alone.
Use a confirmation flow for signups
If a person enters the address in your product, check obvious format errors, then send your own time-limited confirmation link or code when ownership matters. Rate-limit that flow and avoid exposing whether a separate customer account exists. Successful confirmation answers a different question from DNS: the user demonstrated access at that time.
Handle Gmail results in a list
Keep recent successful correspondence, consent and bounce history alongside technical verification. A mailbox-unknown result should not erase a reliable customer relationship. Conversely, a familiar Gmail domain should not rescue a clearly mistyped local part. Segment uncertain records for review and use the actual sending provider’s delivery reports to diagnose later failures.