Microsoft 550 5.7.515 Bulk Sender Diagnostic
Microsoft announced that Outlook rejects non-compliant bulk-sender mail with 550 5.7.515 from 5 May 2025, though its own pages still mention Junk. Diagnose your domain against Microsoft's high-volume sender requirements and get the exact DNS records to publish.
Why are my messages bouncing with 550 5.7.515?
Since 5 May 2025, Microsoft has enforced authentication requirements for any sender pushing 5,000 or more messages per day to Outlook.com, Hotmail, or Live.com. Microsoft announced that it rejects non-compliant mail, though its own pages still mention Junk in places, so a sender may see either. Treat a Junk placement as the same problem as the rejection, which reads:
550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level.
That is the exact string in Microsoft's own remediation article, Fix NDR error 550 5.7.515 in Outlook.com.
The fix is rarely about message content — it is almost always about three DNS records: SPF, DKIM, and DMARC. This tool checks all three plus the supporting transport-security records that Microsoft itself publishes for outlook.com. The most common SPF root cause is the 10-lookup PermError — the SPF Flattener resolves it in one pass.
Microsoft's bulk-sender requirements
The full list from Microsoft's Tech Community announcement and the High-Volume Sender Requirements page:
| Control | Status | What Microsoft does on failure |
|---|---|---|
| SPF passes | Required | 550 5.7.515 rejection announced; Junk still mentioned |
| DKIM signs and passes | Required | 550 5.7.515 rejection announced; Junk still mentioned |
| DMARC at p=none or stricter, aligned with SPF or DKIM | Required | 550 5.7.515 rejection announced; Junk still mentioned |
| Functional unsubscribe link | Recommended | Listed under Microsoft's hygiene recommendations; Outlook reserves the right to filter or block non-compliant senders |
| List hygiene to reduce spam complaints | Recommended | Listed under Microsoft's hygiene recommendations; no complaint threshold is published in the announcement |
| TLS for SMTP delivery | Our advice | Not part of Microsoft's announced requirements |
What this tool covers
DNS-borne controls only: SPF, DMARC, MTA-STS, TLS-RPT, DNSSEC. DKIM cannot be verified from DNS alone because the selector is not discoverable — use the DKIM Checker with your specific selector to confirm the key. One-click unsubscribe lives in the message headers, not DNS; use the Email Header Analyzer on a sample message.
Volume threshold — am I in scope?
The 5,000/day threshold is per sending domain, per receiving tenant. Transactional sends count. Marketing sends count. Internal team emails count if the recipient is on Outlook. If the volume is borderline, treat yourself as in-scope — the moment a single product launch pushes you over, enforcement starts without warning.
Seeing AS9031519 instead of 550 5.7.515?
From November 5 to 9, 2026, operators saw Outlook.com also refuse part of
the mail from smaller senders whose domain had no DMARC record, with
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519). Microsoft
365 senders saw it after 550 5.7.23.
Microsoft's incident EX1545193 blamed a faulty
spam enforcement rule update and puts the end of impact at November 9, 2026, 11:02 UTC,
after a rollback; the 5,000/day rule did not change. If your domain
has no DMARC record, the scorecard above flags it. For the bounce forms,
the timeline and what to resend, read
what the AS9031519 bounces were.
Common 550 5.7.515 root causes (in order)
- SPF flat-out missing. Most common. Publish a record listing every sender (use the SPF Generator).
- SPF lookup overflow. 10-DNS-lookup limit exceeded means the record evaluates to PermError — which Microsoft reads as fail. Use the SPF Flattener.
- SPF misalignment. SPF passes for the bounce address but the From header is a different organisational domain. DMARC alignment fails and Microsoft enforces.
- DKIM missing on a new sender. An ESP added last week was not enrolled with DKIM. Check your DMARC aggregate reports.
- DMARC missing. Less common in 2026 but it happens. Microsoft will not even evaluate alignment without the policy.
Outside this tool's scope
Bulk-sender reputation, spam-complaint thresholds, and IP warmup are operational and not visible in DNS. If your domain passes everything above and you are still hitting rejections, your sending IP reputation is likely the cause — check it via the Blacklist Check.
Read the complete Microsoft guide to learn more.
Get the full picture with DMARCguard
Continuous monitoring, aggregate report parsing, and actionable insights for all your email authentication protocols.
Start Free