Email Deliverability
91160.com
68%
C62 / 90 points
2
MX hosts
4
MX IPs
0
Blacklisted
4
No PTR
4
No FCrDNS
Issues (7)
criticalNo DMARC record
Without DMARC, there is no policy signal telling receivers what to do with unauthenticated mail. Gmail and Yahoo now require DMARC for high-volume senders.
→ Publish a TXT record at _dmarc.yourdomain.com: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; fo=1
highMX IP 103.86.78.2 has no PTR (reverse DNS)
Gmail and Microsoft both require reverse DNS on sending IPs. Without it, mail from this host is almost always rejected or spam-foldered.
→ Add a PTR record at your hosting provider. For cloud MTAs (AWS SES, Mailgun, etc.) this is managed by the provider.
highMX IP 103.86.78.3 has no PTR (reverse DNS)
Gmail and Microsoft both require reverse DNS on sending IPs. Without it, mail from this host is almost always rejected or spam-foldered.
→ Add a PTR record at your hosting provider. For cloud MTAs (AWS SES, Mailgun, etc.) this is managed by the provider.
highMX IP 43.154.252.202 has no PTR (reverse DNS)
Gmail and Microsoft both require reverse DNS on sending IPs. Without it, mail from this host is almost always rejected or spam-foldered.
→ Add a PTR record at your hosting provider. For cloud MTAs (AWS SES, Mailgun, etc.) this is managed by the provider.
highMX IP 43.154.252.16 has no PTR (reverse DNS)
Gmail and Microsoft both require reverse DNS on sending IPs. Without it, mail from this host is almost always rejected or spam-foldered.
→ Add a PTR record at your hosting provider. For cloud MTAs (AWS SES, Mailgun, etc.) this is managed by the provider.
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.
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.