Article

Can You Verify an Email Address With Just DNS? What It Can and Can't Prove

By Unlimited Verifier Team ·

Diagram showing a DNS domain check as the first stage before an SMTP mailbox check when verifying an email address with just DNS.

Summary

No. DNS can only show that a domain is set up to receive mail through its MX or A records, not whether a specific mailbox exists. Confirming an individual address requires an SMTP RCPT TO probe, with DNS used as a fast first filter to remove dead domains.

No, DNS alone cannot verify an individual email address, because it can only confirm that a domain is set up to receive mail. Checking whether a specific mailbox exists requires an SMTP RCPT TO probe, which asks the receiving server directly.

DNS still earns a place in list cleaning. It is fast, inexpensive to run in bulk, and it removes whole domains that can never receive mail. It is the wrong tool for deciding whether an individual address will bounce, and that gap is where most list damage hides. This guide explains what each DNS record proves, where DNS-only checks fail, and how to combine DNS with full verification in the right order. For the wider picture, start with how email verification works.

Quick answer

What can a DNS lookup actually tell you about an email address?

A DNS lookup tells you whether the domain after the @ exists, which hosts accept its mail, and what sending policies it publishes. It says nothing about the part before the @, because DNS has no record type for individual mailboxes.

Record What it tells you What it does not tell you
A / AAAA The domain resolves to a host address Whether that host runs an SMTP server on port 25
MX Which hosts accept mail for the domain, ranked by preference Whether any mailbox on those hosts exists
Null MX (0 .) The domain has declared it accepts no mail, per RFC 7505 Anything about mailboxes; this is a clear "no"
TXT (SPF) Which servers may send for the domain, per RFC 7208 Whether the domain can receive mail
TXT (DMARC, DKIM) Sending authentication policy and signing keys Receiving status or mailbox validity
NXDOMAIN status The domain name does not exist in DNS Nothing further; this is a hard fail

Two details matter in practice. First, the MX record is the signal that counts for receiving. RFC 5321 says that if a domain has no MX record, the sender should fall back to the domain's A record. An A-only domain can therefore be attempted, but a parked website with an A record is a weak receiving signal. Second, a missing SPF or DMARC record does not stop a domain from receiving mail. Plenty of domains that accept mail publish no sending policy at all, so rejecting a domain for lacking SPF removes good contacts.

Bottom line: A usable DNS check reads the MX record and the NXDOMAIN status. SPF and DMARC describe sending, not receiving.

Why can't DNS confirm that a mailbox exists?

DNS cannot confirm a mailbox because the list of valid users lives inside the receiving mail server, not in the DNS zone. DNS answers "which server handles mail for this domain?" The server then decides whether a user exists during the SMTP conversation, at the RCPT TO command.

A rejection at that stage typically looks like 550 5.1.1. The 5.1.1 is the enhanced status code for a bad destination mailbox, defined in RFC 3463. The VRFY command was designed to ask a server whether a user exists, but many servers disable it, so RCPT TO is the main automated probe. For a closer look at the probe itself, read what RCPT TO means in email verification. The full sequence of steps is explained in how an email verifier checks if an address exists.

The consequence is that a domain can have perfectly healthy DNS and zero working mailboxes. A company that has wound down its staff but still pays for its domain and mail hosting is a common example. Its MX records resolve, the domain passes every DNS test, and every address sent there bounces.

Bottom line: DNS tells you the building exists. Only the SMTP conversation tells you whether anyone is at the desk.

Where does a DNS-only check go wrong?

A DNS-only check fails in six predictable ways, and each one leads either to a bounce or to a wrongly deleted contact. Knowing these failure modes is more useful than memorising record types.

  1. Catch-all domains. The receiving server accepts any local part, so DNS passes and SMTP accepts even made-up addresses. Neither check can confirm the specific mailbox. How verifiers detect catch-all domains explains the detection logic, and what send-based catch-all verification is covers the one method that can add evidence for these addresses. Unlimited Verifier flags catch-all domains so you can treat them separately; see its catch-all email verification page for how they are handled.
  2. Live domain, dead mailbox. The MX records resolve, but the people have left. DNS cannot see this at all.
  3. Lookalike domains. Typo and squatted domains are sometimes registered and configured to receive mail. They pass DNS and tell you nothing about whether the person meant to type them.
  4. Mail routed through a gateway. An MX record may point to a filtering service that accepts the message and routes it internally. DNS shows the gateway, not whether the internal mailbox exists.
  5. Temporary failures. A SERVFAIL or timeout is a resolver problem, not proof that a domain is invalid. Marking these as invalid is one of the most common and costly errors.
  6. Newly registered domains. A domain launched recently may not yet publish MX records. Recheck before deleting anything.

