Article
Best Free MX Record Lookup Tools in 2026 (Compared)
By Unlimited Verifier Team ·

Summary
For a single domain, Google Admin Toolbox Dig is a free, account-free way to read MX records, while dig suits scripts and nslookup or Resolve-DnsName work on Windows. For whole email lists, a bulk verifier that runs MX checks across every address is more practical. An MX record shows a domain can receive mail, not that a specific mailbox exists.The best free MX record lookup for a single domain is Google Admin Toolbox Dig, with the open-source dig command for scripts. For a whole email list, Unlimited Verifier is our top pick because it applies MX checks to every address in a file.
This guide is for list owners, agencies and SaaS teams who need to confirm that domains can receive mail, whether they're checking one domain or cleaning 50,000 addresses. An MX lookup is a useful first layer of list hygiene, but it is not a verdict on any individual mailbox. If you're new to the category, start with our free and cheap email verifiers overview. This page focuses on MX lookups specifically.
Quick answer
- Best overall for lists: Unlimited Verifier. It runs MX checks inside bulk verification, sorts results into Valid, Risky or Invalid, and offers unlimited standard verification on the Free plan.
- Best for reading raw records: Google Admin Toolbox Dig. It's free, needs no account, and shows MX answers with preference values.
- Best for scripts:
dig, which can loop through a domain list from a terminal. - Best no-install option on Windows:
nslookup, or PowerShell'sResolve-DnsNamefor structured output. - Core rule: an MX record proves a domain is set up to receive mail. It does not prove that a specific mailbox exists.
Which free MX record lookup tool is best for each job?
The right tool depends on whether you need raw DNS answers, a diagnosis for one domain, or a verdict on every address in a list. Start with the picks below, then compare the full table.
Quick picks
- Best for list-level MX checks: Unlimited Verifier.
- Best for an authoritative-style single-domain answer: Google Admin Toolbox Dig.
- Best for batch and scripted lookups: dig.
- Best for a no-install check on Windows: nslookup.
- Best for structured Windows output: Resolve-DnsName.
- Best for troubleshooting a bouncing domain: MXToolbox.
- Best for checking whether a DNS change has spread: DNSChecker.
| Tool | Starting price | Free tier | Catch-all handling | Best for |
|---|---|---|---|---|
| Unlimited Verifier | $0 (Free); Pro $29/mo or $25/mo billed annually | Yes: 25 lists/mo of up to 150 emails each, 750 deep verifications/mo; results kept 24 hours | Detects catch-all domains and flags them | MX and mailbox checks across whole lists |
| Google Admin Toolbox Dig | Free | Free, no account | Not applicable (DNS lookup only) | Reading one domain's MX answer |
| dig (BIND utilities) | Free, open source | Free | Not applicable | Scripted and batch lookups |
| nslookup | Built into most Windows machines | Free | Not applicable | Quick Windows spot checks |
| Resolve-DnsName (PowerShell) | Built into Windows | Free | Not applicable | Structured Windows output |
| MXToolbox | Free tier plus paid plans | Varies (usage limits; check current terms) | Not applicable | Diagnosing mail-server problems |
| DNSChecker | Free web tool | Varies (check current terms) | Not applicable | Multi-location propagation checks |
Bottom line: no single free tool does everything, so match the tool to whether your job is one domain or a full list.
How we compared (and limitations)
We judged each option on six criteria that matter for MX work. This comparison is based on public documentation and each vendor's published information:
- Question answered. Does it show raw DNS records, a diagnosis, or a deliverability verdict per address?
- Volume. Can it take a list file, or only one domain at a time?
- Free tier clarity. Are the limits published and easy to find?
- Output. Can you read preference values and TTLs, and export the results?
- Diagnostic depth. Does it add blacklist or SMTP context?
- Retention and usage limits. How long are results kept, and what limits apply to free use?
Limitations. We did not run head-to-head tests of response times, accuracy or propagation speed, so nothing here is based on our own benchmarks. Free-tier limits change, so confirm them before you rely on them. DNS answers depend on which resolver responds and what it has cached, and no DNS lookup can prove that a mailbox exists. For full verifiers with free allowances, see top email verifiers with free monthly credits and 5 email verifiers with the biggest free tier. We list prices only where they are publicly stated. For how cost models differ, see email verification pricing.
Bottom line: treat any DNS tool as a view of the public record at a moment in time, not a verdict on a mailbox.
The 7 best free MX record lookup tools, reviewed
1. Unlimited Verifier (best for MX checks across a whole list)
Unlimited Verifier is a bulk email verification tool, not a DNS explorer. You upload a CSV or Excel file of up to 10MB, the email column is detected automatically, and every address is checked for syntax, domain, MX records and the SMTP mailbox. Each address then lands in Valid, Risky or Invalid. The MX step tells you whether a domain runs mail servers at all. The mailbox step tests the specific address.
Catch-all domains are detected, so you can segment those addresses rather than treating them as confirmed. Disposable and role-based addresses are flagged too. The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent measurement.
Key features
- Syntax, domain, MX and SMTP mailbox checks in one run
- Catch-all email verification detection
- Valid / Risky / Invalid sorting, exportable as CSV, Excel or JSON
- Deep verifications for addresses that need a closer look: 750 a month on Free, 25,000 on Pro
- REST API with keys on Pro, for single checks and batches of up to 10,000 emails per request
- A free single-email checker and a free domain blacklist checker
- An open-source verification engine on GitHub
Pros
- Turns MX checking from a domain-by-domain chore into one list-level step
- Standard verification is unlimited on Free and Pro, so re-checking a list adds no per-email fee
- The open-source engine lets technical reviewers see how the checks are built
- Valid / Risky / Invalid maps directly to send, segment and suppress decisions
Cons
- It returns verdicts, not raw records. You won't see MX host names and preference values the way dig shows them.
- Free results are kept for 24 hours, so exports must be downloaded the same day.
- The Free plan has no API access, and each list is capped at 150 emails.
- No native ESP, CRM or Zapier integrations. Workflows are export, verify, re-import, or API calls.
Best for: list owners who need MX checks on thousands of addresses without writing scripts.
Where it falls short: explaining why one domain's mail is misrouted. Use a DNS tool for that.
Pricing: Free ($0) includes 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Pro is $29/month, or $25/month billed annually, with unlimited lists of up to 25,000 emails each and 25,000 deep verifications a month.
Worked example. Your list has 4,200 rows.
- On Free: 4,200 ÷ 150 = 28 files. Free allows 25 lists a month, so month one covers 25 × 150 = 3,750 addresses. The remaining 3 files (450 addresses) run the following month. Cost: $0.
- On Pro: the same 4,200 rows fit in a single file, well under the 25,000 cap. At $25/month billed annually, that's $300 a year.
Tip: Remove exact duplicate addresses before upload, but don't dedupe by domain. Every address needs its own verdict. Use the domain count for planning and spot checks, as the tutorial below shows.
Bottom line: the strongest choice here for running MX checks across a whole file and getting a per-address decision.
2. Google Admin Toolbox Dig (best for one domain's authoritative-style answer)
Google's Admin Toolbox includes a Dig tool, a web front end for the same kind of DNS query the dig command makes. You enter a domain, select MX, and read the answer section, which lists each mail exchanger with its preference value and TTL. No account is needed.
Key features
- MX and other record types
- Full answer section, including preference values and TTLs
- Browser-based, with no sign-up
Pros
- Free, with no account, for single-domain checks
- Output resembles a standard DNS answer, so you can compare it line by line with what your DNS host shows
- Useful as a neutral reference when someone insists "our records are fine"
Cons
- One domain per query, with no file upload and no export of multiple results
- Answers reflect the resolver Google uses at that moment, including whatever it has cached
- No mailbox check and no catch-all detection
Best for: confirming what public DNS says about one domain before you blame a bounce on it.
Where it falls short: any list, or any job that needs a per-address verdict.
Pricing: free.
Tip: If Dig returns no MX records, check the A record too. RFC 5321 describes implicit MX handling: a domain with no MX records can still receive mail through its address record. "No MX" alone doesn't prove the domain is undeliverable.
Bottom line: the cleanest single-domain view, with nothing for lists.
3. dig (best for scripted and batch MX lookups)
dig is the DNS lookup utility from the BIND project. It's included in the DNS utilities on most Linux distributions and ships with macOS. It returns raw answer sections for any record type and gives you control over each query.
Useful commands:
dig MX example.com +noall +answerprints only the answer section.dig +short MX example.comprints preference and host name, one per line.dig @8.8.8.8 MX example.comqueries a specific public resolver.while read d; do dig +short MX "$d"; done < domains.txtruns a lookup for each domain in a file.
Key features
- Raw DNS answers for any record type
- Resolver selection with
@ - Output you can pipe into other tools
Pros
- Free and open source
- Exact answers you can parse, filter and log
- Works well on domain lists you've already extracted
Cons
- Needs a terminal, and Windows doesn't include it by default
+shorthides the status line, so a timeout can look the same as "no answer." When results matter, check the full output forstatus: NOERRORorNXDOMAIN.- A shell loop runs one domain at a time, so long lists take a while, and you write your own timeout handling
Best for: technical users who want domain-level MX answers across a deduplicated domain list.
Where it falls short: address-level decisions.
Pricing: free.
Tip: To list unique mail hosts for a domain, run dig +short MX example.com | awk '{print $2}' | sort -u. A null MX shows as preference 0 with a host of "." Flag it. On Linux and macOS, host -t MX example.com gives a plainer reading for a single domain, and it's the same data, so use it when you just want to read the answer. For a self-hosted verifier rather than a DNS tool, see open source email verification tools.
Bottom line: the most flexible option for scripts, and the one that demands the most effort.
4. nslookup (best for a no-install check on Windows)
nslookup ships with Windows and most other operating systems. From a command prompt, nslookup -type=MX example.com returns the mail exchangers and their preference values. Interactive mode works too: run nslookup, type set type=MX, then enter the domain. Microsoft documents the command in its Windows commands reference.
Key features
- Built into Windows, with no install
- One-line and interactive modes
- Accepts a resolver argument, such as 8.8.8.8
Pros
- Available immediately on most Windows machines
- Quick for one-off spot checks
- Documented by Microsoft
Cons
- Default output is terse and harder to scan than dig's
- Uses your local resolver unless you specify another, which may serve cached answers
- Output is plain text, so bulk work means scripting around it
Best for: a quick check on a Windows machine when you don't want to install anything.
Where it falls short: auditing a list or explaining results to a client.
Pricing: free, built in.
Tip: Run the lookup twice, once with your default resolver and once with nslookup -type=MX example.com 8.8.8.8. If the answers differ, the record probably changed recently and your local resolver is still serving the old one.
Bottom line: the fastest free check on Windows, with the least structured output.
5. Resolve-DnsName (best for structured Windows output)
Resolve-DnsName is a PowerShell cmdlet in the DnsClient module and the structured alternative to nslookup. Resolve-DnsName -Name example.com -Type MX returns objects with properties such as NameExchange and Preference, so you can sort, filter and export results without parsing text.
Key features
- Returns objects rather than text
- Accepts a server parameter, such as
-Server 8.8.8.8 - Works in PowerShell on Windows with no install
Pros
- Structured output exports to CSV far more easily than nslookup's text
- Sorting by Preference is a single pipeline step
- Built into Windows, so no third-party tool is needed
Cons
- Windows-only, so Linux and macOS users need dig or host
- A domain with no records typically raises an error rather than returning an empty result, so scripts need error handling
- It handles one domain per command, and list work needs a loop you write yourself
Best for: Windows administrators who want MX answers they can pipe into a report.
Where it falls short: a verdict on each address, or any list-level decision.
Pricing: free, built in.
Tip: To check a CSV of domains, try: Import-Csv domains.csv | ForEach-Object { try { Resolve-DnsName -Name $_.domain -Type MX -ErrorAction Stop } catch { "$($_.domain): $($_.Exception.Message)" } }. The snippet assumes a column named domain. Logging failures this way keeps a missing record from disappearing silently.
Bottom line: the best no-install option on Windows when you need output you can reuse.
6. MXToolbox (best for diagnosing a domain that bounces)
MXToolbox is a web toolkit whose MX lookup sits alongside checks for DNS blacklists, SMTP responses and other mail-related records. Its strength is diagnosis. When a domain's mail fails, you can check its MX hosts, blacklist status and SMTP responses in one place.
Key features
- MX lookup alongside mail-server checks
- Blacklist checks next to DNS results
- SMTP diagnostics for mail servers
Pros
- Several troubleshooting checks in one interface, which shortens root-cause work
- Blacklist results sit beside MX answers, so you can rule reputation in or out quickly
- Readable reports you can share with a team or client
Cons
- Free use has usage limits, so it isn't a bulk tool for lists (check current terms)
- Deeper monitoring and bulk features sit on paid plans
- Results are per domain or server, with no per-address verdict
Best for: troubleshooting one sending or receiving domain.
Where it falls short: cleaning a list of thousands of addresses.
Pricing: free tier plus paid plans. Limits change, so check the current terms.
Tip: If a domain's MX records look correct but mail is still rejected, check the blacklist result before you edit DNS. The problem is often sender reputation, not routing.
Bottom line: the best diagnostic pick here, and not a list-cleaning tool.
7. DNSChecker (best for confirming MX changes have spread)
DNSChecker queries DNS records from multiple locations at once. This matters because a record you just changed may look correct from your office while resolvers elsewhere still hold the old answer. Enter a domain, choose MX, and compare results across locations. WhatsMyDNS offers a similar multi-location view if you want a second opinion.
Key features
- MX and other record lookups
- Results from multiple locations
- Free web interface
Pros
- Shows propagation across locations, not just your own resolver
- Practical during mail-provider migrations, when old and new MX answers can coexist
- Easy for non-specialists to read during a change review
Cons
- One domain per query, with no list handling
- Shows DNS only, not mailbox status
- Results depend on each location's cache at query time, so "not yet propagated" can mean "still cached"
Best for: confirming that a mail-provider change has reached the public resolvers you care about.
Where it falls short: list audits or address-level decisions.
Pricing: free web tool. Check current terms.
Tip: Before a migration, look up the current MX TTL with dig. If the TTL is 3,600 seconds, resolvers that cached the old record can keep serving it for up to an hour after your change. TTL defaults vary by DNS host, so check yours. Use a second tool only when the first one's answers look inconsistent.
Bottom line: the right choice when the question is "has my DNS change reached the public resolvers yet?"
What does an MX lookup actually prove?
An MX record lists the servers that accept mail for a domain, each with a preference value. Under RFC 5321, lower values are tried first. A lookup therefore proves that a domain has mail routing configured. It does not prove that a particular mailbox exists, and it can't tell you whether a catch-all domain accepts everything. For a broader look at what free tools can and can't predict, see free tools to check if an email will bounce.
Five possible results need different handling:
| What the lookup returns | What it means | What to do |
|---|---|---|
| Normal MX hosts | The domain runs mail servers | Continue to the mailbox check |
| No MX, but an A record exists | Mail can still route through the A record (RFC 5321) | Don't mark invalid on MX alone |
| A single MX of "." (null MX) | The domain declares it accepts no mail (RFC 7505) | Treat as undeliverable |
| Domain doesn't exist (NXDOMAIN) | The domain isn't registered, or the address is misspelled | Treat as invalid, after checking spelling |
| Timeout or server failure | The lookup didn't finish, which proves nothing | Retry later; mark unknown |
The timeout row is where many homemade checks go wrong. A failed lookup is not evidence that a domain is dead.
Bottom line: a clean MX record is a necessary condition for delivery, not a sufficient one.
How do you check MX records for a whole email list?
This workflow uses Unlimited Verifier for the list and dig for spot checks. The effort is about the same for 500 rows or 50,000, because the upload process doesn't change. For a comparison of list cleaners, see best free email list cleaner online.
- Export your list as CSV. Include the email column and keep other columns in place so re-importing stays clean.
- Remove exact duplicate addresses, then count domains for planning. In a helper column, use
=MID(A2,FIND("@",A2)+1,255)(change A2 to your email cell), then count unique domains. Illustrative example: 20,000 addresses might contain around 1,800 unique domains, because a few large consumer providers account for many rows. Checking each domain by hand at an assumed 15 seconds apiece would take 1,800 × 15 = 27,000 seconds, about 7.5 hours. A list-level check avoids that. - Check size and split. Keep each file under 10MB. On Free, keep each file at 150 emails or fewer. On Pro, keep each file at 25,000 or fewer.
- Create a free account. Free works for small lists.
- Upload and verify your list. The email column is detected automatically.
- Optional: run deep verifications on Risky. Free includes 750 deep verifications a month, and Pro includes 25,000. Spend them on the Risky bucket, where extra checking is most likely to change a decision.
- Read the three buckets. Valid addresses are safe to send. Invalid addresses should be suppressed. Risky addresses, including catch-alls, should be segmented rather than sent to by default.
- Group Invalid by domain. Use a pivot table on the domain column. If one typo domain accounts for hundreds of Invalid rows, fix the signup form rather than suppressing those rows one by one.
- Download immediately. Free results are kept for 24 hours. Pro results are kept for 30 days.
- Spot-check surprising domains. Run
dig +short MX domainand read the status line. For one-off addresses, the free email checker works too. - Re-import. Update Valid as active, add Invalid to your suppression list, and tag Risky.
- Automate on Pro, if needed. Generate keys for the email verification API. Batches go up to 10,000 emails per request, within the 100,000-a-month API allowance. This is the core of email verification API and automation. For checks at signup, see real-time email validation.
Bottom line: dedupe exact duplicates only, verify the full list once, and download results before the retention window closes.
How should you choose an MX lookup tool?
Pick by job, not by brand. Match your situation to a tool below.
| Your situation | Pick | Why |
|---|---|---|
| Thousands of addresses to check | Unlimited Verifier | Whole-file MX and mailbox checks with Valid/Risky/Invalid output |
| Why does this one domain bounce? | MXToolbox | Blacklist and SMTP diagnostics in one place |
| Read the raw MX answer for one domain | Google Admin Toolbox Dig | Standard DNS-style answer |
| Scripted domain lists on Linux or macOS | dig | Shell loops and raw output |
| Windows, no install, reusable output | Resolve-DnsName | Objects you can sort and export |
| Windows, no install, quick check | nslookup | Built into most Windows machines |
| Confirm a DNS migration has spread | DNSChecker | Multi-location answers |
Some situations need a different kind of decision:
- Low volume, a few hundred addresses a month: start with best email verification tools for low volume senders, then read how to choose an email verifier before committing to a paid plan.
- Comparing another vendor's free allowance: Hunter's free plan limits show how one vendor structures its free tier.
- SaaS signup forms: email verification for ecommerce and SaaS covers signup-time checks, which need real-time validation rather than batch files.
- WordPress sites: if your forms run on WordPress, see best WordPress plugins for email validation.
- Paid tools and unknown results: check how each vendor bills unknown results before you buy. Best email verifiers that refund unknown results covers that.
For a general framework, the best email verification tools entry covers the categories these tools fall into.
Bottom line: use a DNS tool to understand one domain, and a list tool to decide on every address.
What mistakes do people make with MX lookups?
- Marking "no MX" as invalid. Check the A record first. RFC 5321 describes implicit MX handling, so a domain without MX records can still receive mail.
- Treating an MX pass as proof of a mailbox. Catch-all domains accept mail for any local part, so MX can't confirm that a specific address exists.
- Deduping the upload by domain. Each address needs its own verdict. Dedupe by domain only for spot checks and planning.
- Trusting one resolver after a DNS change. Compare two resolvers, and remember that cached answers persist until their TTL expires.
- Reading
+shortoutput as a complete answer. It hides status codes, so a timeout can look like a missing record. - Treating timeouts as dead domains. An incomplete lookup proves nothing. Mark it unknown and retry.
- Losing free results. Free exports disappear after 24 hours, so download the same day.
- Skipping consent. A valid DNS record doesn't make an address lawful to email. See the FTC's CAN-SPAM compliance guide and email verification compliance and hygiene. For routine cleaning, see email list maintenance best practices.
Bottom line: most MX errors come from reading a DNS answer as a deliverability verdict.
Verdict
For a single domain, Google Admin Toolbox Dig is the best free MX lookup for reading the record. dig is the choice for scripts, and nslookup or PowerShell's Resolve-DnsName covers Windows. For a whole email list, Unlimited Verifier is the most practical free-to-start option. It applies MX, domain, syntax and SMTP mailbox checks to every address and sorts the results into Valid, Risky or Invalid. Standard verification is unlimited on every plan, so weekly re-checks don't add per-email fees.
Its limits are real. It isn't a DNS explorer, Free results last 24 hours, and Free lists are capped at 150 emails. Plan your downloads and file splits around those numbers.
Bottom line: use a DNS tool to read the record, and a list verifier to act on it.
Which MX tool fits the job
| Job | Best free pick |
|---|---|
| Read one domain's MX answer | Google Admin Toolbox Dig |
| Loop through a domain list | dig in a script |
| Quick check on Windows | nslookup |
| Structured Windows output | Resolve-DnsName |
| Clean a whole email list | Bulk verifier (MX plus mailbox checks) |
Frequently asked questions
What is an MX record?
An MX record is a DNS entry that tells mail servers which hosts accept email for a domain. Each record has a preference value, and lower numbers are tried first. Its presence shows the domain is set up to receive mail, but it does not confirm any particular mailbox exists.
Is Google Admin Toolbox Dig free to use?
Yes. Google Admin Toolbox Dig is a free web tool that returns DNS answers, including MX records, without requiring an account. It is useful for reading one domain's mail server records and their preference values quickly.
How do I check MX records from the command line?
On macOS or Linux, run dig example.com MX +short to get the mail servers and preference values. On Windows, run nslookup -type=MX example.com. For structured output in PowerShell, use Resolve-DnsName -Name example.com -Type MX.
Can an MX lookup tell me if an email address is valid?
No. An MX lookup only confirms that a domain has mail servers configured. It cannot tell whether a specific address exists. Mailbox-level checks need a verifier that performs additional steps, and even those can be unreliable on catch-all domains.
What is the difference between an MX lookup and an SMTP check?
An MX lookup queries DNS for the mail servers of a domain. An SMTP check connects to one of those servers and asks whether a recipient is accepted. The MX lookup is faster and less intrusive, but the SMTP check gives a closer signal about a specific mailbox.
Why does my MX lookup show no records?
A domain with no MX records usually cannot receive mail, though some domains fall back to an A record. Check for typos, confirm the DNS zone is published, and remember that DNS changes can take time to propagate across resolvers.
How do I check many domains at once for MX records?
Use a script with dig or Resolve-DnsName that loops through a text file of domains, or use a bulk verifier that runs MX checks across an uploaded list. Scripts give raw data, while bulk tools sort results into categories for list cleaning.
What does a catch-all domain mean for MX checks?
A catch-all domain accepts mail for any address, so a valid MX record and an accepting server do not prove a mailbox exists. Verifiers flag catch-all domains so list owners can treat those addresses as uncertain rather than confirmed.
Do I need an account to use free MX lookup tools?
Most DNS lookup tools, including Google Admin Toolbox Dig and command-line utilities, need no account. Bulk verification platforms often require sign-up to upload lists, and their free allowances are subject to each vendor's current terms.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.