How to check if an email exists without overstating the result
You can check an address’s format, its domain and its receiving infrastructure. You may also obtain a mailbox response. Those checks can rule out some errors, but they cannot always establish that a specific inbox exists or belongs to the person you expect.
Open the relevant free tool →Technical checks and ownership are separate
Start with the address you were given
Copy the address from its original source and look for missing characters, extra spaces or a mistyped domain. Do not silently guess a replacement. A plausible-looking correction can belong to someone else. If a customer entered the address, offer a suggestion and let them accept it instead of changing their account identifier behind the scenes.
Inspect domain and MX results
A syntax pass only means the string fits the checker’s supported format. Next inspect whether the domain resolves and whether mail routing is configured. A nonexistent domain is a stronger failure than a temporary DNS timeout. An explicit null MX means the domain declares that it accepts no mail. Keep these cases distinct when explaining the result to a user.
Read mailbox evidence as evidence
A SMTP SMTP check may accept the recipient, reject it or return no conclusive answer. Providers can restrict these checks. Even an acceptance may describe a catch-all domain rather than an individual inbox. Avoid claims like “this person definitely uses this address” or “we found their account.” The verifier has not observed those facts.
Use confirmation when ownership matters
For a new account, password-reset destination or sensitive delivery, use a confirmation flow in the application that owns the relationship. Send a time-limited link or code and require the user to complete it. A technical check can speed up the experience before that step by catching obvious mistakes, but it should not grant access or mark an address as owned.
Apply the result to a list
For an existing list, make separate groups for clear failures, contextual risks and unknown results. Combine the verification date with previous bounce reports and the contact source. Keep an audit trail of corrections. If a check is inconclusive, a limited retry later is more appropriate than repeatedly probing or marking the address as confirmed because the domain is familiar.
Worked example
Result: syntax passes, MX present, mailbox unknown. Safe description: “The domain appears configured for mail; this check could not confirm the mailbox.”