Van Born Labs / Guides / Email & Data Quality
Email Verifier with MX, SPF and DMARC (No SMTP)
Syntax, typo suggestions, MX, disposable and role flags, plus published SPF and DMARC — without probing the destination inbox.
By Arkadiusz Van Born. Updated 2026-11-18 (America/Phoenix).
Validating an email list before you import it is one of the few data-quality jobs that pays for itself. Bounces hurt sender reputation. Disposable addresses waste a trial. A typo in a domain (gmial.com) is often recoverable if you catch it early. A published SPF or DMARC record will not tell you if a person wants your mail, but it will tell you whether the domain is set up like a real mailbox domain.
This page describes a conservative verifier: syntax, typo suggestions, MX, disposable and role-account flags, SPF and DMARC — and no SMTP probe of the destination inbox.
What each check actually tells you
- Syntax. If the string is not an email, stop. This is cheap and should always run first.
- Typo suggestions.
gmial.comandyahooo.comare well-known mistakes. A suggestion is a hint for a human or a confirmation form, not an automatic rewrite. - MX records. If the domain publishes no mail exchanger, mail cannot be delivered in the normal way. That is a strong “do not send” signal. The inverse is not a guarantee: an MX record does not prove the mailbox exists.
- Disposable providers. Addresses from throwaway inbox services are often useless for a product relationship. Flag them; let your policy decide.
- Role accounts such as
info@,admin@, orsupport@. These may be valid mailboxes and still be a poor fit for a personalised sales sequence. - SPF and DMARC. These are domain-level records. They are useful for risk and for “does this domain look like a real organisation?” They do not confirm a particular local part.
Van Born Labs
Try it live
Paste an email. You’ll get syntax, typo suggestions, MX, SPF and DMARC — three free checks a day.
Why this verifier does not open SMTP
Some “email verifiers” try a mailbox probe: they start an SMTP conversation with the destination server and ask, in effect, whether the address exists, then quit. That can catch more true/false mailboxes. It can also:
- trip anti-harvesting defences and honeypots,
- get your network flagged,
- and, on catch-all domains, return a confident “yes” that is meaningless.
A verifier that stops at DNS and syntax will miss some dead mailboxes. That is a trade-off. For many list-import and sign-up checks, it is the correct one.
A simple workflow
- De-duplicate the list first. You should not pay twice for the same address in one run.
- Run syntax, typo, MX, disposable, role, SPF and DMARC checks.
- Drop or hold addresses with no MX, obvious syntax errors, or a disposable domain — according to your policy.
- Present typo suggestions to a human or to the user who typed the address. Do not silently rewrite.
- For the remainder, send mail like a responsible sender (permission, authentication, a real unsubscribe path). Validation is not consent.
The Email Verifier & Domain Validator on Apify implements this set of checks at $0.50 per 1,000 unique results, with no SMTP probe and no proxy. The same engine is on RapidAPI as Email Verifier & Domain Validator, with a cap of 50 addresses per call, which is the right shape for a sign-up form or a small app.
Use official bulk-verification products with SMTP probing only if you understand the risk and you have a supplier you trust. Do not run your own probe from a random VPS and hope for the best.
Independent software by Van Born Labs. It will not tell you whether someone wants your email, only whether the address and domain look deliverable on paper.
Questions
What does an MX check tell you?
If a domain publishes no mail exchanger, mail cannot be delivered in the normal way. An MX record does not prove that a specific mailbox exists.
Why skip SMTP probing?
A mailbox probe can trip honeypots and blocklists, and catch-all domains make the result meaningless. A DNS-and-syntax verifier misses some dead mailboxes and avoids that risk.
Tools mentioned
Related guides
Canonical URL: https://arkadiuszvanborn.com/labs/guides/email-verifier-mx-spf-dmarc. Support: arkadiuszvanborn@gmail.com.