Email Deliverability Check - Review Authentication and DNS Risks
Check the domain-level email configuration signals that MXScan can inspect, including SPF, DKIM, DMARC and supported infrastructure checks. Use the findings to troubleshoot possible deliverability problems. DNS configuration alone cannot predict whether a specific email will reach the inbox or spam folder.
What We Check
This assessment focuses on supported configuration checks. Inbox placement also depends on message content, the actual sending IP, sender history, recipient engagement and each receiving provider's filtering decisions.
Email Authentication
- • SPF record validation - Not assessed by this check
- • DKIM selector discovery - Not assessed by this check
- • DMARC policy analysis - Not assessed by this check
- • MTA-STS configuration - Not assessed by this check
DNS & Infrastructure
- • MX record configuration - Not assessed by this check
- • DNS propagation status - Not assessed by this check
- • SMTP TLS support - Not assessed by this check
- • Reverse DNS setup - Not assessed by this check
Reputation & Blacklists
- • Major RBL checking - Not assessed by this check
- • IP reputation analysis - Not assessed by this check
- • Domain reputation - Not assessed by this check
- • Sender score indicators - Not assessed by this check
Example report - illustrative values only
SAMPLE DATA - NOT A LIVE SCAN. These numbers and labels demonstrate the report layout. They are not an assessment of your domain. Enter a domain and run a check to view available domain-specific findings.
Deliverability Score
Good - Minor improvements recommended
Authentication
95Infrastructure
92Reputation
75Recommended next steps depend on your actual results
A DNS change should address a verified issue in your own domain. Do not publish a generic DMARC or TLS reporting record simply because it appears in an example report. Review the current policy, sending providers, mailbox ownership and reporting destination before applying changes.
What this check can and cannot determine
Recommended next steps depend on your actual results
A DNS change should address a verified issue in your own domain. Do not publish a generic DMARC or TLS reporting record simply because it appears in an example report. Review the current policy, sending providers, mailbox ownership and reporting destination before applying changes.
What this deliverability check can and cannot determine
- Can inspect: DNS records and configuration signals that the checker actually retrieves, with relevant warnings and limitations.
- Cannot determine from DNS alone: true inbox placement, complete sender reputation, email engagement, or whether a particular message passed aligned authentication.
- For message-level diagnosis: send a controlled test message, examine full authentication headers and any SMTP response, and use the receiving provider's available delivery diagnostics.
How to interpret findings
Treat missing or invalid authentication records as configuration issues to investigate. Treat blacklist or reputation data as verified only when the underlying check actually ran and identifies the source checked. A technically valid domain configuration does not guarantee delivery. Review each finding before changing DNS.
Related reading: Why emails go to spam, email blacklist check, and email security audit.
Improve Your Email Deliverability
Learn why emails go to spam and how to fix common issues.
Individual Security Checks
Deep dive into specific email security components.
Frequently Asked Questions
Why am I landing in spam?
Spam placement can be influenced by authentication failures, sender/IP reputation, message content, complaint rates and receiving-provider filtering. A domain-level scan may identify some configuration risks; it cannot identify every cause of a particular message's placement.
How fast do fixes help?
DNS changes take 1-48 hours to propagate globally. Authentication improvements show immediate results once propagated. Reputation improvements can take days to weeks depending on sending volume and consistency.
Does a high deliverability score guarantee inbox placement?
No. A configuration score can summarize the checks performed by a tool, but it is not an inbox placement rate. Deliverability also depends on the specific message, sending IP and the receiving service. Use the underlying findings rather than treating a single score as proof of successful delivery.