Bounce codes › 550 5.7.26
550 5.7.26: The inbox rejected unauthenticated mail
The receiving inbox could not confirm the email really came from your domain, because SPF and DKIM did not pass in a way that matches your DMARC policy.
Find out why your email bounced
A free check of your domain's live public records. Nothing is changed.- 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.
- Why it matters: It reads your own records, so you see your own problem, not a general one.
- What to do: Type your domain and press Check my domain.
How to fix 550 5.7.26
What the code means and the free fix.- What we found: The receiving inbox could not confirm the email really came from your domain, because SPF and DKIM did not pass in a way that matches your DMARC policy.
- Why it matters: Every email sent the same way will bounce the same way until the cause is fixed.
- What to do: Make sure every service that sends as you is in your SPF record, turn on DKIM signing at your email provider, and publish a DMARC record.
Step-by-step guides
Guides for your own email service and DNS host.- What we found: The exact steps depend on where your DNS is and which service sends your email.
- Why it matters: Each DNS host labels its screens differently.
Common questions
The questions people ask most about this code.- What we found: These are the questions people ask most about this code.
- Why it matters: A clear answer can save you a support ticket.
- What to do: Read the answers below.
- Is 550 5.7.26 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.