Is Microsoft 365 catch-all? How to verify company addresses on Exchange Online
It depends on how the domain is set up. When every mailbox is in Exchange Online, Directory Based Edge Blocking is on by default and a missing address gets 550 5.4.1, which CleanBounceList marks invalid. Hybrid domains set to Internal relay pass unknown recipients on instead. When we get no clear answer, an accepted address stays ok with the note provider_post_data_reject and a score of 70 or less.
At a glance
- Answer to a made-up address
- 550 5.4.1 with Directory Based Edge Blocking; passed on to the company's own server on Internal relay domains
- Mail servers
- A host ending in mail.protection.outlook.com, or in mx.microsoft when the domain uses DNSSEC
- Bounce for a missing account
- 550 5.4.1 Recipient address rejected: Access denied
- Catch-all option
- No setting documented; Internal relay domains do not reject unknown recipients
- Our result
- invalid for 550 5.4.1; ok for an accepted address, with provider_post_data_reject and a score of 70 or less when unclear
How Microsoft 365 handles a missing mailbox
Microsoft calls the feature Directory Based Edge Blocking (DBEB). Its documentation says that if all recipients for your domain are in Exchange Online, DBEB is already in effect. For an address that does not exist, the service "blocks the message before filtering even occurs" and answers 550 5.4.1 Recipient address rejected: Access denied.
DBEB needs the domain to be set as Authoritative. Hybrid and migration setups, where some mailboxes still live on a company's own Exchange server, can use Internal relay instead. Microsoft's docs say an Internal relay domain passes mail for unknown recipients on to the on-premises Exchange organization rather than rejecting it.
Microsoft also warns that even with DBEB, "there might be infrequent instances" where addresses that don't exist get through. Its bounce messages use a second code for unknown recipients, 550 5.1.10 RESOLVER.ADR.RecipientNotFound.
How CleanBounceList checks these addresses
Our check stops before a message is sent, so a bounce that comes later never reaches it. We ask about a made-up address on the domain first to learn which kind of tenant we are talking to.
- The made-up address gets 550 5.4.1: DBEB is on. Real addresses that are accepted come back ok with no cap, and any address with 5.4.1 comes back invalid.
- The made-up address is accepted: the domain takes any address, and its 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.
Plus addressing on Microsoft 365
Microsoft says plus addressing is on by default in Exchange Online. Mail to jane+news@company.com reaches jane@company.com: Exchange first looks for the full address, then for the address without the +tag. An admin can turn it off for the whole organization.
What to do with unclear Microsoft 365 addresses
Treat provider_post_data_reject as a yes with doubt. Send to these addresses in a smaller batch, apart from your main list, and drop every address that bounces. Recent replies or clicks from an address are better proof than any check.
Questions
No. When all of a domain's mailboxes are in Exchange Online, Microsoft rejects unknown addresses with 550 5.4.1 by default. Domains set to Internal relay pass unknown recipients on instead, so a check cannot rule them out.
On Microsoft 365 it is the Directory Based Edge Blocking answer for an address that does not exist in the organization. We mark it invalid. On other mail servers we report a 5.4 code as unknown.
Look up the domain's MX record. Microsoft 365 domains usually point to a host ending in mail.protection.outlook.com. Domains that turned on DNSSEC for inbound mail point to a host ending in mx.microsoft instead. We check both the same way.
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.
- Microsoft Learn: Use Directory-Based Edge Blocking to reject messages sent to invalid recipients in Exchange Online
- Microsoft Learn: How SMTP DNS-based Authentication of Named Entities (DANE) works
- Microsoft Learn: Fix NDR error 550 5.4.1 in Exchange Online
- Microsoft Learn: Fix NDR error 550 5.1.10 in Exchange Online
- Microsoft Learn: Plus addressing in Exchange Online