Mx Lookup Online — Free Mx Lookup Tool

CodexFuse Team · 2026-11-02T07:27:16.921Z · 10 min read min read

Find where your domain's email is routed, read MX records correctly, and fix missing-mail problems before they cost you orders.

An MX lookup shows which mail servers should receive email for a domain. When a customer emails your business, the sending server asks your domain's DNS for its mail exchanger (MX) records, then delivers to the server listed there. If those records point to the wrong place, mail can vanish, arrive hours late, or land in an inbox nobody checks.

That is why a quick check matters before you blame a customer, a spam filter, or your inbox app. This guide explains what the results mean, how to run a check in under a minute, and what to fix first.

What Is an MX Lookup?

An MX lookup is a DNS check that lists the mail servers assigned to receive email for a domain, in the order senders should try them. Each result normally pairs a priority number with a mail server hostname, so a lower priority number means that server is tried first and higher numbers act as fallbacks.

Think of it as the postal address for your domain's email. Your website address tells browsers where to find your pages. Your MX records tell mail servers where to deliver messages. The two can live in different places, and changing one does not automatically fix the other. Problems start when a website moves, an email provider changes, or a DNS edit is copied incorrectly and nobody re-checks the mail route.

Why Do Emails Go Missing When MX Records Are Wrong?

Emails go missing when MX records are wrong because senders deliver to the server named in DNS, not to the inbox you happen to open. If DNS still names an old provider, the message goes to that old mailbox, even though you stopped checking it months ago.

Timing also confuses people. DNS changes spread gradually, so a fix may work for one sender and not another for a while. Re-check after propagation and ask the affected sender to retry, rather than changing records again in a panic.

Worked Example: A Bakery That Lost Its Order Emails

This is a fictional scenario, created to show the steps clearly. The domain and mail values below are illustrative, not a real result.

Riverside Bakes, a small bakery, moved its website to a new host on a Friday. On Monday, wholesale order emails had stopped, while personal messages to a different address still arrived. The website worked perfectly, so the team assumed the email app was at fault.

A check on riverside-bakes.example told a different story. Its mail records still pointed to the old host's mail service, which the bakery no longer used. New orders were landing in an old mailbox nobody monitored.

Once the route was visible, the fix was straightforward. The team updated the records to the bakery's current email provider, removed the leftover old entry, and asked two wholesale customers to resend their orders. Both arrived in the correct inbox. The bakery did not need a new email app. It needed to see where its mail was going, fix one routing record, and confirm the new route with a second check.

How Do You Run an MX Lookup on CodexFuse?

To run this check on CodexFuse, open the free tool on CodexFuse, enter the domain hostname, and view its mail records. The tool is free and unlimited, and you need an account to use it, so sign in first if prompted.

1. Enter the domain, not an email address. Type the hostname, such as riverside-bakes.example, without a name or an @ symbol.
2. Run the check and read the records. Review each mail server and its priority, and note anything that does not match your current provider.
3. Compare the result with your email setup. If your provider gave you specific mail servers, the result should match them. Any extra or missing entry is your lead.
4. Fix DNS only where you manage the domain. Update records at your DNS provider, keep a note of the old values, and run the check again after the change spreads.

This takes less than a minute, and it answers a question guessing cannot: is the problem in your inbox, or in the route to it? For a related network check, see this domain-to-IP guide when you also need to confirm which server a domain resolves to.

How Do You Read MX Results Without Guessing?

You read MX results by checking three things in order: the server names match your current provider, the priority order makes sense, and no stale provider remains in the list. A result passing all three is usually healthy, even if the server names look unfamiliar at first.

• Priority means order, not quality. A lower number is tried first. A server with priority 10 is tried before one with priority 20, and the higher number is a fallback, not a spare to ignore.
• Server names must match exactly. One wrong letter creates a different destination. Copy expected values from your provider's setup guide and compare them side by side.
• Extra entries are a warning sign. Leftover records from a previous provider can split or misdirect mail. Identify every entry's owner, and remove only what you can explain.
• No result is a result. If no records appear, senders may fail entirely. Treat a blank result as an urgent setup gap, not proof that email is fine.

After the check, note the domain, the date, and the listed servers. That short note turns a future "email stopped working" report into a two-minute comparison instead of a fresh investigation.

What Should You Fix First When the Results Look Wrong?

When results look wrong, fix the mismatch with your current email provider first, before changing spam settings, filters, or inbox apps — start there. Most missing-mail cases are routing cases, and routing is decided in DNS, not in your mail app.

1. Confirm your current provider. Check your admin panel and write down the mail servers your provider actually expects.
2. Remove only the stale entries. Delete records for providers you no longer use, and keep the current provider's full set intact.
3. Re-check after propagation. Run the lookup tool again and confirm the new result matches your provider before telling customers the issue is closed.

If records are correct and mail still fails, move to the next layer. A deliverability check can reveal authentication or reputation problems that routing alone cannot show, as explained in this email deliverability guide. Also confirm addresses with an email validator before assuming the route is the only fault.

What This Check Cannot Tell You

A clean result does not guarantee every message will arrive, be trusted, or be read. It only proves the delivery address in DNS. The rest of the journey needs its own checks.

• It does not check spam authentication. SPF, DKIM, and DMARC affect whether receivers trust your mail, and they live in separate DNS records.
• It does not test the mailbox itself. A correct route can still lead to a full, suspended, or misconfigured mailbox.
• It does not measure sender reputation. Past spam complaints can hurt delivery even with perfect routing.
• It does not prove a server is online now. DNS can name a server that is temporarily down, so a failed delivery needs a retry and a server-side check.

Use the check for what it is: the fastest way to rule routing in or out. If routing is correct, spend your next hour on authentication and mailbox health, not on editing records repeatedly. A domain hosting check can also help when you are unsure which provider controls the domain.

Move From a One-Off Check to Managed Business Email on CodexFuse

A one-off check is useful, but it should not become a weekly chore. If your business depends on order confirmations, client replies, quotes, and invoices, email routing deserves a managed setup where moves, DNS changes, and provider switches are handled as one job.

On CodexFuse, the workflow is concrete. First, run the check and record your current route. Second, move your business email to CodexFuse as a managed service, with records set to the correct managed servers as part of the migration. Third, re-check the route after the change and confirm test messages arrive in the right inbox. Credits cover the managed service on a pay-as-you-go basis, with no subscription lock-in.

Do not wait for another lost order to prove the point. Run an MX lookup on your main business domain today, fix any stale entry you find, and if email keeps competing with hosting, DNS, and security chores for your attention, move it to CodexFuse and let one managed platform carry the whole stack.

Frequently Asked Questions

What is an MX lookup?

An MX lookup is a DNS check listing the mail servers set to receive email for a domain, with a priority for each server. Senders use that list to decide where to deliver a message.

Do I need the full email address to run a check?

No. You need the domain hostname only, without a username or @ symbol. The tool then returns the mail records for that domain.

Why does my website work but my email does not?

Web and email use different DNS records. Your website can load correctly while mail records still point to an old or wrong provider, so check the mail route separately.

How often should I run an MX lookup?

Run one after any hosting move, domain transfer, email migration, or DNS cleanup, and whenever mail suddenly stops or splits between inboxes.

Can a wrong record cause mail to bounce?

Yes. A missing record, a misspelled server name, or a record pointing to a closed service can cause bounces or silent delivery to an unmonitored mailbox.

Is the CodexFuse tool free?

Yes. The tool page states it is free and unlimited. You need an account to use it, so sign in or create a free account if prompted, then enter a hostname.