Check the address format
An email address is a local part, such as a user name, followed by an at sign (@) and a domain; RFC 5322 defines the format. RFC 5321, the SMTP standard, limits the local part to 64 octets, or 64 characters in plain ASCII. The whole address should not exceed 254 octets: SMTP allows 256 for the path, which includes the angle brackets around the address, and a server may reject a longer one.
A format check catches typing mistakes, such as a missing at sign or domain. It should not be stricter than the standard: characters such as + and _ are allowed in the local part, so user+shop@example.com is correctly formatted.
With auto-correct on, Email Verifier and Email Validator also fix common domain typos such as gmial.com before the check and show this in Typos Fixed.
Check the domain and its MX records
A sender looks first for the domain's MX records, which point to the servers that receive its mail. If the domain does not exist, delivery fails. If it has no MX records, RFC 5321 applies an “implicit MX” that points to the domain itself, so mail arrives only if a mail server answers at the domain's own address.
A domain that accepts no email can publish a null MX: a single MX record with preference 0 and the name “.” (RFC 7505). Senders then learn on the first attempt that the address cannot receive mail, instead of retrying, typically for a week. The documentation domain example.com publishes one (checked in November 2026).
Email Verifier and Email Validator report this step in Domain Status: Can receive email, or the reason it cannot, such as Invalid domain or No MX records. The tools count a domain without MX records as unable to receive email, which is stricter than the implicit MX rule.
Ask the mail server about the mailbox
To test the mailbox itself, a checker opens an SMTP session with the domain's mail server, gives a sender with MAIL FROM and names the address with RCPT TO. It reads the reply and ends the session before DATA, the command that starts the message transfer, so no email is sent.
- 250: the server accepts the address.
- 550: the server refuses it. RFC 5321 lists a missing mailbox, no access and policy rejections as causes, so a 550 does not prove that the mailbox is missing.
- 4xx, such as 450: a temporary failure; the same request may succeed later.
Even a 250 is not a promise: some servers check recipients only after the message text arrives and report failures later. SMTP also has a VRFY command that asks about an address directly, but sites may disable it for security reasons and must then answer 252, which neither confirms nor rejects the address.
Why some answers stay unconfirmed
A catch-all domain accepts mail for any address, including addresses with no mailbox. Google Workspace, for example, lets administrators route mail for non-existent addresses into one mailbox. On such a domain, a 250 says nothing about the address you are checking. Email Verifier flags these domains as Catch-All.
Greylisting, an anti-spam technique described in RFC 6647, has a similar effect: the server answers unfamiliar senders with a temporary 4xx reply and invites a retry after a minimum time, such as 30 minutes. The reply does not tell the sender whether greylisting or a local problem caused it. Email Verifier shows a postponed answer as Deferred; the address may still be valid.
Confirm with an email and a link
The checks above test the address, not the person. A confirmation email closes that gap: send a message with a link, and use the address only after someone clicks it. The anti-abuse group M3AAWG calls this confirmed opt-in, or double opt-in, the highest standard of opt-in, because it stops a typo or a maliciously submitted address from being added to a mailing list.
- Keep the confirmation email simple and free of advertising, so it is not filtered as abuse.
- Confirm a changed address in the same way as a new one.
- Protect the form with a CAPTCHA and rate limits: scripts can enter one person's address in many forms to flood that mailbox with confirmation emails, which M3AAWG calls list bombing.
How to read an Email Verifier result
Email Verifier runs the syntax and domain checks first, then asks the mail server over SMTP; some servers take up to 60 seconds to answer. The result starts with one of three labels:
- Verified: the server confirmed the mailbox.
- Valid (Unverified): the address passed the syntax and domain checks, but the mailbox could not be confirmed, for example on a catch-all domain or after a delayed answer.
- Invalid Email: the address failed the checks. The tool page's example, user@example.com, gets this label because example.com accepts no email.
The other fields explain the label: SMTP Status sums up the mailbox check, SMTP Response shows the mail server's own reply when a server answered, and Deferred and Catch-All flag the cases described above. Free Email and Disposable show whether the address comes from a free service such as Gmail or from a temporary email service, not whether the mailbox exists.
Decide in advance what each label means for your sign-up form. Valid (Unverified) means unknown, not false: you can accept the address and let the confirmation email settle it.
Terms in this guide: MX record, SMTP verification, Catch-all domain, Disposable email address
Sources
- RFC 5322: Internet Message Format (IETF, October 2008; Sections 3.2.3 and 3.4.1)
- RFC 5321: Simple Mail Transfer Protocol (IETF, October 2008; Sections 3.3, 3.5, 4.1.2, 4.2, 4.5.3.1, 5.1 and 7.3)
- RFC 3696: Application Techniques for Checking and Transformation of Names (RFC Editor, Erratum ID 1690, verified April 2010)
- RFC 7505: A “Null MX” No Service Resource Record for Domains That Accept No Mail (IETF, June 2015)
- RFC 2606: Reserved Top Level DNS Names (IETF, June 1999; Section 3)
- MX lookup for example.com (Google Public DNS, checked 6 November 2026)
- Get misaddressed email in a catch-all mailbox (Google Workspace Admin Help)
- RFC 6647: Email Greylisting: An Applicability Statement for SMTP (IETF, June 2012)
- M3AAWG Sender Best Common Practices, Version 4.0 (M3AAWG, August 2026)