MX Record Lookup

What is an MX record?

An MX (Mail Exchange) record tells the world which servers accept inbound email for your domain. Each record carries a priority — lower numbers are tried first, with the rest acting as fallbacks.

Reading priority

Standard configurations use priorities like 1, 5, 10, 20. The active server has the lowest number; identical priorities are load-balanced. Most managed providers (Google, Microsoft) ship four to five MX hosts.

Why this matters for senders

When you send cold email, recipient MX detection drives ESP-matched routing — sending Google-to-Google and Microsoft-to-Microsoft when possible significantly improves inbox placement.

MX record FAQs

How many MX records should a domain have?

Managed providers publish between two and five hosts so mail keeps flowing when one server is unreachable. A single MX record works, but it leaves no fallback path: if that host is down, senders retry for a while and then bounce the message back.

Do MX records affect whether my cold email lands?

Indirectly, and in two ways. Your own MX setup determines whether replies and bounce notifications reach you, which is how you measure a campaign honestly. The recipient's MX tells you which ecosystem you are sending into, so you can match Google mailboxes to Google recipients and Microsoft to Microsoft.

Why does my MX lookup show a different provider than expected?

Usually a stale record from a previous provider, a security gateway sitting in front of the real mail server, or DNS changes that have not finished propagating. Wait for the TTL to expire, then check again before troubleshooting anything else.

Can I send email without MX records?

Technically yes, but you should not. Receivers treat a sending domain with no inbound mail path as a throwaway, and you never see replies or bounces. Every domain you send from should accept mail as well.