How Outlook.com and Hotmail answers a verification check
Outlook.com, Hotmail, Live and MSN addresses all land on Microsoft's consumer mail servers under olc.protection.outlook.com. When a mailbox does not exist, they reply with the RFC 5321 default wording: 550 5.5.0 Requested action not taken: mailbox unavailable. There is no "user unknown" phrase, so a generic parser cannot tell it apart from a policy rejection.
Microsoft is also the strictest major provider about senders. It refuses IPs on its own blocklist with 550 5.7.606 or 5.7.511, restricts suspicious traffic with 4.7.500 to 4.7.699 ("Access denied, please try again later"), and its Outlook.com postmaster policy requires high-volume senders to pass SPF, DKIM and DMARC, with 550 5.7.515 for domains that do not.
Outlook.com and Hotmail replies and what RocketVerifier returns
Each SMTP reply maps to one status and sub-status. Replies about the probing server are never counted against the address.
| Reply | Result | What it means |
|---|---|---|
| 250 2.1.5 Recipient OK | deliverable none | The mailbox exists. |
| 550 5.5.0 Requested action not taken: mailbox unavailable | undeliverable mailbox_not_found | On Outlook.com this wording means the mailbox does not exist. |
| 550 5.7.606 Access denied, banned sending IP | unknown blocked | About the sending IP, never the mailbox. Not charged. |
| 451 4.7.500 Access denied, please try again later | unknown blocked | Microsoft throttling. Not a mailbox answer. |
| 550 5.7.515 Access denied, sending domain does not meet the required authentication level | unknown blocked | A sending rule for high-volume mail. Fix SPF, DKIM and DMARC. |
What RocketVerifier does differently for Outlook.com and Hotmail
-
Microsoft's "mailbox unavailable" read correctly
On Microsoft hosts, a 550 with the RFC default "mailbox unavailable" text is a missing mailbox. Everywhere else the engine treats that wording as ambiguous, so it is never over-applied.
-
Outlook.com and Microsoft 365 kept apart
The engine tells consumer Outlook.com from Microsoft 365 tenants by their MX hosts and applies separate rules and limits to each.
-
Banned-IP replies never cost you an address
5.7.606, 5.7.511, 5.7.708 and 5.7.750 are recognised as IP blocks. The address comes back unknown and free.
-
Hotmail typos fixed at the source
hotmial.com, hotmail.con, outlok.com and similar slips are flagged as possible_typo with the corrected address in did_you_mean.
-
RocketShield on your forms
Stop mistyped and fake Outlook and Hotmail signups before they reach your list, with one script tag.
-
Deferrals retried for you
Temporary deferrals are retried automatically, up to three times about ten minutes apart, before a final result is returned.
Sending to Outlook.com and Hotmail: what to get right
- Outlook.com requires domains that send over 5,000 messages a day to pass SPF, DKIM and DMARC. Non-compliant mail goes to Junk first and can be rejected with 550 5.7.515. Check all three before a big send.
- Outlook.com's postmaster policy tells senders to stop sending to an address after a permanent failure. Suppress hard bounces right away.
- Hotmail lists are often old. Abandoned Hotmail accounts are closed after long inactivity and start to bounce, so clean Hotmail-heavy lists before you mail them.
Keep reading
Sources
- Outlook.com Postmaster: Policies
- Microsoft Support: Fix NDR error 550 5.7.515 in Outlook.com
- Microsoft Learn: Email non-delivery reports in Exchange Online
Last reviewed