Microsoft sender requirements
Check a domain against the four Microsoft rules and find out why mail bounced with 550 5.7.515.
More in Email · Reports
What the bounce means
The full message reads "550 5.7.515 Access denied, sending domain does not meet the required authentication level". Outlook.com, Hotmail, Live and MSN send it when a domain that sends them 5,000 or more messages a day does not pass SPF, DKIM and DMARC. The mail is refused, not delayed, so retrying does not help.
The fix is in DNS and in how your sending service signs mail. This page shows which of the four rules your domain misses and what to change, and it keeps the question of what DNS can show apart from what only a sent message can.
The four rules
| Rule | What it asks | What settles it |
|---|---|---|
| M1 SPF passes | The SPF check on the sending address passes | The SPF record, then a sent message |
| M2 DKIM passes | The message carries a DKIM signature that verifies | The DKIM key, then a sent message |
| M3 DMARC record published | A DMARC record exists, with any policy | DNS alone |
| M4 DMARC passes | SPF or DKIM passes and matches the From domain | A sent message |
DNS shows whether the records are in place. Only the headers of a message show whether it passed, which is why two of the four rules show as unknown until you paste the headers of a message you sent. A policy of none counts for rule M3, though it protects nobody from forged mail.
How to find and fix the problem
- Enter the domain in your From addressWe read its SPF record, look for DKIM keys and check DMARC. Enter the IP your mail leaves from under More options if you want the reverse DNS checked too.
- Read the failing rows firstEach row says what we found and gives the record or the tool that fixes it. A DKIM key that is not yet published for a Microsoft 365 selector is shown as information, not as an error.
- Settle the unknowns with one messageSend a test message to an Outlook.com address, open Show original or its headers, and paste them under "Check a sent message". The page then judges SPF, DKIM and alignment from that message.
The usual causes
- SPF is missing, or has more than 10 lookups so receivers ignore it. See the SPF flattener.
- A new sending service signs with its own domain, so DKIM passes but is not aligned with your From domain. Add its DKIM records, or use a custom signing domain.
- There is no DMARC record at all. Publish one with the DMARC record generator.
- A forwarding address or mailing list rewrites the message and breaks SPF, so only DKIM can carry the result.
For Gmail and Yahoo, which ask for more, use the Gmail and Yahoo sender requirements page. The checks overlap, so a domain that meets one list is most of the way to the other.
Questions people ask
Who counts as a high-volume sender for Microsoft?
A sender of 5,000 or more messages a day to Outlook.com, Hotmail, Live and MSN mailboxes from one From domain. The rules are written for those consumer mailboxes.
Does p=none satisfy the DMARC rule?
Yes for the rule about having a record. It does not stop anyone pretending to be you, so move to quarantine or reject when your reports show that all your own mail passes.
Why does the page show unknown for DKIM?
A DKIM key in DNS shows that signing is possible, not that a message was signed and verified. The headers of a sent message carry that result, so the rule stays unknown until you paste them.
Will the bounce go away once the records are fixed?
New mail is judged again as it arrives, so it clears as soon as the records are live and a message passes. DNS caches can delay that by the time to live of the old records.
Do you store the headers I paste?
No. In a browser with JavaScript they are read on your device and only six facts are sent. Without it the text reaches our server for one request and is not kept, logged or put in the address.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is sender_requirements_check. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/sender-requirements?q=github.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp