Outlook.com Now Bounces Small Senders Without DMARC (Microsoft Hasn't Said So)
Since November 5, 2026, Outlook.com has been bouncing some email from domains that publish no DMARC record, returning "550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records" to senders far below Microsoft's 5,000-a-day bulk threshold. Microsoft has not announced it. The fix is one DNS TXT record, and the exposed domains are usually the ones your ESP never touches.
The first public write-up came from MailRoute, which spotted the bounces in its own outbound logs on November 5 and noted that Microsoft had published no postmaster notice, blog post or service-health entry. Within a day, Suped had collected firsthand reports from Microsoft Q&A threads, including a Zoho message that was rejected once and then delivered on a resend. That inconsistency is the part I'd pay attention to. A domain can get maybe half its mail through and look totally fine in a spot check.
For most marketing teams, the newsletter domain is not the problem. Your ESP made you set up SPF, DKIM and DMARC years ago, probably during the May 2025 push when Microsoft started enforcing authentication for senders above 5,000 messages a day. The problem is everything else that sends mail with your name on it.
Microsoft already said this was coming (sort of)
Microsoft's original high-volume sender post was pretty explicit about who it targeted: domains sending more than 5,000 emails a day to outlook.com, hotmail.com and live.com. Non-compliant mail would go to Junk first, and the post said rejection would follow at a "date to be announced," with the error code 550 5.7.515.
Buried in that same post is a line that reads differently now: "While enforcement first targets large senders, all senders benefit from these best practices." On paper, that was a polite suggestion. In practice, it looks a lot like a preview.
And to be fair, the new bounce is not the same mechanism. The 5.7.515 rejection lists SPF, DKIM and DMARC results. The new one, per MailRoute, is a bare 550 5.7.1 with an AS9031519 tag that didn't even appear on day one. Microsoft hasn't confirmed what triggers it, and db8 points out that some admins with correct records also reported bounces. So I'd treat "missing DMARC" as the strongest pattern so far, not a confirmed rule. It's still the cheapest thing on the list to fix, by a wide margin.
Your newsletter domain is fine. Your invoices probably aren't
Look at who's actually getting hit. db8's examples are invoices, appointment confirmations, webshop order confirmations and replies to contact forms, sent by small offices. MailRoute says the affected domains it saw mostly had working SPF, many had DKIM, and they just never published DMARC. One Microsoft Q&A poster with a GoDaddy-hosted custom domain said his email stopped working on November 6; his SPF record was six to eight years old and DKIM and DMARC were missing entirely.
Now map that onto a typical marketing org. A typical marketing org has a pile of sending domains nobody has audited in a while:
- A secondary domain for cold outreach or sales engagement, set up by an SDR manager who has since left
- The billing or invoicing tool, sending from a subdomain finance created
- Webinar and event platforms sending confirmations "from" your brand
- Website contact forms and lead magnet delivery, often routed through PHP mail or a plugin
- Regional or product microsites with their own domains
None of those hit 5,000 a day, which is exactly why they slipped through the 2025 audit. And a lot of them send to personal addresses. Freelancers, small-business buyers and a decent share of B2C leads use hotmail.com and outlook.com addresses. If your lead magnet email bounces, the lead just thinks you never sent it.
A bounce on a lead magnet doesn't show up as a bounce. It shows up as a conversion rate that dropped a little and nobody can explain why.
How common is the gap? The Guardian360 DMARC benchmark scanned 10,833 domains and found 25.8% had no DMARC record at all. That's primary domains, mostly. Side domains are, I'd guess, quite a bit worse, because nobody checks them until something breaks.
The 20-minute audit, in roughly this order
This is the boring version, and honestly it's the right one.
1. List every domain and subdomain that sends mail as you. Pull it from your DNS provider, your ESP, your CRM's sending settings, the sales engagement tool, the invoicing tool and the form plugin. If you have a DMARC record with rua reporting already, the aggregate reports will show senders you forgot about. My rough benchmark: if your list has fewer than four sending sources, I would assume you missed one.
2. Check each one for a DMARC record. Run dig +short TXT _dmarc.yourdomain.com for each domain. Output starting with "v=DMARC1" means a record exists. Nothing back means you're exposed. MailRoute's sister company has a browser-based checker for this exact bounce if the command line isn't your thing.
3. Publish p=none with reporting. Add a TXT record at _dmarc with v=DMARC1; p=none; rua=mailto:you@yourdomain.com. Only one DMARC record per domain; db8 notes that two records make receivers ignore both, which is a very annoying way to fail.
4. Confirm alignment, not just existence. DMARC only passes if SPF or DKIM passes for the domain in the From address. A DMARC record sitting on top of a tool that signs with its own domain fixes nothing. MailRoute calls out Microsoft 365 specifically: it signs with an onmicrosoft.com domain until you enable DKIM for your own domain, and that signature doesn't count.
5. Send a test to a personal Outlook.com address from each stream. Because the rejections are intermittent, send three or four, not one. Keep any bounce messages in full; the exact code tells you whether you're looking at 5.7.1, 5.7.23 (an SPF problem) or 5.7.515.
If you already enforce p=reject on a domain, don't weaken it to p=none to test this. Suped is explicit that p=none doesn't guarantee acceptance, and dropping enforcement mostly just helps spoofers.
Why I think this sticks
Google and Yahoo moved first in 2024, Microsoft followed for bulk senders in 2025, and every one of those rollouts started quietly and got documented later. I'd put the odds at roughly 70% that Microsoft formalizes a no-DMARC rejection for all senders to its consumer domains by the end of Q1 2027, probably with a postmaster page that describes what's already happening. Could also be a bug they roll back next week. I'm not betting on that.
Anyway, the tradeoff is lopsided. Publishing a p=none record takes a few minutes per domain and changes nothing about how your mail is treated today, except that receivers can now see you have a policy. Not publishing it means some fraction of your quotes, receipts and lead magnets to Outlook users vanish, and nothing in your dashboards tells you. We covered why you can set up all three records and still get rejected back in June, and alignment is still where most of those failures live.
Email is also the channel that has been growing while organic shrinks, which makes the quiet stuff matter more, not less.
The domains nobody owns
The hardest part of this isn't DNS. It's figuring out who owns the sales domain, the billing subdomain and the form plugin, because usually the answer is "someone in 2023." If you do one thing Monday, send a message in whatever channel your ops, sales and finance people share, asking every team to name the tools that send email as the company. The list you get back will be incomplete, but it'll be a lot more complete than the one in your head.
I don't think this turns into a crisis for anyone with a decent ESP setup. It's more the slow leak kind of problem, the kind you only find when a customer forwards you a bounce and asks why their invoice never showed up.