Email Deliverability
nt.technology
B
75 / 90
1
MX hosts
2
MX IPs
0
Blacklisted
0
No PTR
0
No FCrDNS
Issues (5)
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.
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.
lowOnly one MX host
Single MX means any outage or block at that host results in mail loss or bounces. Industry best practice is at least two MX records at different hosts.
→ Add a secondary MX at a different provider or a backup MX service.
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.
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.