Scanning
Scanning your domain…
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 26, 2026 08:29 UTC · 7 checks · public report
One finding blocks deliverability.
myaccept.co has no enforceable DMARC policy, so mail that forges its domain is not blocked at the recipient.
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: 3600v=DMARC1; p=none; np=rejectYour SPF setting is using a “soft fail” ending, which means mail from servers not on the approved list is treated as suspicious but not fully blocked. This is usually fine for DMARC, but it is a little less strict and can let some unwanted mail through. If you want to tighten it, change the ending to a hard fail only after you are sure every legitimate sender is already included.
We email you a link to the full report, with every finding and fix. Opening it signs you in to a free account and starts a 14‑day Monitor trial. No card, and you can unsubscribe in one click.
Check SPF, DMARC, DKIM, MX, DNS health, blacklists and domain & SSL expiry in one free scan, with the exact record to paste for each problem it finds.
Domain owner? Re-scan any time — or email hello@dnsdoctor.dev to have this page removed.
Apply this at Cloudflare — step-by-step guide.
Edit your SPF record at Cloudflare — step-by-step guide.
Publish your DKIM record at Cloudflare — step-by-step guide.