550 5.7.515: domain does not meet authentication level
Quick fix
Make both SPF and DKIM pass for the sending domain, and publish a DMARC record with at least p=none that aligns with SPF or DKIM.
How to fix it
- Find the service that sent the rejected message and the domain in its From address.
- Add that service to the SPF record of the envelope sender (Return-Path) domain, with the include or IP range it documents, and keep the record under 10 DNS lookups.
- Turn on DKIM signing with your own domain in that service and publish its key, so DKIM passes for a domain that aligns with the From domain.
- Publish a DMARC record at
_dmarc.example.comwith at leastp=none, for examplev=DMARC1; p=none; rua=mailto:[email protected]. - Send a test message to an Outlook.com address and check that the Authentication-Results header shows
spf=pass,dkim=passanddmarc=pass.
Learn more: DMARC explained: policy, alignment and reports
How to check
The email security check looks up SPF, DKIM and DMARC for the domain in the From address and shows the DMARC policy. Then check a real message: send one to an Outlook.com address and read the Authentication-Results header, which must show spf=pass, dkim=pass and dmarc=pass.
The Email security check opens with your domain filled in; it runs when you press Check.
Tools to check it
What the error means
Full error text: 550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.
550 5.7.515 is the rejection Outlook.com (the consumer service behind outlook.com, hotmail.com and live.com) gives mail from high-volume senders that do not authenticate the way Microsoft requires. Microsoft's announcement gives the text as "550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level." The fix is in your DNS and in the sending service: SPF and DKIM must pass, and DMARC must be published and aligned.
Microsoft writes: "For domains sending over 5,000 emails per day, Outlook will soon require compliance with SPF, DKIM, DMARC." and "This applies to Outlook.com - our consumer service, which is supporting hotmail.com live.com and outlook.com consumer domain addresses." The requirements are:
- SPF: "Must Pass for the sending domain."
- DKIM: "Must Pass to validate email integrity and authenticity."
- DMARC: "At least p=none and align with either SPF or DKIM (preferably both)."
Both SPF and DKIM have to pass, not just one of them, which is stricter than DMARC itself. Alignment means the From domain matches (or is a subdomain of the same organizational domain as) the domain that SPF or DKIM passed for; see SPF passes but DMARC fails.
The timing in Microsoft's post is not consistent. After its April 2025 update it says "Non‐compliant messages will first be routed to Junk", and "in the future (date to be announced), non-compliant messages will be rejected", but it also says "we have made a decision to reject messages that don't pass the required authentication requirements". Senders report 550 5.7.515 bounces in public Microsoft Q&A threads, so treat the rejection as live. The code is not in the Exchange Online list of SMTP errors: a Microsoft 365 recipient that rejects on DMARC sends 550 5.7.509 instead.
Sources
- Microsoft Defender Blog: Strengthening Email Ecosystem: Outlook’s New Requirements for High‐Volume Senders (checked 2026-11-17)
- Microsoft Learn: Email nondelivery reports (NDRs) and SMTP errors in Exchange Online (checked 2026-11-17)
- RFC 9989: DMARC (checked 2026-11-15)