Choosing an Email Verifier for a List Full of Microsoft 365 Domains

A good email verifier can confirm many Microsoft 365 company addresses, but not all of them, and the ones it cannot confirm should come back risky with a reason rather than valid. B2B lists are full of 365 domains, so how a tool handles them decides how many of your valid, risky and invalid labels you can trust. This post is for the buyer comparing verifiers on a list that is mostly company domains. It covers the three behaviours you will meet, a short test to run before you pay, and how SimpleVerifier handles each.

Microsoft 365 is not Outlook.com

People say "Outlook" for three different systems. They answer a mailbox check differently.

System	Typical domains	MX host ends in	What a check can learn
Consumer Microsoft mail	outlook.com, hotmail.com, live.com, msn.com	olc.protection.outlook.com	Weak evidence; Microsoft limits probing
Microsoft 365, edge blocking on	Company domains	mail.protection.outlook.com	A clear reply for unknown users
Microsoft 365 behind a gateway, or mid-migration	Company domains	A third-party gateway host	Often accepts every address

The first row is a known weak spot for the whole industry. We cover it in why Outlook and Hotmail addresses come back risky. This post is about rows two and three, which is what a company list contains.

The three cases on a company domain

Case 1: edge blocking on

The tenant rejects unknown recipients during the SMTP conversation. A verifier connects, asks whether it would accept mail for the address, and gets a 550 5.4.1 style rejection for an address that does not exist. That is a clear invalid. An address the server accepts is a valid.

This is the happy path, and it is common. A verifier that handles it properly gives you confident labels on a large share of a typical B2B list. See 550 5.4.1 recipient address rejected for what the reply means.

Case 2: a gateway or migration in front

Many companies put a filtering service in front of Microsoft 365, or are part-way through moving from another system. The front door accepts every recipient and sorts it out later, so the verifier hears "yes" for real and made-up addresses alike. Nothing can be learned from that "yes". It behaves exactly like a catch-all domain.

A trustworthy verifier labels these risky, with a reason such as accept-all, and does not call them valid. If a tool shows green for every address on such a domain, it is guessing. We explain what to do with them in what to do with catch-all emails and should you send to catch-all emails.

Case 3: probing blocked or limited

Some tenants and networks throttle or refuse recipient checks. A verifier that hits this should say it could not check, not invent an answer. Expect a small share of any list to land here on any tool.

The test to run before you buy

You do not need a big sample. You need real domains where you know the truth. Fifteen minutes is enough.

1. Pick three company domains on Microsoft 365 that you know. Look up the MX record with the free MX lookup to confirm they point at Microsoft.
2. For each, take one address you know is real and one you know is made up (a random string at that domain).
3. Add one domain you know sits behind a gateway or accepts everything, if you have one.
4. Run all of them through each verifier you are comparing. SimpleVerifier's free email checker takes single addresses with no account, and the 100 free checks cover the rest.
5. Score it. Real addresses should be valid. Made-up ones on edge-blocking domains should be invalid. Anything on the gateway domain should be risky or accept-all, not valid.

A verifier that marks made-up addresses valid on a gateway domain is not telling you more than a syntax check. A verifier that marks everything risky on a normal 365 domain is not trying. Our bench test guide goes deeper on setting up seeds, and what to test with free checks lists addresses worth including.

You can also see how a whole list splits by provider before you verify it. The bulk email provider lookup groups addresses by who hosts their mail, so you know how many of your rows are Microsoft 365, Google, or something else, and can predict how many will come back risky.

What to ask a vendor

• How do you label accept-all domains? The answer should be risky or a separate accept-all status, not valid.
• Do you show a reason per row? A reason column lets you tell a gateway from a blocked probe from a bad mailbox.
• What do you do with consumer Microsoft addresses? Honest answers say whether the mailbox is probed.
• Do you detect the domain type once and reuse it? Checking a domain once per file saves time and avoids hammering one tenant.
• Can I see the catch-all domains in my file in one view? The bulk catch-all checker and catch-all checker do this for any domain.

Our wider catch-all verifier comparison shows how vendors describe their handling.

How SimpleVerifier handles Microsoft 365

• 365 domains that reject unknown users are probed normally. You get valid or invalid with a reason. The Microsoft 365 email checker identifies a 365 tenant and checks the mailbox.
• Accept-everything domains come back risky, flagged as catch-all, never valid. The reason column says so, so you can route them rather than drop them.
• Consumer Microsoft mailboxes are not probed at present, because Microsoft is refusing checks from our server's network. They come back risky after syntax, domain, typo, disposable and role checks pass, with a reason that says the provider hides mailbox status. We do not call them valid. That limit is stated on pricing and in the Outlook email checker, and if you need that slice confirmed, a second verifier on a different network may help; see should you use two email verifiers.
• Every row carries a label and a reason, and you can export valid, risky and invalid separately.

What this means for price

Because the checks are the same on every plan, the plan you pick depends on volume and access, not on how good the 365 handling is. Starter is $9 a month for 2,500 emails, CSV only. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off, plus the API. We compare them in Starter or Pro.

Where another vendor is the better fit, say if you need a consumer Outlook mailbox probed from a different network, or an inbox-placement test bundled with verification, use it. Our ZeroBounce comparison and best bulk verifiers say where each fits.

A routing plan for the results

Once a company list is verified, treat the three labels differently.

• Valid: send. These are confirmed by the server.
• Risky, accept-all company domains: send in a small, warmed segment at lower volume. A pile of risky rows at one domain is the signature of a gateway. How many catch-all emails you can send gives a rule of thumb.
• Risky, consumer Microsoft: a separate segment, careful volume, suppress bounces after step one.
• Invalid: do not send.

Try it on your own domains

The first 100 checks are free with a Google sign-in, no card, and use the same mailbox check as paid plans. Pick your three test domains, run them at the verify page, and read the reason column. If the labels match what you know, Pro is $39 a month for the first 100,000 checks at full speed, then slower, never cut off. See pricing.