What does an MX lookup show?

It shows the DNS mail exchanger records that tell mail servers where to deliver messages for a domain.

Does an MX record prove email is configured correctly?

No. MX records show mail routing targets, but SPF, DKIM, DMARC, mailbox, and provider settings also matter.

What data source does this use?

MyIPScan queries a free DNS over HTTPS resolver through a server-side route with caching and rate limits.

Email Security Tool

MX Lookup

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.

Check MX records

Enter a domain to check MX records.

Technical response details (optional)

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.

B2B diagnostic report model

Email domain diagnostics

Email checks connect MX, SPF, DMARC, optional DKIM selector records, PTR/rDNS, sender-IP context, blacklist context, and email-header evidence.

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.

Review Safe Copy Ask about monitoring beta

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.