Email Deliverability
bulletjournal.com
87%
A87 / 100 points
5
MX hosts
10
MX IPs
0
Blacklisted
1
No PTR
1
No FCrDNS
Issues (4)
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.
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 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.