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 2, 2026 20:16 UTC · 7 checks · public report
Two findings block deliverability.
bradleyripple.live 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 Namecheap — step-by-step guide.
Your domain does not have a DMARC policy set up, which means receiving mail servers have no clear instructions for what to do with messages that claim to come from your domain. This matters because it makes your domain easier to impersonate in phishing and spoofing attacks, and it also reduces your control and visibility over email delivery. The fix is to publish a DMARC record in your DNS for the domain.
_dmarc · Record type: TXT · TTL: 3600One 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.
v=DMARC1; p=none; np=rejectApply this at Namecheap — step-by-step guide.
This means your domain’s DKIM email signature is using a 1024-bit key, which is considered weak by modern security standards. It matters because weaker keys are easier to attack, and that can reduce trust in your outgoing mail or make it more likely to be rejected. The fix is to replace it with a stronger DKIM key and update the mail service to use the new selector/key.
Publish your DKIM record at Namecheap — step-by-step guide.