Email Deliverability
la.lv
68%
C62 / 90 points
5
MX hosts
10
MX IPs
2
Blacklisted
1
No PTR
1
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 192.178.234.27 is blacklisted
This IP is listed on 1 blocklist(s): UCEPROTECT Level 1. Mail from this IP will be rejected or spam-foldered by many receivers.
→ Request delisting from each blocklist provider. If the IP is shared (e.g., a cloud sending service), contact your provider's deliverability team — you may need to move to a dedicated IP.
highMX IP 172.253.157.26 is blacklisted
This IP is listed on 1 blocklist(s): UCEPROTECT Level 1. Mail from this IP will be rejected or spam-foldered by many receivers.
→ Request delisting from each blocklist provider. If the IP is shared (e.g., a cloud sending service), contact your provider's deliverability team — you may need to move to a dedicated IP.
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.
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:c17::1b, 2800:3f0:4003:c14::1b, 2a00:1450:400b:c02::1a, 2a00:1450:4009:c0f::1b, 2a00:1450:400c:c23::1b: 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.