Outlook.com sender requirements (May 2025): checklist

Since May 2025, Outlook.com rejects mail from high-volume senders without SPF, DKIM and DMARC. Check your domain against Microsoft's rules.

Applies to
Domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses.
In force
Enforced since 5 May 2025.

Check your domain against this list

We only read public DNS records. The domains you check are not stored.

The email checklist

  1. SPF passes

    The sending domain needs an SPF record that includes every service sending for it.

    Our check verifies this. How to set it up

  2. DKIM passes

    Mail must be signed with a DKIM key published under the sending domain.

    Our check verifies this. How to set it up

  3. DMARC record, at least p=none

    A DMARC record must be published. Microsoft accepts p=none.

    Our check verifies this. How to set it up

  4. DMARC passes

    SPF or DKIM must align with the domain in the From address. Microsoft prefers both.

    Our check verifies this. How to set it up

  5. Valid From and Reply-To addresses Recommended

    Use addresses that exist and can receive replies.

    Not visible from outside: check it yourself.

  6. Working unsubscribe link Recommended

    Let people leave your mailing lists easily.

    Not visible from outside: check it yourself. How to set it up

  7. Clean mailing lists Recommended

    Remove addresses that bounce and people who never open your mail.

    Not visible from outside: check it yourself.

Who has to comply

Domains that send more than 5,000 messages a day to consumer Outlook.com addresses, which include hotmail.com and live.com. Mail to businesses on Microsoft 365 follows each organisation's own settings, but meeting the same bar helps there too.

What happens if you don't

Since 5 May 2025, Outlook.com rejects mail from high-volume senders that don't meet the rules, with the error 550 5.7.515: "sending domain does not meet the required authentication level". The message bounces, so the recipient never sees it.

Required and recommended

SPF, DKIM and DMARC are the hard requirements; they trigger the rejection. The other items are what Microsoft calls good practice: they don't cause 5.7.515, but they affect whether your mail lands in the inbox or in Junk.

Microsoft accepts p=none, but it does ask that DMARC passes, which means SPF or DKIM has to align with your From address. You can only see that in DMARC reports: DNS shows that your records exist, reports show whether your mail actually passes.

The rules match what Gmail and Yahoo ask, so one setup covers all three.

Check it, then keep it that way

A record that is right today can break tomorrow: a new tool gets connected, a DNS migration drops a line, a provider rotates its keys. Check your domain now, and let MailWatch check it every day, so you hear about problems before a receiver or an auditor does.

This checklist covers email only, in our own words. It is not legal advice and not a full list of what the rules ask.