Email Deliverability
mail.nt.technology
B
72 / 90
1
MX hosts
2
MX IPs
0
Blacklisted
0
No PTR
0
No FCrDNS
Issues (4)
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
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.
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.
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.