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 Oct 14, 2026 22:24 UTC · 7 checks · public report
Two findings block deliverability.
ssgpt6.com has no enforceable DMARC policy, so mail that forges its domain is not blocked at the recipient.
Your domain does not currently have a valid SPF record, so receiving mail servers can’t verify which services are allowed to send email for your site. This matters because it can increase the chance that your messages land in spam or that attackers can more easily spoof your address. The fix is to add or correct the SPF setting in DNS so it lists the email services you actually use to send mail.
Edit your SPF record at Cloudflare — step-by-step guide.
Your domain has more than one DMARC record, which confuses email systems because they only expect one policy to follow. This can weaken email protection and make it harder for receivers to know whether messages from your domain are legitimate. The fix is to keep just one DMARC policy in DNS and remove the extra duplicate record(s).
Edit your DMARC record at Cloudflare — step-by-step guide.
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 hello@dnsdoctor.dev to have this page removed.
DKIM helps prove that your emails really came from your domain and were not changed in transit. A 1024-bit DKIM key is considered weak, so it is easier to attack than a stronger key. The fix is to replace it with a new, stronger DKIM key and update the matching DNS entry for that selector.
Publish your DKIM record at Cloudflare — step-by-step guide.