Your domain, checked and fixed.

Bounce codes › 550 5.7.23

550 5.7.23: SPF check failed

Your SPF record does not list the server that sent this email, so the receiver treated it as forged.

Find out why your email bounced
  1. What we found: We check your SPF, DKIM, DMARC and blocklists and show which one failed, with the exact record to fix it. Free, about 10 seconds.
  2. Why it matters: It reads your own records, so you see your own problem, not a general one.
  3. What to do: Type your domain and press Check my domain.
How to fix 550 5.7.23
  1. What we found: Your SPF record does not list the server that sent this email, so the receiver treated it as forged.
  2. Why it matters: Every email sent the same way will bounce the same way until the cause is fixed.
  3. What to do: Add the sending service's include to your one SPF record.
Step-by-step guides
  1. What we found: The exact steps depend on where your DNS is and which service sends your email.
  2. Why it matters: Each DNS host labels its screens differently.
Common questions
  1. What we found: These are the questions people ask most about this code.
  2. Why it matters: A clear answer can save you a support ticket.
  3. What to do: Read the answers below.
    Is 550 5.7.23 my fault or the receiver's?
    Usually the sending side. The receiver checked the sending domain or server and didn't trust what it found.
    Will resending the email work?
    Not until the cause is fixed. The same email will usually bounce the same way.
    How long until it works after I fix it?
    Most DNS changes show within an hour. Some DNS hosts say to allow up to 48 hours. Run the free check again to see when it's live.
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.