Understand the email you send.
MXValidation helps you inspect email authentication, message content and sending configuration, with clear findings and practical next steps.
Make email troubleshooting easier to understand
Email delivery depends on several things working together: the domain’s DNS records, the sending platform, the message itself and the receiving server. A setting can look correct in isolation while a real message reveals a different picture.
MXValidation brings those details into one report. Send an email through the platform you normally use, then review the authentication results, delivery information and content findings together. Each check explains what was observed and what you can investigate next.
Follow the authentication evidence
Inspect SPF, DKIM and DMARC alongside the identities they apply to. Where recorded data is available, SPF lookup chains and DMARC alignment details explain how the envelope sender and DKIM signing domains relate to the visible From address.
A valid DNS record and a message that passes authentication are different questions. The report helps you examine both.
See the server behind the delivery
Review the sending IP, reverse DNS, EHLO/HELO identity, configured IP blocklist checks and the TLS connection observed when the message arrived.
These findings describe the server that delivered the email to MXValidation. If you use an external relay, that is usually your provider’s infrastructure.
Understand content and spam signals
SpamAssassin findings show which rules were triggered and how they contributed to its score. Positive and negative contributions help you distinguish signals that increase the score from those that reduce it.
Review the individual findings alongside your template and sending setup. One keyword or one rule does not explain every delivery outcome.
Inspect the message itself
Check headers, MIME structure, HTML characteristics and extracted links. Compare the HTML preview with the plain-text version, or inspect the original source when you need the technical detail.
Link checks inspect URLs and DNS information. They do not visit destination pages or certify that their content is safe.
Useful wherever you send email
Developers can inspect transactional messages from applications, such as notifications and account emails. Newsletter and marketing teams can review a representative campaign before sending it. Domain and mail administrators can investigate authentication and DNS issues or compare results after a configuration change.
Use the same sending service, domain and template that you want to evaluate. A message sent through another provider tests that provider’s delivery path instead.
A simple workflow, with the detail when you need it
- Generate a test address and send a representative, non-confidential email to it.
- Open the report and expand the checks to see the evidence and explanations.
- Address confirmed problems, then review any warnings in the context of your sending setup.
- After making changes, use a new test address to check a fresh delivery.
For a walkthrough, see How it works. You can also explore an example report before submitting a message.
Read the findings alongside the score
The overall score summarizes the configured checks for one delivery. Passed means a check succeeded, Warning highlights something to review, and Unknown means there is not enough reliable evidence to reach a conclusion. Unknown is not a confirmed failure.
Authentication and domain policy are presented separately. For example, a message that passes DMARC with p=none still receives full DMARC points; monitoring mode does not turn that pass into a failure.
A high score does not guarantee inbox placement. Recipient providers also consider their own reputation signals, engagement, filtering and policies. MXValidation does not validate mailing lists or verify whether individual mailboxes exist. Read the scoring methodology and service limits for more detail.
Tools for a closer look at individual settings
You can investigate public DNS without sending an email. Check SPF, DKIM and DMARC records, review receiving servers with the MX Record Checker, or inspect MTA-STS and TLS-RPT settings.
The EML / EMLX Viewer opens saved message files locally in your browser. Standalone tools do not consume your email-test viewing allowance. For explanations and practical guides, visit the MXValidation blog.
Start free and keep a useful testing history
Guests can access 3 distinct tests and verified free accounts 20 per rolling 24 hours, subject to viewing rules and request limits.
A free account gives you a history of your account-owned tests to revisit as your configuration changes. Those results remain until you delete the test or account; original message files have separate retention rules.
Know what you are sharing
Creating a report involves processing and storing the message you submit, its technical results and delivery information. Use a test copy and remove passwords, confidential attachments and personal information that the analysis does not need.
Keep guest report links private. Account-owned reports require the owning account. HTML previews disable active content, and external images remain blocked unless you explicitly load them. Our Privacy first page explains access, retention and analytics, with full details in the Privacy Policy.
Help with your next step
The frequently asked questions cover common questions about reports, accounts and testing limits. If a finding needs clarification or something does not work as expected, contact us with a description of the issue. Avoid including confidential message content.
See what your next email reveals.
Start with a real delivery and a report you can act on.