Is Outlook.com catch-all? How to verify Outlook, Hotmail and Live addresses
Microsoft documents no catch-all for Outlook.com, Hotmail or Live, and it does not say at which step it turns away a missing mailbox. CleanBounceList first asks about a made-up address on the domain. If the server rejects it, we trust its yes for real addresses. If not, an accepted address stays ok with the note provider_post_data_reject and a score of 70 or less.
At a glance
- Domains
- outlook.com, hotmail.com, live.com
- Answer to a made-up address
- Not documented by Microsoft
- Mail servers
- outlook-com, hotmail-com and live-com.olc.protection.outlook.com
- Bounce for a missing account
- 550 5.5.0 Requested action not taken: mailbox unavailable (per a Microsoft Q&A answer)
- Catch-all option
- None documented for personal accounts
- Our result
- Accepted address: ok if the made-up address was rejected, otherwise ok with provider_post_data_reject and a score of 70 or less
- Bulk sender rules
- Over 5,000 messages a day: SPF and DKIM must pass, DMARC at p=none or stricter
What Microsoft says about missing Outlook.com mailboxes
Microsoft has no public page that says whether Outlook.com rejects an unknown address while the sending server is still asking, or only after the message arrives. A Microsoft Q&A answer about Hotmail bounces says 550 5.5.0 "Requested action not taken: mailbox unavailable" means the recipient "wasn't found by SMTP address lookup".
We handle Outlook.com, Hotmail and Live addresses the same way. Their MX records all point to hosts under olc.protection.outlook.com.
How CleanBounceList checks these addresses
Our check stops before a message is sent, so a rejection that comes later is invisible to it. To find out whether the server's yes means anything, the first address we ask about on the domain is a made-up one.
- The server rejects the made-up address: it checks recipients, so we trust its answers. Accepted addresses come back ok with no cap.
- The server accepts the made-up address: it says yes to anything, and addresses come back catch_all.
- No clear answer: an accepted address stays ok, carries the note provider_post_data_reject and scores 70 at most, below the safe group.
What to do with low-confidence Outlook addresses
An address with provider_post_data_reject was accepted, but the server may still bounce the message later. Mail it in a smaller batch apart from your main list and remove anything that bounces. Recent opens, clicks or replies from the address are stronger proof than the check.
Microsoft's rules for high-volume senders
Microsoft's rules cover domains that send more than 5,000 emails a day to Outlook.com consumer addresses (outlook.com, hotmail.com, live.com). SPF must pass, DKIM must pass, and DMARC must be at least p=none and align with SPF or DKIM, preferably both. Microsoft lists an unsubscribe link and list hygiene as recommended practices.
Microsoft's post says that from May 5, 2025, mail that misses these rules goes to Junk. It adds that rejection with "550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level" comes later, at a date "to be announced".
Questions
Microsoft does not say. That is why we test each domain with a made-up address first. If the server turns it away, we trust its yes for real addresses. If we get no clear answer, accepted addresses carry the note provider_post_data_reject.
A Microsoft Q&A answer says it means the hotmail.com or outlook.com address was not found when the server looked it up. We mark it invalid. Remove it from your list.
They apply to domains sending more than 5,000 emails a day to Outlook.com, Hotmail and Live addresses.
Yes. Every unique address we check costs 1 credit, whatever the result. Duplicates in the same list are free.
Sources
Checked on November 15, 2026. Prices and plans change, so open the vendor's page before you buy.