Live · updated just now

Outlook is quietly bouncing emails from business domains missing a DMARC record

Monday, 9 November 2026 · Marketing & design · Full report

What was found

Since November 5, 2026, Microsoft's free consumer email service has started bouncing some messages sent from domains that have no DMARC record 1. DMARC is a short DNS entry that tells receiving mail servers how to check whether a message really comes from the domain it claims. The bounces happen even when the sender already has working SPF or DKIM, the two older checks that confirm a sender's identity 1. Rejected messages come back with a "550 5.7.1" error, and the pattern is uneven: some emails from the same domain arrive normally while others are refused 1. This goes further than Microsoft's May 2025 rule, which required all three checks only for senders pushing more than 5,000 messages a day 1.

Who it applies to

The change affects anyone who sends mail from their own custom domain to Microsoft consumer addresses ending in outlook.com, hotmail.com, live.com, or msn.com 1. Small and low-volume senders, who were not covered by the 2025 bulk-sender rule, are the ones newly caught 1.

How strong the evidence is

Early. This is an incident report and technical write-up from MailRoute, an email security company, based on rejection traffic it began seeing on November 5, 2026 1. The full article was read. It does not say how many messages or domains were affected 1. As of November 6, Microsoft had not announced or documented the change, so the details come from outside observation rather than an official source 1. The error message does not say which check failed, and because the rejections come and go, affected senders may have trouble noticing the problem or confirming its cause 1.

What it means in practice

Domain owners who email Microsoft consumer inboxes should publish a basic DMARC record 1. This is a DNS TXT entry placed at "_dmarc" on the domain, such as "v=DMARC1; p=none" 1. The "p=none" setting only asks receivers to report on checks and does not tell them to block anything, yet having the record appears to be enough to stop the bounces 1. The fix works only if SPF or DKIM lines up with the domain shown in the From address, so owners should confirm that this alignment is in place as well 1. Without these steps, important messages such as invoices, password resets, or customer notices could fail to arrive, and the sender might never realize it 1.