Check a domain's mail exchanger records and see which hosts receive mail for that domain. This is a DNS record check, not a full email-deliverability audit.
MX records name the servers that accept mail for a domain and the order to try them: the lowest priority number goes first. This lookup lists them with their priorities. A domain with no MX record falls back to its own A or AAAA address, and a single MX of "." (null MX) means the domain accepts no mail.
What the results mean
MX records list mail servers and priorities. Lower priority numbers are tried first. Missing MX records may mean the domain does not receive mail or relies on a provider-specific setup.
How to use this tool
Enter a domain name.
Review each mail exchanger host and priority.
Check SPF and DMARC next if you are reviewing email authentication.
FAQ
Can MX records be hidden?
Public mail routing generally needs public MX records, though some domains intentionally receive no mail.
Why do multiple MX records exist?
Multiple records can provide priority ordering and fallback mail delivery paths.
Does this check DKIM?
No. DKIM records vary by selector. Use DNS Lookup if you know the selector.
How these reports are structured, and how to share them safely
SummaryStart with a plain-language status for the public target.Top issuesPrioritize the few findings that need attention first.What passedShow expected public signals without turning them into a certification.What needs reviewSeparate limited, unavailable, and review-worthy signals.Why it mattersExplain the business, delivery, crawl, or implementation impact.Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.What this tool cannot checkThis does not send mail, inspect private mailboxes, guarantee inbox placement, or certify sender reputation everywhere.Client-safe copyClient-safe copy should keep authentication findings and fixes while removing email local-parts, raw TXT payloads, raw sender IP details, and private mailbox context.Monitoring beta (optional)Optional monitoring beta can compare MX, SPF, DKIM selector checks, DMARC policy, PTR/rDNS, and selected blacklist signals for approved domains.
Client-safe report
Share findings without leaking raw technical material
Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.
About this checkWhat it checks, what it cannot, and how to read it
Check my email domain
What this checks
Public mail-domain records and pasted email-header signals such as MX, SPF, DMARC, DKIM selector context, and sender-route clues.
Limits
What this cannot check
It cannot guarantee inbox placement, inspect private mailboxes, or certify sender reputation everywhere.
Read results
How to use the output
Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.
Checks public MX records and shows mail exchanger priority and hostnames.
How to use
Enter the domain that appears after the @, not the hostname of a mail server.
Read priorities in order: the lowest number is tried first.
Check that each MX hostname resolves to an address before assuming mail can be delivered.
What the result means
MX records name the hosts that accept mail for a domain and the order a sender should try them. The lookup runs through /api/dns-lookup, so the result tells you where mail is routed. It says nothing about whether those hosts accept, filter or deliver a particular message.
Limitations
A domain with no MX record can still receive mail at its A record, so an empty answer is not proof that nothing is configured.
Answers come from one DNS-over-HTTPS resolver and are cached, so a recent change may not be visible yet.
Correct MX records imply nothing about SPF, DKIM, DMARC or whether the mailbox behind them exists.
More questions
Does an MX record prove email is configured correctly?
No. MX records show mail routing targets, but mailbox, SPF, DKIM, DMARC, and provider settings also matter.
What does MX Lookup do?
MX Lookup checks public MX records and shows mail exchanger priority and hostnames. Results are review signals with stated limits.
How should I use MX Lookup results?
Use the result to decide what to review next, make one change at a time, and retest in the same browser, network, domain, or provider context when possible.
What does MX Lookup not prove?
It does not prove that the domain receives mail correctly or that messages reach the inbox: MX records only name where mail should be delivered, and missing records can also mean a provider-specific setup.