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 Sep 4, 2026 22:00 UTC · 7 checks · public report
Solid base — three policy steps remain.
python.org publishes DMARC with p=none — spoofed mail is monitored but not blocked.
v=spf1 mx ip4:188.166.95.178/32 ip6:2a03:b0c0:2:d0::71:1 include:stspg-customer.com include:_spf.google.com include:mailgun.org ~allEdit your SPF record at Amazon Route 53 — step-by-step guide.
v=DMARC1; p=none; pct=100; rua=mailto:[email protected]; sp=none; aspf=r;Edit your DMARC record at Amazon Route 53 — .
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.
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.