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 Sep 11, 2026 00:30 UTC · 7 checks · public report
Solid base — three policy steps remain.
amped-m.com publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF check is using a softer “maybe not allowed” setting for mail that isn’t listed, instead of a stricter “block it” setting. This matters because it can make spoofed or misconfigured emails a little less clearly rejected by other mail servers. The fix is to switch to the stricter setting only after you’re sure every legitimate sender is already included in your SPF setup.
v=spf1 include:_spf.google.com ~allEdit your SPF record at GoDaddy — step-by-step guide.
DMARC is set up, but it is only in monitoring mode, so it is not actively protecting your domain from spoofed or fake email. This matters because attackers can still send messages that look like they come from you, which can hurt trust and deliverability. To fix it, change the DMARC policy from monitoring-only to an enforcement mode so email that fails checks is rejected or quarantined.
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.
v=DMARC1; p=none; rua=mailto:[email protected]Edit your DMARC record at GoDaddy — 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 GoDaddy — step-by-step guide.