01 · Definition
What is email address validator?
An email address validator checks whether an email address is real and deliverable. It combines syntax parsing, MX record resolution, SMTP-level mailbox probing, and disposable-provider detection into a single result. The outcome is a six-way verdict: valid, invalid, catch-all, unknown, disposable, or spam trap.
The tool above submits each address through four sequential checks: RFC 5321/5322 format validation, domain MX lookup, SMTP handshake, and disposable-provider matching. It returns the primary verdict alongside flags for free providers and role accounts (info@, support@, noreply@). If it spots a likely typo in the domain, it surfaces a correction. Read the in-depth email address validator guide for what each verdict means, how to interpret role and free flags, and where full validation fits in a list-cleaning workflow.
02 · Process
How it works
- 1Submit the email address.Enter any address and click Validate. The tool passes it to the Spotzee Extended API for multi-step verification.
- 2Syntax check.The format is validated against RFC 5321 and RFC 5322 rules. A format failure returns immediately, without hitting DNS or SMTP.
- 3Domain and MX resolution.The domain is resolved in DNS to confirm MX records exist. No MX records means the domain cannot receive mail at all.
- 4SMTP handshake.The tool connects to the highest-priority mail server and asks whether the mailbox exists. The server response determines the final verdict.
- 5Return the result.The response includes the primary verdict, an expanded detail code, role and free-provider flags, and a typo suggestion if the domain looks misspelt.
03 · Risk
Why it matters
Invalid addresses in a mailing list cost money in two ways. Sending providers charge per message, valid or not. Mail servers penalise senders for the resulting bounces, dragging inbox placement down for the whole list, including the valid contacts.
Full email validation catches the failures a pure syntax check misses: correctly formatted addresses at domains with no MX records, defunct mailboxes on live domains, disposable addresses created to bypass signup forms, and role accounts that spam filters treat with more scrutiny. The validator flags all four without requiring separate checks.
04 · Use cases
Common ways to use this tool
- List cleaning before a campaign. Run the list through the validator, remove invalid and disposable addresses, and the survivors go to your ESP with a lower bounce risk and better inbox placement.
- Signup form validation. Wire the API into your registration flow to block disposable addresses and catch domain typos at the point of entry, before the contact enters your database.
- Catch-all domain identification. A catch-all result means the server accepts every address at the domain, so individual mailbox existence cannot be confirmed. Flag these for a double opt-in step before sending.
- Role address filtering. Role accounts (info@, admin@, noreply@) often reach distribution groups or go unmonitored. The validator flags them so you can segment or suppress them ahead of cold campaigns.
05 · Interpretation
What to check in the result
- result: invalid. The address does not exist or the domain cannot receive mail. Remove it from your sending list. If expanded_result is bad_domain, the domain itself does not resolve — a sign of a manufactured or expired address.
- result: disposable. The address was created with a throwaway provider. These addresses expire and always hard-bounce. Remove them immediately.
- result: spam_trap. The address is operated by a blacklist or ISP to identify senders who skip list hygiene. Sending to one damages your sender reputation. Suppress it immediately.
- result: catch_all. The domain accepts any address. The validator cannot confirm whether this mailbox exists. Treat catch-all results as unconfirmed and consider a double opt-in before adding them to an active send list.
- role: true. Role accounts reach teams or distribution groups, not a named individual. They generate more spam complaints and are less likely to convert. Segment them separately or suppress them for cold outreach.
- didyoumean not empty. The validator detected a likely domain typo and suggested a correction. Review the suggestion and, where possible, confirm the intended address with the contact before adding it to a list.