Email Deliverability
eonet.jp
34%
F31 / 90 points
0
MX hosts
0
MX IPs
0
Blacklisted
0
No PTR
0
No FCrDNS
Issues (5)
criticalNo MX records resolve to IP addresses
Your MX hosts could not be resolved. Mail to this domain will bounce.
highDMARC policy is none (monitor only)
p=none provides visibility but no protection. Spoofed mail still passes through to inboxes. Move to quarantine once you've verified legitimate senders are authenticated.
→ Once DMARC aggregate reports show your legitimate mail aligned, upgrade to p=quarantine, then to p=reject.
mediumSPF uses ~all (softfail) instead of -all (hardfail)
Softfail still lets mailbox providers accept unauthorized senders. Upgrade to -all once you're confident all legitimate senders are covered.
→ Replace ~all with -all in your SPF record.
lowDMARC has no reporting address
Without rua= aggregate reports, you're flying blind on authentication failures.
→ Add rua=mailto:dmarc@yourdomain.com to your DMARC record. Consider a service like dmarc.io, Postmark DMARC, or URIports to parse reports.
infoDKIM could not be verified
We checked common selectors (default, google, selector1/2, mail, etc.) and found none. This is normal for providers that use custom selectors (Amazon SES, Fastmail) — DKIM may be working fine. It is NOT scored against you.
→ Confirm DKIM is set up with your mail provider. If you know the selector, you can verify it directly on the email-auth page.