Email Deliverability
drawdown.org
90%
A90 / 100 points
5
MX hosts
10
MX IPs
0
Blacklisted
1
No PTR
1
No FCrDNS
Issues (5)
highMX IP 2800:3f0:4003:c14::1b 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.
lowDMARC policy is quarantine, not reject
Quarantine sends unauthorized mail to spam. Reject blocks it outright. Move to reject once DMARC reports show no legitimate senders being affected.
→ Change p=quarantine to p=reject once you trust your reports.
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.
infoBlocklist status unknown for 5 MX IP(s)
2607:f8b0:4004:c07::1a, 2a00:1450:400b:c02::1a, 2800:3f0:4003:c14::1b, 2a00:1450:4009:c0f::1b, 2a00:1450:400c:c23::1a: no blocklist answered for these addresses (our queries failed, or the address is IPv6, which these IP blocklists don't cover). They are left out of the reputation score, neither clean nor listed.