Help · Email and spam
550 5.7.26: "This mail is unauthenticated"
Direct answerDNSFix help, reviewed 2026-11-12The answer in one or two sentences. The steps below show how to do it. Our editorial policy says how we write and check these pages. Learn more
A big inbox rejected your email because it couldn't verify it came from your domain: SPF and DKIM didn't pass in a way that matches DMARC.
What it means
The receiving inbox checked your email and none of the proofs lined up with the domain in the From address. Since late 2025 the biggest inboxes reject these outright instead of sending them to spam.
Why it happens
- The service sending the email (your website, CRM or newsletter tool) isn't in your SPF record.
- DKIM isn't turned on at that service, or its DKIM record isn't in your DNS.
- Your DMARC record is missing, so the receiving inbox treats any failure strictly.
Fix it
- Find which service sent the email that bounced. The bounce usually names the sending server.
- In that service, turn on "domain authentication". It gives you one to three DNS records.
- Add them at your DNS host, and add the service to your SPF record (only one SPF record, ever).
- Add a DMARC record if you don't have one:
v=DMARC1; p=none; rua=mailto:reports@dnsfix.com. - Re-run the check, then resend.
Stop it happening againDNSFix can check your domain on a schedule and email you when something changes.
DNSFix Pro checks your domain every 4 hours and emails you the step-by-step fix soon after we spot a problem. From $19 a month.Questions
Is 5.7.26 a problem on the receiver's side?
No. It's always about your domain's SPF, DKIM or DMARC records, which you control.
Related
- Why are my emails going to spam?
- How to set up DKIM (and fix "DKIM not found")
- DMARC fail or "DMARC alignment failed"
- big inbox sender rules: what small businesses need
Product names belong to their owners. DNSFix isn't affiliated with them.