DNS is not the only place failures hide. Hosts that rate-limit or block probes can pass the DNS stage and then fail the SMTP stage without a clear answer. Why mail servers block email verification probes covers this in detail.

Bottom line: A DNS pass means the domain can receive mail. It does not mean the address will.

How does DNS compare with SMTP and full verification?

Each method answers a different question, so they stack rather than compete. The table below shows what each one catches and where it stops. If you are comparing vendors afterwards, our guide to the best email verification tools and how to choose an email verifier cover the selection criteria.

Method Question it answers Cost and speed in bulk Catches Misses
Syntax check (see syntax validation) Is the address well formed? Local processing, no network lookups Typos, spaces, missing @ Any real-world failure
DNS / MX lookup Does the domain exist and accept mail? Network lookups; quick per domain Dead, parked and null-MX domains Dead mailboxes on live domains
SMTP RCPT TO probe Does this server accept this recipient? Slowest stage; often rate-limited Nonexistent mailboxes on non-catch-all servers Catch-all servers; blocked probes
Full verification All of the above, plus catch-all, disposable and role flags Per-address pricing or plan quota Most invalid addresses; flags Risky ones Consent and engagement

No single row is enough for a clean list. DNS is the cheapest way to remove whole domains. SMTP is the main automated way to test individual mailboxes. Full verification adds the context a mailbox provider or reviewer cares about, such as whether a domain is disposable or a role account. Note that "valid" is not the same as "deliverable" either. What deliverable means in email verification explains the difference.

Bottom line: Run DNS first to shrink the job, then SMTP and full checks to finish it.

How do you run a DNS check yourself?

You can run a DNS check yourself with dig on macOS or Linux. It is practical for a handful of domains but slow for a large list. The steps below assume a terminal and a text file of domains. For the logic behind domain acceptance, see how verifiers check if a domain accepts mail.

  1. Extract unique domains. Split each address on the @, lowercase the result, and remove duplicates. Consumer-heavy lists often contain far fewer unique domains than addresses, so you check each domain once and reuse the result.
  2. Query MX records and read the status. Run dig MX example.com and check the status: field in the header. NOERROR means the query worked, NXDOMAIN means the domain does not exist, and SERVFAIL means the resolver failed.
  3. Read the answer section. NOERROR with no answer means the domain has no MX record. Check for an A record with dig A example.com, and count that as a weak pass.
  4. Look for null MX. An answer of 0 . means the domain has declared it accepts no mail. Mark it as a fail.
  5. Sort each domain into pass, fail or unknown. Treat NXDOMAIN, null MX, and no MX plus no A record as fail. Treat an MX record as pass. Treat SERVFAIL and timeouts as unknown, and retry them at least twice, a few hours apart, before deciding.
  6. Map the status back to your list. Join the results to your addresses so every row carries its domain status.

To script step 2 across a file of domains, use:

while read -r d; do
  s=$(dig MX "$d" | grep -o 'status: [A-Z]*' | cut -d' ' -f2)
  echo "$d $s"
done < domains.txt

Do not use dig +short for this job. It hides the status code, so a blank result could mean NXDOMAIN, no MX record, or a timeout. Those three outcomes need different handling. Output formats also differ slightly between operating systems, so test the script against a domain you know before trusting it.

Bottom line: DNS checks are straightforward by hand, but the status code, not the answer, is what you need to read.

What is a DNS-first framework for a large list?

