%20What%20is%20a%20good%20open%20rate%20for%20email%202%20-%20Copy.jpg)
Email validation evaluates an email address in layers. It starts with inexpensive deterministic checks such as format and domain configuration, then uses mail-server and risk signals where the receiving system allows them. The goal is to estimate whether an address is usable without sending a message.
This guide focuses on how the process works. If you are looking for the broader business case for validation in campaigns, see why email validation matters for email marketing.
What Email Validation Checks
1. Syntax and format
The address is checked for a valid local part, an @ symbol, and a domain. This catches malformed values before any network request is made.
2. Domain and DNS
The verifier checks whether the domain exists and whether its DNS configuration indicates that it can receive email.
3. MX records
Mail exchanger records identify the servers responsible for receiving email for the domain. Missing or unusable MX configuration is a strong signal that the address cannot receive normal mail.
4. Mail-server response
Where the receiving server permits it, the verifier can evaluate server responses related to the specific mailbox. Not every provider exposes the same level of detail, so mailbox-level certainty can vary.
5. Risk signals
Additional checks can identify disposable services, catch-all domains, role-based addresses, and other signals that make an address less certain or less suitable for a marketing workflow.
Email Validation vs. Email Verification
The terms are often used interchangeably. In stricter usage, validation can refer to syntax and domain checks, while verification includes deeper mail-server and mailbox-level signals. Proofy combines these layers in one verification workflow rather than treating them as separate products.
For the technical overview behind Proofy's process, see how email verification works.
What the Results Mean
- Valid: available signals support sending to the address.
- Invalid: the address fails one or more decisive checks.
- Risky: the address or domain has signals such as catch-all or other uncertainty that should be reviewed before sending.
- Unknown: the receiving infrastructure did not provide enough information for a confident result.
A verifier should not force every address into Valid or Invalid. Returning uncertain cases separately is more useful than pretending the mail server provided evidence it did not provide.
When to Validate an Email Address
- At signup: use real-time validation to catch malformed or clearly unusable addresses before they enter the database.
- Before importing a list: validate a CRM export or acquired first-party list before the receiving ESP evaluates the first campaign.
- Before a major send: re-check older lists when contact quality is uncertain.
- After a long period of inactivity: mailbox status can change after an address was originally collected.
Bulk Validation vs. Real-Time API
Bulk email validation
For existing files and large database cleanups, use bulk email verification. Proofy supports CSV and TXT files, with up to 65 MB and up to 1 million addresses per file.
Real-time validation
For forms, applications, CRMs, and automated workflows, use the Email Verification API. The API is designed to return structured verification results that your application can handle according to its own rules.
Common Validation Mistakes
- Treating syntax as deliverability. A well-formed address can still point to a domain or mailbox that cannot receive mail.
- Treating catch-all as confirmed. A catch-all server may accept mail for many local parts without proving that a specific mailbox exists.
- Deleting every Unknown result immediately. Unknown means the available server response was inconclusive, not automatically invalid.
- Assuming a past result is permanent. Domains, mailboxes, and server behavior change over time.
- Using verification as proof of consent. Technical validity does not establish marketing permission.
Frequently Asked Questions
Does email validation send a message?
No. Verification evaluates technical signals without sending a normal email to the recipient.
Can validation guarantee delivery?
No. A result reflects the signals available at verification time. Future delivery also depends on mailbox changes, sender reputation, authentication, content, recipient behavior, and provider policy.
Can I validate one address for free?
Yes. The Free Email Checker is designed for one-off checks.
What is the best option for an existing list?
Use bulk verification for a file-based workflow. If the goal is broader database hygiene that also includes duplicates and list-quality cleanup, see email list cleaning.
Bottom Line
Email validation works best as a layered evidence process: format first, domain and MX next, then mail-server and risk signals where available. Use bulk verification for existing files and a real-time API for addresses entering your systems.
