All guides · Updated: 2026-11-12
Email bounced with “550 5.7.515”: what Outlook is telling you
550 5.7.515 is Outlook's way of saying: the domain that sent this email doesn't meet the authentication rules Microsoft requires, so I refused it. The full message is “Access denied, sending domain [your domain] does not meet the required authentication level”. It's a permanent rejection: the email isn't retried. It gets fixed in the sender's domain.
Across the 1,500 small-business sites we checked, two of the causes of this error were frequent: 1 in 17 had a broken SPF, and more than a third of the domains with email on Microsoft 365 had never turned on DKIM.
Who it applies to, and since when
The rule belongs to consumer Outlook, and Microsoft announced it like this:
- It covers email sent to outlook.com, hotmail.com and live.com addresses.
- It applies to domains that send more than 5,000 emails a day to those addresses.
- Since 5 May 2025, email that doesn't comply is rejected with this code. The first plan was to send it to Junk; Microsoft switched to rejection so nobody is left wondering why.
What counts is the domain in the “From:” line, and everything that goes out under it: newsletters, invoices, your online store's notifications. Being on the recipient's safe senders list doesn't get around the rule.
What Microsoft requires: all three at once
- SPF passing for the sending domain.
- DKIM passing.
- DMARC published, at least at
p=none, and aligned with SPF or DKIM (preferably both).
“Aligned” means the domain that passed SPF, or that signed with DKIM, is the same one shown in the email's “From:” line. A newsletter service that signs with its own domain instead of yours passes DKIM but isn't aligned.
That's more than Gmail asks of small senders, who get by with one of the two (SPF or DKIM). Here it's both, plus DMARC.
Step 1: see which of the three failed
The code doesn't say which of the three failed, and since the email was refused you can't open it in Outlook. There's another way to see it:
- Find out which service sent the bounced email: your mailbox, newsletters, invoicing, your online store, your website's form.
- Send a test email from that same service to a Gmail account of yours.
- Open it, click the three dots and “Show original”. At the top you'll see SPF, DKIM and DMARC, each with PASS or FAIL, and the domain each one passed with.
If the domain next to SPF or DKIM isn't yours, that's the alignment case: the service is sending with its own domain.
Step 2: SPF and DKIM, in the service that sent it
- Add the service to your SPF: the
include:it gives you goes into the SPF record you already have, never into a second record. - Turn on that service's DKIM with your domain, following its help (usually one or two CNAME or TXT records). Each service's help calls this “domain authentication”.
- If the service allows it, ask for the return-path address to use your domain too: that's what aligns SPF.
Two SPF records or more than 10 lookups: how to tidy up SPF
Step 3: DMARC, at least at p=none
If your domain has no DMARC yet, create this record in your DNS panel, with an address of yours to receive the reports:
- Type
TXT- Name (host)
_dmarc- Value
v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com
p=none is enough to meet Microsoft's rule, but it only watches: it doesn't stop anyone sending fake email in your name. Once SPF and DKIM are right for everything you send, move up to p=quarantine.
What Microsoft also recommends, and can't be seen from outside
- A real “From:” and “Reply-To:” address, on your domain, that can receive replies.
- An easy, visible way to unsubscribe, especially in newsletters and campaigns.
- Clean lists: regularly remove addresses that no longer exist.
- Honest subject lines, and only sending to people who agreed to receive it.
No DNS check can see these, ours included. Microsoft says it may filter or block senders who don't follow them, and even with everything right the inbox isn't guaranteed: the rest is the sender's reputation.
Step 4: confirm
Repeat the test from step 1: the test email has to show SPF, DKIM and DMARC with PASS, and your domain next to them. Then send again to the Outlook address that bounced it.
And check the domain: Excubitor tells you whether SPF is broken, whether Microsoft or Google DKIM is switched off and where your DMARC stands, with the evidence for each.
Mistakes we see often
- Fixing the mailbox when the bounced email came from the newsletter tool or the invoicing system.
- Getting SPF right and thinking that's enough: Outlook wants DKIM and DMARC too.
- Letting the service sign with its own domain: DKIM passes, but it isn't aligned with yours.
- Creating a second SPF record for the new service, instead of adding the
include:to the existing one.
So you don't have to check again
These errors show up the day someone adds a new service or touches the DNS. Excubitor can watch the domain every week and email you only when something changes. Free for 1 domain: run the check and press “Notify me”.