Webmaster & Network·4 min read

Email Syntax vs Deliverability: What a Check Proves

A sign-up form that accepts anything containing an @ will happily store addresses that can never receive mail. The fix starts with separating two ideas. Syntax says an address is well formed. Deliverability says a message will actually arrive. There is a lot of space between the two. A validator can prove the first and estimate the second, but only a real delivery settles it. Here is what each layer of checking buys you, where it stops, and how to work within those limits honestly.

Open the free Email Validator All insights

Well formed is not the same as reachable

Three separate claims.

user@gmali.com is perfectly valid syntax and perfectly undeliverable, because the misspelled domain does not run mail. An address at a real company can be well formed, route to a real server and still bounce because the employee left last quarter. Format, domain and mailbox are three separate claims, and each needs its own evidence.

This matters commercially too. A high bounce rate damages your sending reputation with providers like Gmail, and a damaged reputation hurts delivery to your good addresses as well. Filtering out the provably bad ones before you send is cheap insurance.

The three layers of validating an email address

Each layer catches a different failure.

Layer one is syntax: does the string follow the format rules, with one @, a valid name part and a plausible domain? This catches typos and junk input instantly.

Layer two is the domain: does it publish MX records, meaning some server has agreed to accept mail for it? This catches misspelled and abandoned domains, and a null MX that says a domain takes no email at all. Layer three is the mailbox itself, and no outside check can reliably confirm it. Only the receiving server knows whether a mailbox exists, and big providers do not say. Email Validator covers layers one and two, adds flags for disposable and role addresses, and sends nothing, so the person is never contacted.

A worked example: four addresses through the checks

Same tool, four verdicts.

sales@@example.com fails the Syntax box, and the MX box reads Skipped (fix the format first), since a malformed address cannot be routed anyway. The fix is editorial: remove the second @.

hello@gmail.com passes both boxes, and the MX table lists servers such as gmail-smtp-in.l.google.com with their priority numbers, lower numbers tried first. team@a-domain-that-lapsed.com passes Syntax but fails MX, so mail sent there has nowhere to land and will bounce. And an address at a well-known throwaway service passes both checks but gets the verdict Valid, but a throwaway inbox, which is a signal to ask for a real address. Each verdict tells you the next move.

What the MX table actually tells you

DNS shows routing, not residents.

The MX lookup reads public DNS to find the servers accepting mail for a domain, sorted by priority. Records pointing at Google Workspace or Microsoft 365 tell you the domain has live, professionally hosted mail, which makes a random typo less likely. No records tell you delivery is impossible today.

What the table cannot reveal is anything about individual mailboxes, full inboxes or spam filtering on the receiving side. A domain with perfect MX records will still bounce mail sent to a deleted account. Treat an MX pass as necessary but not sufficient.

Disposable and role addresses

Real, but worth a second look.

A disposable address comes from a throwaway inbox service and disappears after a short time. The tool flags domains from a built-in list of well-known providers. New ones appear all the time, so no list is complete. If burner sign-ups are a real cost for you, pair the check with a confirmation email.

A role address such as info@, sales@ or support@ belongs to a team rather than a person. It is often perfectly valid, but several people or nobody may read it, and some email platforms limit sending to them. The badge is a warning, not a failure. Decide how your list should treat them rather than deleting them by reflex.

Validation mistakes that let dead addresses through

Most list quality problems trace back to one of these habits:

Relying on a regex alone. A format check waves through every plausible address at a dead domain, which is exactly the kind that bounces hardest.
Rejecting valid addresses with an overly strict pattern. Plus signs (name+tag@gmail.com), long top-level domains and hyphenated domains are all legal, and homemade patterns often reject real users.
Treating an MX pass as proof the mailbox exists. It proves the domain accepts mail, nothing more.
Validating once and never again. Addresses die as people change jobs, and a list that was clean two years ago is not clean now.

Why mailbox checks from outside are guesses

Know what you are not testing.

The missing layer is SMTP mailbox probing, where a service starts a delivery to see whether the server accepts the recipient, then hangs up. It is slow, can get the checking server flagged, and catch-all servers answer yes to everything. Even paid verification services report a confidence score rather than certainty, so be wary of anyone promising a definite mailbox verdict from the outside.

The only proof that an address belongs to the person who typed it is a confirmation email with a link. For large lists, double opt-in going forward does more for list quality than any one-off check.

Where Email Validator fits next to DNS Lookup

Use Email Validator when the question is about specific addresses: will mail to this contact, or to each of the next hundred, plausibly arrive? For a wider view of the same domain, DNS Lookup shows the full record set and flags whether SPF and DMARC are published, which matters when you are working out why your own outbound mail lands in spam.

If you are pulling addresses out of a long document first, Email Extractor collects them, and you can then spot-check the ones that matter here, one at a time.

Try it now

Open Email Validator

The tool is one click away. No sign up, no upload, no payment.

Open Email Validator

Write a review