A DNS-first framework runs the cheapest checks first, keeps unknowns out of the delete pile, and reserves mailbox-level checks for the addresses that survive. This is the sequence we recommend for marketers, agencies and SaaS teams cleaning a list for ecommerce or SaaS.

  1. Validate syntax first. It is local and inexpensive. Remove malformed addresses before any network work.
  2. Deduplicate by domain. Check each domain once and reuse the result for every address on it.
  3. Assign a DNS status per domain. Use pass, fail or unknown, following the rules above.
  4. Quarantine the unknowns. Retry them later instead of deleting them.
  5. Run the mailbox check on the survivors. Include SMTP probing, catch-all detection, and disposable and role flags. The difference between standard and deep checks is covered in deep versus standard verification.
  6. Route the results. Valid addresses go to your first sends, Risky addresses wait, and Invalid addresses are suppressed. The rest of the maintenance cycle is set out in email list maintenance best practices.

Following this order means every expensive check runs on a smaller, cleaner set of addresses. It also means your Risky bucket is built from addresses that have already passed the cheap tests, which makes it easier to explain to a reviewer.

Bottom line: Cheap checks first, quarantine the unknowns, and send mailbox checks only to what is left.

What does a DNS-first run look like on a 10,000-row list?

The example below is illustrative. The counts are hypothetical, but the arithmetic and the plan limits are real.

Imagine a 10,000-row list exported from a signup form.

Stage 0: syntax. 188 rows are malformed. That leaves 9,812 rows (188 ÷ 10,000 = 1.9% removed).

Stage 1: DNS. Of the 9,812 rows:

Stage 2: mailbox checks on the 9,373 survivors. Hypothetical results:

Check: 6,890 + 1,405 + 1,078 = 9,373.

Why the DNS stage alone is not enough. If you had sent to all 9,373 DNS survivors, the 1,078 dead mailboxes would have produced about 11.5% bounces from that group (1,078 ÷ 9,373 = 11.5%). Amazon SES's sending documentation describes a bounce rate of 5% as a level that puts accounts under review, so 11.5% on a first send would be a serious problem. Other platforms act at different thresholds, and sources disagree on the exact figure. We recommend planning around a 2% ceiling, which is well below any platform's trigger.

Final tally. Invalid addresses total 1,705: 188 syntax fails, 439 DNS fails and 1,078 mailbox fails (188 + 439 + 1,078 = 1,705). Valid is 6,890 (68.9% of the original 10,000), Risky is 1,405, and 6,890 + 1,405 + 1,705 = 10,000.

Plan limits. The Free plan allows 25 lists a month of up to 150 emails each. That is at most 3,750 emails a month (25 × 150), and this 10,000-row file would need 67 lists (10,000 ÷ 150 = 66.7, rounded up), so it cannot be processed on Free in one month. Pro allows lists of up to 25,000 emails, so the whole file fits in one list. Pro also includes 25,000 deep verifications a month, so all 10,000 rows can be deep-checked with 15,000 deep verifications to spare. On Free, the 750 deep verifications would cover only 7.6% of the 9,812 rows that reach the mailbox stage (750 ÷ 9,812).

Cost. At Pro's $29 monthly price, this run costs $2.90 per 1,000 rows ($29 ÷ 10). The cost per 1,000 falls if you use the same plan across several lists in the month. Compare email verification pricing on that basis rather than on the headline monthly price alone.

Bottom line: DNS removed 439 rows cheaply, but the mailbox stage found more than twice as many bad addresses among the rest, so you need both.

How do you run the full check in Unlimited Verifier?

Unlimited Verifier runs the domain and MX checks as part of its full pass, so you do not need to script DNS yourself for a standard list cleaning. The steps below assume you start from a CSV export of your email platform.

  1. Export a CSV. Include the email column and any engagement fields, such as last open or signup date. Keep a separate file of bounced and suppressed contacts for your records.
  2. Sign up for a free account. The Free plan covers lists of up to 150 emails, with 25 lists a month.
  3. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  4. Let the checks run. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
  5. Read the three buckets. Valid addresses are safe for first sends. Invalid addresses should be suppressed. Risky addresses, including catch-all, disposable and role accounts, should wait until the rest of the list has proven stable.
  6. Export the results. Download CSV, Excel or JSON, and save the summary counts for your records.
  7. Re-import only the Valid contacts. Unlimited Verifier has no native ESP, CRM or Zapier integration, so you export the file, re-import the Valid segment, and add the Invalid addresses to your suppression list.

