Outlook 550 5.7.1: "Message lacks SPF/DKIM/DMARC Auth Records"
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)
The short answer
If you got this bounce between about 5 and 9 November 2026, it was a Microsoft fault, not a problem with your domain. A faulty update to Microsoft's spam rules wrongly blocked some email to Outlook.com, Hotmail and Live addresses. Microsoft rolled the update back and says mail flow has been restored (incident EX1545193, ended 9 November 2026).
You don't need to change your DNS records because of this bounce. Resend anything important that bounced during those days.
Correction: the first version of this page (10 Nov 2026) described these bounces as ongoing and as a reason to add DMARC. That was wrong, and we've corrected it.
What happened
- When: senders reported bounces from about 5 November 2026. Microsoft's incident ran from 6 November (18:00 UTC) to 9 November (11:02 UTC).
- Who: email sent to personal Outlook.com, Hotmail and Live addresses. Independent tests didn't see it on business Microsoft 365 mailboxes.
- Why: a faulty spam-filter update, which Microsoft has fully rolled back. Microsoft has not announced any new DMARC requirement for small senders.
- Not this error: 550 5.7.515 is Microsoft's separate, published rule for senders of more than 5,000 emails a day.
If you still get this bounce
- Check the date on the bounce. If it was between about 5 and 9 November 2026, it was the Microsoft fault: resend the email.
- If the bounce is newer, keep the full bounce message, including its headers.
- Run a free scan to check SPF, DKIM and DMARC for your domain.
- If those pass and the bounce continues, send the full bounce to Microsoft through Outlook.com sender support.
Separately: does your domain have a DMARC record?
This bounce wasn't a reason to add DMARC. But a domain with no DMARC record lets anyone send email that looks like it comes from that domain, which is worth fixing for its own sake. A starting record (replace example.co.uk with your domain):
Name: _dmarc.example.co.uk
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]
Use an address you actually read for rua, on your own domain. If you send reports to another domain, that domain has to publish an authorisation record.
Check you have only one TXT record at _dmarc. Two DMARC records make receivers ignore both.
p=noneonly collects reports. It doesn't stop anyone sending fake email in your name. Real protection is quarantine or reject, once every service that sends as you (your mailbox provider, invoicing, newsletters, booking systems) passes SPF or DKIM. See DMARC is p=none: what next?
Check your domain free
The free scan tells you in seconds whether you have a DMARC record, and whether SPF and DKIM are set up for your email provider. No signup.
Scan my domain free → Buy the £24 Fix Pack (one domain) →You can publish a DMARC record yourself for free. The Fix Pack is for when you want it done right first time: records worked out for your domain and your email services, in a safe order, checked live as you go, with the steps to move on to quarantine and reject. One-off payment by card, Apple Pay or Google Pay via Stripe.
DNS on Cloudflare? Fix it for me adds your SPF and DMARC records in one click (£49 plus VAT, Fix Pack included). To hear if anything changes later, monitoring checks your domain every day from £4 a month.
Frequently asked questions
Was this a new Microsoft DMARC rule?
No. Microsoft put it down to a faulty update to its spam rules and rolled the update back (incident EX1545193). Its only published DMARC rule for Outlook.com covers senders of more than 5,000 emails a day.
Do I need to add DMARC because of this bounce?
No. Microsoft rolled back the faulty update, so no record change is needed for this bounce. Separately, a domain with no DMARC record lets anyone send email that looks like it comes from that domain, which is a reason to set one up anyway.
Did it affect email to business Microsoft 365 addresses?
Independent tests during the fault found it on Microsoft's consumer servers (outlook.com, hotmail.com, live.com and similar), not on business Microsoft 365 mailboxes.
Will Outlook resend the bounced emails?
No. A 550 is a permanent rejection. Resend anything important that bounced between about 5 and 9 November.
I'm still getting this bounce after 9 November.
Then it isn't the November fault. Check that SPF or DKIM passes for your own domain, and send the full bounce to Microsoft through Outlook.com sender support.
Related guides
- No DMARC record found
- Outlook 550 5.7.515: access denied
- Gmail 550 5.7.26: unauthenticated email
- Microsoft 365 DKIM not signing
Based on public reports and tests published 5–10 November 2026. We'll update this page if Microsoft confirms, changes or reverses the behaviour.