Email Deliverability
wy.sk
87%
A87 / 100 points
3
MX hosts
5
MX IPs
0
Blacklisted
0
No PTR
2
No FCrDNS
Issues (5)
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.
mediumMX IP 185.102.21.66 fails FCrDNS check
Reverse DNS returns mx-lb-bra.core.webglobe.com, but forward-resolving that hostname does not include 185.102.21.66. 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.
mediumMX IP 185.102.21.66 fails FCrDNS check
Reverse DNS returns mx-lb-bra.core.webglobe.com, but forward-resolving that hostname does not include 185.102.21.66. 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.
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 1 MX IP(s)
2001:1ab0:7e1f:1::1:0: 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.