Running diagnostic
Running your DNS diagnostic…
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Scanned Aug 20, 2026 23:16 UTC · 7 checks · public report
Solid base — three policy steps remain.
ted.com publishes DMARC with p=none — spoofed mail is monitored but not blocked.
v=spf1 include:aspmx.sailthru.com include:spf.mandrillapp.com include:_spf.google.com include:_spf.intacct.com include:et._spf.pardot.com exists:%{i}._spf.mta.salesforce.com include:mail.zendesk.com ip4:108.60.129.112/28 ~allEdit your SPF record at Amazon Route 53 — step-by-step guide.
v=DMARC1; p=none; pct=100; rua=mailto:[email protected]; sp=none;_dmarc · Record type: TXT · TTL: One send: the full report — every finding and fix — lands in your inbox, with a free account waiting. Opening it signs you in and starts a 14-day Monitor trial. No card, and you can unsubscribe in one click.
Domain owner? Re-scan any time — or email [email protected] to have this page removed.
3600v=DMARC1; p=quarantine; rua=mailto:[email protected]; sp=none; np=rejectApply this at Amazon Route 53 — step-by-step guide.
Your email authentication is using a DKIM key that is too short, which makes it weaker than recommended. This matters because weaker keys are easier to break, so email spoofing and tampering are harder to defend against. The fix is to replace that DKIM key with a stronger, longer key and update the DKIM setup for the affected selector.
Publish your DKIM record at Amazon Route 53 — step-by-step guide.