What is DNS Validation?

Definition

DNS validation, in the context of email verification, is the process of checking the DNS records of the domain in an email address to determine whether that domain can receive email. Every email address has two parts, the local part before the at sign and the domain after it. DNS validation is concerned entirely with the domain part, asking a single core question: is this a real, mail-capable domain.

DNS, the Domain Name System, is the distributed directory the internet uses to translate human-readable domain names into the information machines need. Within DNS, different record types serve different roles. An MX record names the mail servers that receive email for a domain. An A record maps a domain to an IPv4 address and an AAAA record to an IPv6 address. DNS validation queries these records to build a picture of whether mail to the domain has anywhere to land.

It helps to be precise about what DNS validation can and cannot tell you. It confirms the domain exists in DNS and that the domain is configured to receive mail. It does not confirm that any particular mailbox at that domain exists. A domain can have flawless DNS records while the specific address user@example.com has no mailbox behind it at all. DNS validation establishes that the destination domain is real and reachable, and a later, separate check tests the individual address.

How It Works

DNS validation is a sequence of DNS lookups against the address's domain. The central lookup is the MX query. The verifier asks DNS for the domain's MX records, and the answer is the list of mail servers, each with a priority value, that the domain has designated to receive its email. If the domain returns valid MX records, it is configured to accept mail. If it returns none, the domain cannot receive email in the normal way, and any address on that domain is undeliverable.

Beyond the MX lookup, DNS validation can resolve the hostnames the MX records point to. The email standards require each MX hostname to map to a valid A or AAAA address record, so a verifier can confirm those hostnames actually resolve to reachable mail servers rather than to dead names. DNS validation also commonly checks whether the domain resolves at all, which catches domains that were never registered, have expired, or were simply mistyped. When a domain publishes no MX record, a verifier may consider whether an A or AAAA record exists as a delivery fallback, though that fallback is fragile and treated cautiously.

The reason DNS validation runs early is efficiency. Email verification is built as a series of stages ordered from cheapest to most expensive. Syntax parsing comes first because it is nearly free. DNS validation comes next because a DNS lookup is fast and lightweight. The live SMTP handshake comes later because it requires opening a real network connection to a mail server. By placing DNS validation before the SMTP stage, a verifier eliminates every address whose domain cannot receive mail at all, so the slow and resource-intensive SMTP check only ever runs against addresses that are still plausible.

Why It Matters for Email Deliverability

DNS validation catches a category of bad addresses that is both common and entirely avoidable: addresses on domains that cannot receive mail. This includes domains that were never registered, domains that have expired, domains mistyped at signup, and domains that exist but publish no MX records. Every one of these produces a hard bounce if you send to it, because the message has no valid destination.

Hard bounces are the most damaging kind of delivery failure for your reputation. Mailbox providers watch hard bounce rates closely and read a high rate as proof that a sender is mailing low-quality, unverified data. The consequence is reduced inbox placement, with more of your mail diverted to spam folders, and that penalty applies to your entire audience, not just the bad addresses. A widely used benchmark is to keep overall bounce rate below two percent, and addresses that fail DNS validation are a direct, preventable contributor to crossing that threshold.

There is an efficiency angle as well. Addresses that fail DNS validation never need to reach the expensive SMTP stage of verification, so a verifier that does DNS validation well processes large lists faster and more cheaply. For a sender, removing DNS-failing addresses before a campaign means none of those guaranteed bounces ever touch your sending reputation. DNS validation is a small, fast check that prevents a disproportionate amount of deliverability damage.

How VeriMails Handles It

DNS validation is a built-in stage of the VeriMails verification pipeline. For every address you submit, VeriMails queries the domain's DNS records, performs an MX lookup to confirm the domain publishes valid MX records, and checks that the domain resolves and that its mail servers are reachable. A domain that fails these checks cannot receive email, so VeriMails marks the address as undeliverable quickly, before spending resources on later stages.

DNS validation works as part of a layered set of checks. Syntax is validated first, DNS validation and the MX lookup come next, and a live SMTP handshake then tests whether the specific mailbox accepts mail. VeriMails also performs catch-all detection and flags disposable and role-based addresses. Because DNS validation runs early, an address on a dead, expired, or non-mail domain is filtered out immediately rather than after a wasted connection attempt, which keeps verification both accurate and fast.

VeriMails reports clear deliverability results rather than a vague numeric score, and DNS validation is one of the checks behind its clear deliverability categories. You can run verification through the REST API for real-time checks or upload a CSV for bulk verification of an entire list. Verification starts at $0.0019 per email, with 10,000 credits for $19, and subscription plans begin at $15 per month. Every new account includes 100 free credits with no credit card required, and those credits never expire.

Frequently Asked Questions