Email deliverability test
Review the DNS configuration that affects whether a domain can send and receive authenticated email.
Try
A configuration check, not an inbox guarantee
This report checks published DNS records. Inbox placement also depends on sending reputation, message content, recipient engagement, and provider-specific filtering that DNS alone cannot measure.
- Mail routing and address records
- SPF, DKIM, and DMARC presence
- Authoritative nameserver configuration
- Direct links to inspect each record set
Checks
What it reads
Mail routing, authentication records, and nameservers, all from public DNS.
Proves
What it can show
That your domain is configured to send and receive authenticated mail.
Blind to
What it cannot see
Your sending history, complaint rate, and how recipients treat your mail.
Inbox
What decides placement
Providers weigh all of it together. DNS alone never guarantees the inbox.
Common questions
- What does this test actually check?
- The DNS records that affect email: MX routing, SPF, DKIM, DMARC, and nameservers.
- Everything passed but mail still lands in spam. Why?
- DNS is only the setup. Placement also depends on sending reputation, message content, and recipient engagement.
- How often should I run it?
- After any DNS or provider change, and whenever delivery drops. Records break quietly.
- Does a new domain start with poor deliverability?
- It starts with none at all. Reputation builds with volume, so warm up gradually instead of sending a large first batch.
- Can I test a domain I do not own?
- Yes. Every record it reads is published publicly.
Use these checks during signup
The API returns allow, review, or block with the reasons behind it.