# MX Lookup Explained: Check Your MX Records Free

> Run a free MX lookup on any domain, see which provider receives its email, and fix missing, old or wrong MX records after a move to Google or Microsoft.

Page: https://adengage.ae/growth-gps/guides/mx-lookup-explained.html
Published: 2026-11-22
Updated: 2026-11-22
Tool on this page: email checker (https://adengage.ae/growth-gps/email-checker.html)

## MX lookup explained: see who receives your email, and fix the records that lose it

Type any domain into the free checker below to list its MX records and mail provider, then use this guide to read them and fix what is wrong.

## What is an MX lookup?

An MX lookup asks DNS which mail servers receive email for a domain, and in what order. Each MX record names a server and a preference number, and lower numbers are tried first. If a domain has no MX records, senders fall back to its address record, and a domain that takes no mail at all can say so with a null MX.

## How to run an MX lookup and fix what you find

1. **Look up the domain** Type the domain, or any address on it, into the checker above. It lists the MX records and names the mail provider when it recognises it.
2. **Read the order** Each record carries a preference number. Senders try the lowest number first, and records with equal numbers share the mail at random.
3. **Confirm the provider is the current one** After a move to Google Workspace or Microsoft 365, MX should point to the new provider. Old records left behind can deliver mail to a system nobody checks.
4. **Set the new records** Google Workspace uses one record, `smtp.google.com`, with priority 1. Microsoft 365 shows the exact MX value for your domain in the admin center during domain setup.
5. **Deal with the old ones** Google says to remove any other MX records. Microsoft says to remove records for the previous provider, or set them to a lower priority than the Microsoft 365 record.
6. **Point MX at names, never IP addresses** An MX record must name a host that has an address record. RFC 5321 does not allow an IP address as the MX target.
7. **Allow time to spread** Google says new MX records can take up to 72 hours to be recognised. Keep the old mailbox open until mail arrives at the new one.
8. **Check again** Run your next lookup on the full email checker page, and check SPF, DKIM and DMARC for the new provider at the same time.

## Reading MX lookup results

| What you see | What it means | What to do |
|---|---|---|
| One record, smtp.google.com, priority 1 | Google Workspace receives your mail | Nothing, if you use Google Workspace |
| Records that start with aspmx | Older Google Workspace values, still supported | Leave them if mail works; Google says you do not need to change them |
| A host on protection.outlook.com | Microsoft 365 receives your mail, and the checker names it | Confirm it matches the value your Microsoft 365 admin center shows |
| Records for two different providers | Mail may split between an old and a new system | Remove the old provider's records |
| No MX records | Senders fall back to the domain's address record, usually the website host | Add your provider's MX records, or a null MX if the domain takes no mail |
| One record: preference 0 and a single dot | A null MX: the domain accepts no mail | Right for domains that never receive email, wrong for your main domain |

Values from Google Workspace Admin Help, Microsoft Learn and RFC 7505.

## Priority, fallback and null MX in plain words

**Priority.** RFC 5321 says senders must sort MX records by preference, with lower numbers more preferred, and choose at random among records with the same number. So a record numbered 1 is tried before anything numbered 5 or 10.

**Fallback.** When a domain has no MX records at all, RFC 5321 treats its address record as an implicit MX with preference 0. For most businesses that address is the website host, which holds no mailbox for you, so mail sent there is likely to fail. If MX records exist but none can be used, that is an error, not a reason to fall back.

**Null MX.** RFC 7505 lets a domain that accepts no mail publish a single MX record with preference 0 and a target of a single dot. Senders see it on the first attempt and stop, instead of queueing and retrying. It suits parked and redirect-only domains.

## MX checklist after a mail move

- [ ] MX records point only to your current provider
- [ ] Google Workspace: smtp.google.com at priority 1, or the older aspmx values if mail already works
- [ ] Microsoft 365: the MX value your admin center shows for the domain
- [ ] Old provider records removed, or set to a lower priority than the new ones as Microsoft describes
- [ ] Every MX target is a host name with an address record, never an IP address
- [ ] SPF updated for the new provider, with the old provider taken out
- [ ] DKIM turned on with the new provider
- [ ] The DMARC reporting address sits on a domain with working MX records
- [ ] Parked domains carry a null MX if they should never receive mail
- [ ] Test messages from a Gmail and an Outlook address arrive in the new mailbox

## Who uses an MX lookup

- **IT leads** Confirm that a move to Google Workspace or Microsoft 365 is complete, with no old records left to split mail.
- **Sales teams** Before sending a big proposal to a new contact, check that their domain can receive email at all.
- **Developers** Make sure the DMARC reporting address and system alert addresses sit on domains that can receive mail.
- **Business owners** Find out which provider runs your email when the person who set it up has moved on.
- **Freelancers** Check a client's domain before you set up forwarding or a shared mailbox for them.
- **Managed IT providers** Spot domains whose MX still points to a provider the client has cancelled.

## Worked examples

### A half-finished move to Microsoft 365

Suppose the lookup lists the Microsoft 365 record and two records for your old host, all with the same preference. Senders choose at random among equal numbers, so some mail lands in the old system. Remove the old records, or set them to a lower priority than the Microsoft 365 record.

### A domain that cannot receive email

Suppose the checker shows the banner that this domain cannot receive email. It found no MX records, and it warns that replies to your quotes will bounce. If you use email on this domain, add your provider's MX records today.

### Two servers at the same number, on purpose

Suppose your mail host publishes two MX records, both at preference 10, on different servers. That is a deliberate setup: senders spread mail between them at random, and the other server is still there if one cannot be reached.

## What changes in 2027 for MX records

### Now

- Google Workspace has used a single MX record, smtp.google.com at priority 1, for domains set up since 2023, and still supports the older aspmx values.
- RFC 7505 gives domains that take no mail a clean way to say so, the null MX, which saves senders from queueing and retrying.
- Microsoft 365 domain setup shows the records to add for your domain, MX among them, so you can check them before you authorise the change.

### Next

- AdEngage UAE expects mail moves to stay common in 2027 as businesses change providers and merge brands, so make an MX lookup the last step of every move.
- Pair every MX check with SPF, DKIM and DMARC: receiving and sending are set up separately, and a move can fix one while it breaks the other.
- Write down who controls your DNS and where it is hosted, so the next change does not wait on a password nobody has.

## Sources

- [RFC Editor: RFC 5321, Simple Mail Transfer Protocol](https://www.rfc-editor.org/rfc/rfc5321.html)
- [RFC Editor: RFC 7505, A "Null MX" No Service Resource Record](https://www.rfc-editor.org/rfc/rfc7505.html)
- [Google Workspace Admin Help: Set up MX records for Google Workspace](https://knowledge.workspace.google.com/admin/domains/set-up-mx-records-for-google-workspace)
- [Microsoft Learn: Connect your domain by adding DNS records](https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider)

## Questions people ask

### What is an MX record?

A DNS record that names a server receiving email for a domain, together with a preference number. A domain can have several, and senders try the lowest number first.

### How do I do an MX lookup?

Type the domain, or an email address on it, into the checker above. It reads public DNS, lists the MX records in order and names the mail provider when it recognises it.

### What does MX priority mean?

It is the preference number on each record. Lower numbers are tried first, and records with the same number share the mail at random, as RFC 5321 sets out.

### What are the MX records for Google Workspace?

One record: smtp.google.com with priority 1. Domains set up before 2023 may use older values that start with aspmx, which Google still supports, so leave them if mail works.

### What is the MX record for Microsoft 365?

Microsoft 365 shows the exact MX value for your domain in the admin center when you add the domain. Use that value, then remove the previous provider's records or set them to a lower priority.

### What happens if a domain has no MX record?

Senders treat the domain's address record as an implicit MX. For most businesses that is the website host, which has no mailbox, so mail is unlikely to arrive. The checker warns that the domain cannot receive email.

### What is a null MX record?

A single MX record with preference 0 and a target of a single dot, defined in RFC 7505. It tells senders the domain accepts no mail, so they stop at once instead of retrying.

### Can an MX record point to an IP address?

No. RFC 5321 says the MX data must be a domain name that resolves to an address record. Point MX at a host name, and give that host an A or AAAA record.

### How long do MX changes take to work?

Google says new MX records can take up to 72 hours to be recognised. Keep the old mailbox working until test mail arrives at the new one.

### Is the MX record checker free?

Yes. It is part of the email checker, free with no login, and answers in seconds, with up to 30 email checks a day for each visitor.

By the AdEngage UAE growth team. Reviewed by Pancham SN Bannerrjee, Founder and CEO. Published 22 November 2026. Last updated 22 November 2026.

6th Floor, Meydan Grandstand, Meydan Road, Nad Al Sheba 1, Dubai. uae@adengage.ae. WhatsApp +971 54 566 6253.
