Email Deliverability
hix.nl
78%
B71 / 90 points
4
MX hosts
5
MX IPs
0
Blacklisted
1
No PTR
2
No FCrDNS
Issues (6)
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 2a00:a0c0:3::1a6 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.
mediumMX IP 83.137.192.116 fails FCrDNS check
Reverse DNS returns mailscanner6.hix.nl, but forward-resolving that hostname does not include 83.137.192.116. Receivers that validate FCrDNS (Gmail, Yahoo, Outlook) treat this as a strong negative signal.
→ Fix either the PTR record or the forward A/AAAA of the hostname so they round-trip to the same IP.
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 1 MX IP(s)
2a00:a0c0:3::1a6: 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.