Skip to content
Microsoft (Outlook.com and Microsoft 365) · permanent error

550 5.7.511: banned sending IP: request removal by email

Microsoft 365 banned the IP you send from and wants to investigate before lifting it; the delist portal cannot remove this block.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
550 5.7.511
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
550 5.7.511 Access denied, banned sender

What it means

5.7.511 is an IP ban like the 5.7.606 to 5.7.649 range, with one difference: Microsoft wants to investigate traffic from the address before releasing it, so the self-service delist portal cannot be used. The bounce tells you to forward it to delist@microsoft.com. Microsoft asks for the full NDR code and the IP address, and says it will contact you within 48 hours with next steps. Use the time to find out why the IP was banned, since the investigation looks at the same traffic.

Common causes

  • The IP sent spam, phishing or other traffic Microsoft judged harmful.
  • A compromised server or account on your network used the IP.

How to fix it

  1. 01Find and stop whatever sent unwanted traffic from the IP.
  2. 02Forward the bounce to delist@microsoft.com with the full NDR code and the IP address.
  3. 03Wait for Microsoft to contact you, which it says happens within 48 hours, and follow its instructions.
  4. 04Do not use sender.office.com for this code; it does not handle 5.7.511.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 550 5.7.606–649Banned sending IP: use the delist portal.Microsoft 365 put your sending IP on its blocked senders list; you can request removal yourself at sender.office.com.MicrosoftPermanent
  2. 5.7.1Sending IP on the Microsoft 365 blocklist.Microsoft 365 refused the message because the sending IP address is on its own blocklist, named Blocklist 1 in the bounce.MicrosoftPermanent

Further reading

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer