Outlook rejects email from domains without DMARC: what to check
Since 5 November 2026, Outlook.com rejects some email from domains without a DMARC record, also from small senders. How to check your domain and fix it.
Since 5 November 2026, Microsoft's consumer email services reject some messages from domains that have no DMARC record. Two email companies, MailRoute and mxio, reported the change on 6 November. It affects mail to Outlook.com, Hotmail, Live and MSN addresses, also from small senders.
If your business sends email from its own domain, a customer with a Hotmail address may not receive your quote or invoice. The usual fix is one DNS record.
The Outlook.com bounce: "Message lacks SPF/DKIM/DMARC"
The sender gets this bounce: 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records. Some versions add a code in brackets, such as (AS9031519).
MailRoute's report is based on its own outbound logs and on reports from other administrators. It says that volume is not the trigger: "A one-line reply from a small office can bounce."
Microsoft rejects only part of the mail from an affected domain. The same message can bounce once and arrive on a second try, so the problem is easy to miss. The mxio guide says that Outlook.com does not try again: you must resend after the fix.
Microsoft has not announced the rule
As of 6 November, Microsoft had published no postmaster notice, blog post or service-health entry about it, MailRoute says. The facts above come from the two companies, which both sell email services, not from Microsoft.
An earlier rule covers only large senders. In April 2025, Microsoft announced requirements for high-volume senders: domains that send more than 5,000 messages a day to Outlook.com must pass SPF and DKIM and publish DMARC at "no less than p=none". From 5 May 2025, Outlook.com sent their failing mail to Junk.
Since 1 February 2024, Google requires all senders to Gmail to set up SPF or DKIM. Google requires DMARC only above 5,000 messages a day.
What SPF, DKIM and DMARC do
These three DNS records prove that an email comes from your domain:
- SPF lists the servers that can send mail for your domain.
- DKIM adds a digital signature to each message.
- DMARC tells the receiving server what to do when the checks fail, and where to send reports.
DMARC passes only when SPF or DKIM passes for the same domain as the From address. This match is called alignment. A DMARC record alone does not help if no service passes SPF or DKIM for your domain.
How to add a DMARC record
Use a free online DMARC checker, or run dig +short TXT _dmarc.yourbusiness.com in a terminal. An empty result means no DMARC record.
In the DNS settings at your domain provider, add a TXT record:
- Name:
_dmarconly. Some providers add the domain, and the full domain makes a doubled name. - Value:
v=DMARC1; p=none; rua=mailto:dmarc@yourbusiness.com. Theruaaddress receives daily reports. Use a mailbox that you read, or remove that part.
A domain can have only one DMARC record. If one exists, edit it.
Then check DKIM. In Microsoft 365, DKIM for your own domain needs two CNAME records, selector1 and selector2. In Google Workspace, turn on DKIM in the admin console and publish the google._domainkey record. Check every other service that sends as your domain too, such as the newsletter tool or the booking system.
According to mxio, p=none stops the rejection but does not stop fake email in your name. For that, change the policy to quarantine and then reject, after the reports show that all your real senders pass. Fake email in a known company's name is a common way to start phishing, as we described in our article on the 123 Reg data breach.
What to do this week
- 01Check your domain for a DMARC record.If you do not manage the DNS, ask your IT provider or web agency.
- 02Add
v=DMARC1; p=noneat_dmarcif there is no record. - 03Turn on DKIM for your domain in Microsoft 365 or Google Workspace.
- 04Send a test message to an Outlook.com or Hotmail address.In the message headers, look for
dmarc=pass. - 05Search for bounces with "Message lacks SPF/DKIM/DMARC" since 5 November, and send those messages again.If DMARC passes and mail still bounces, mxio suggests that you report the full bounce at olcsupport.office.com.