Your domain, checked and fixed.

Help · Email and spam

dmarc=fail (p=quarantine): your own email went to spam

DNSFix™ help, reviewed 2026-11-12

Direct answer
  1. Direct answer: After you tighten DMARC to quarantine, any service that sends as you without passing SPF or DKIM for your domain goes to spam. Find that service and fix it.
  2. What happened:

    At p=none, failing email was delivered anyway. At p=quarantine, inboxes put it in spam, and the headers read dmarc=fail (p=quarantine). So the change didn't break the email; it revealed a sender that was never passing.

  3. Fix it:

    Check your domain first: the report shows the exact fix for your own setup. The steps are inside Fix this.

    Got a record from a chatbot or your web person? Check it before you paste it.

    Fix this
    1. Paste the headers of an email that went to spam into the email header reader. It shows the sending service and which check failed.
    2. Turn on DKIM for your own domain at that service, or add it to your SPF record.
    3. If many senders fail and you can't fix them quickly, go back to p=none for now, fix them using your DMARC reports, then step up again.
    4. Check your record with the DMARC checker.
Stop it happening again
  1. What we found: Every DNSFix™ feature is free right now, including the watch that emails you the step-by-step fix soon after we spot a problem.
  2. What to do:

    Check your domain

Questions
  1. Should I go back to p=none?

    Only if many legitimate senders fail and you can't fix them this week. Fix the senders, then go back up one step at a time.

DNSFix™ Help
Hi, this is DNSFix™ Help. Ask anything about your domain or account. Answers come from our help library, and some are drafted by AI and say so. After any change, check your domain again: the report tests every record against the standard rules. Need more help? We'll follow up by email.