Enter your domain to see its MX records: the mail servers that receive email sent to your address, and which email provider they belong to.
Free, no sign-up. Checks SPF, DKIM, DMARC, mail servers and blacklists in one go.
What MX records do
When someone sends an email to [email protected], their mail system looks up your domain’s MX (mail exchanger) records to find out where to deliver it. Each record names a mail server and a priority number. Lower numbers are tried first; the others are backups.
A business on Google Workspace, for example, has MX records pointing to Google’s servers. If those records are missing or wrong, incoming email bounces or vanishes, even though everything looks fine from your side.
Reading your result
| What you see | What it means |
|---|---|
| Mail servers found (with provider) | Your MX records work. The provider name shows who handles your incoming email. |
| No mail servers found | Your domain can’t receive email. If you use an address at this domain, mail sent to it isn’t arriving. |
| Mail server records have errors | A record points to a name that doesn’t exist, or to a bare IP address, which isn’t allowed. Some email may fail. |
| Domain does not accept email (null MX) | The domain has deliberately said it never receives email. That’s correct for domains you don’t use for mail. |
MX records by email provider
| Email provider | What your MX records usually point to |
|---|---|
| Google Workspace | smtp.google.com (newer setups) or aspmx.l.google.com and its backups |
| Microsoft 365 | Usually yourcompany-com.mail.protection.outlook.com (some newer setups use an address ending in mx.microsoft) |
| Zoho Mail | mx.zoho.com, mx2.zoho.com, mx3.zoho.com (or your region’s version) |
| GoDaddy email | GoDaddy’s secureserver.net servers |
Always copy the exact values from your email provider’s setup screen. Microsoft’s, in particular, include your own domain name.
Common MX problems
- Leftover records from an old provider. After switching from GoDaddy to Google, for example, an old MX record can quietly send some mail to an account nobody checks. Your MX records should all belong to one provider.
- Changing web hosts and losing email. Some website builders and hosts replace your DNS settings when you connect a domain. If email stops arriving right after a website change, check your MX records first.
- An IP address instead of a name. MX records must point to a server name, not a number.
MX records and outgoing email
MX records only control mail coming in. Whether your outgoing email reaches inboxes depends on SPF, DKIM and DMARC, which the free check above tests at the same time. See our SPF checker, DKIM checker and DMARC checker for what each one means.
Common questions
How long do MX changes take?
Usually within an hour, though some mail systems cache the old records for up to 48 hours. Keep your old mailbox working for a couple of days after switching.
Does the MX record affect whether my email goes to spam?
Not directly. But a domain with no working MX records can look suspicious to receiving mail systems, and replies to your messages will bounce.
I never use this domain for email. What should the MX record be?
The cleanest choice is a “null MX” record (priority 0 pointing to .), which says the domain never receives email. With no MX record at all, some mail systems try to deliver to your website’s server instead. Pair the null MX with DMARC set to reject so nobody can send email in its name.
Records break without anyone noticing
A website move, a new email tool or a DNS change can quietly undo this setup. MailWatchman checks your domain every day and emails you the moment something changes, with the fix. Plans start at $6 a month.