For one address, such as a VIP customer who came back Risky, the free email checker gives a quick answer without uploading a file. The tool suite also includes a free domain blacklist checker, which is useful for domains that pass DNS but may be listed on a blocklist.

If you want checks at the point of signup rather than in batches, the email verification API handles single-email checks and bulk requests of up to 10,000 emails per request. API access is included on Pro, with 100,000 emails a month. The workflow is covered in real-time email validation and in our guide to email verification API and automation.

Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark. Its verification engine is also open source on GitHub, so you can read how the checks are implemented.

Bottom line: One upload covers the DNS stage and the mailbox stage, and the Valid, Risky and Invalid buckets tell you what to do with each row.

Does a DNS or mailbox check satisfy consent rules?

No. DNS and mailbox checks support deliverability and list hygiene, but they do not prove consent. Mailbox providers and regulators judge what you send and how you collected the addresses, not how cleanly they verified.

Google's email sender guidelines are a good example of where sources disagree. Many guides quote a 0.3% spam-rate limit, but Google's own wording pairs a target of 0.1% with a ceiling of 0.3%. We recommend planning to the 0.1% target. A verified list keeps bounces low, which helps you stay under those limits, but a complaint from someone who never opted in still counts. In the US, the FTC's CAN-SPAM compliance guide sets the baseline for commercial email. For how verification fits into a broader programme, see email verification compliance and hygiene.

Bottom line: Verification protects deliverability. Consent protects you legally and with recipients, and DNS cannot show it.

What are the most common DNS verification mistakes?

The most common mistakes come from reading DNS results too literally or deleting on the wrong signal.

Bottom line: Read the status codes, retry the unknowns, and never let a DNS pass stand in for a mailbox result.

How we compared (and limitations)

This guide draws on the public DNS and SMTP standards cited above, Google's and Amazon's published sending documentation, the FTC's CAN-SPAM guidance, and the Unlimited Verifier plan facts. We have not run controlled tests against any vendor or mail provider, and dig output formats can vary by operating system.

The worked example uses hypothetical counts. The plan limits and arithmetic are real. Whether a given mail server accepts or rejects a probe depends on that server's policy, which can change without notice, so treat any single probe result as one signal among several.

Two-stage verification order

  1. Syntax check: discard malformed addresses.
  2. DNS check: NXDOMAIN or null MX means remove; SERVFAIL or timeout means unknown and retry.
  3. MX or A present: pass to SMTP mailbox verification.
  4. SMTP result: Valid, Invalid, or Risky (catch-all).
  5. Only Valid addresses go into live sending lists.

Frequently asked questions

Does an MX record mean an email address is valid?

No. An MX record shows the domain is configured to accept mail, but it says nothing about whether a particular mailbox exists on that server. Only an SMTP mailbox check or a send can confirm an individual address.

What does an NXDOMAIN response mean for an email?

NXDOMAIN means the domain does not exist in DNS, so mail sent to any address at that domain will fail. It is a hard fail and a reliable reason to remove the address from a list.

Can a domain receive email without an SPF record?

Yes. SPF controls which servers may send mail for a domain and has no bearing on receiving. Many domains that accept mail publish no SPF or DMARC record, so rejecting them for missing SPF removes good contacts.

What is a null MX record?

A null MX record uses preference 0 and the target '.' to declare that a domain accepts no mail, as defined in RFC 7505. Addresses at such domains should be treated as undeliverable.

What is a catch-all domain?

A catch-all domain accepts mail for any address at that domain, real or not. DNS passes these domains and SMTP probes cannot confirm a specific mailbox, so they are usually held as Risky rather than Valid.

Should I delete an address when DNS returns SERVFAIL or times out?

No. SERVFAIL and timeouts are usually temporary resolver or network problems. Mark these results as unknown and retry later, because deleting them throws away good contacts.

Is a DNS check enough for email list cleaning?

No. DNS is fast and cheap for removing whole dead domains, but it cannot detect individual bad mailboxes. Run DNS first, then a full mailbox verification on the remaining addresses.

What if a domain has only an A record and no MX?

RFC 5321 lets senders fall back to the A record when no MX exists, so the domain can be attempted. However, an A record on a parked website is a weak signal, so treat such domains with caution.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.