Email Deliverability
groups.google.co.nz
91%
A82 / 90 points
5
MX hosts
10
MX IPs
0
Blacklisted
1
No PTR
1
No FCrDNS
Issues (4)
highSPF record has no 'all' mechanism
Without an explicit all qualifier, receivers fall back to neutral and treat unauthorized senders as OK.
→ Add -all (hardfail) or at minimum ~all (softfail) to the end of your SPF record.
highMX IP 2800:3f0:4003:c14::e 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.
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.
infoBlocklist status unknown for 5 MX IP(s)
2607:f8b0:4004:c1b::e, 2800:3f0:4003:c14::e, 2a00:1450:400b:c02::e, 2a00:1450:4009:c0f::e, 2a00:1450:400c:c23::e: 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.