Article
How Accurate Are Email Verifiers on Microsoft 365 Addresses?
By Unlimited Verifier Team ·

Summary
Email verifiers are dependable on Microsoft 365 addresses for syntax, domain and MX checks. Mailbox-level results are less reliable on Outlook.com, Hotmail and catch-all business domains, so treat the SMTP check as conditional on the tenant. Measure accuracy on a sample of your own list before trusting any headline figure.Email verifiers are dependable on Microsoft 365 addresses for syntax, domain and MX checks, but mailbox-level results are less reliable on Outlook.com, Hotmail and catch-all business domains, where a worked example below shows about 23% of a mixed segment landing in Risky.
This guide explains where those gaps come from, how to measure accuracy on your own list instead of trusting a headline figure, and how to act on the results. For the wider picture, start with our pillar on email verifier accuracy.
Quick answer
- Syntax, domain and MX checks are dependable. A default Microsoft 365 MX record ends in
mail.protection.outlook.com, which usually confirms the domain runs on Microsoft 365. - Mailbox checks vary by tenant type. Business tenants that reject unknown recipients usually give a clear answer. Consumer Outlook.com, Hotmail and Live addresses, and catch-all tenants, often don't.
- Plan for a Risky share. In the worked example, 23% of a 12,000-address Microsoft 365 segment is Risky on the first pass.
- Measure your own accuracy. Sample 385 addresses per segment for a ±5% margin at 95% confidence, or 1,068 for ±3%. We recommend 1,068 for any decision.
- Don't mail Risky addresses at full volume. Resolve them with deep verification and engagement data first.
How accurate are email verifiers on Microsoft 365 addresses, check by check?
Accuracy isn't one number. It depends on which check you mean. Structural checks are highly dependable on Microsoft 365 domains. The SMTP mailbox check is where results range from clear, on well-configured business tenants, to inconclusive, on consumer and catch-all domains. No public, provider-level accuracy figure for Microsoft 365 is widely published, so treat any single headline number as a claim to test.
| Check | What it can prove | Reliability on Microsoft 365 | Why |
|---|---|---|---|
| Syntax | The address is well-formed | High | A format rule; says nothing about whether the mailbox exists |
| Domain | The domain exists in DNS | High | Confirms the domain, not the person |
| MX | The domain accepts mail | High | Microsoft 365 domains publish predictable MX hosts |
| SMTP mailbox | The server accepts or refuses this recipient | Varies: high on tenants that reject unknown recipients, low on catch-all and throttled domains | The answer is set by tenant configuration and Microsoft's defences |
| Catch-all detection | The domain accepts any address | Moderate to high | Detects the accept-everything setting, but can't judge one mailbox |
| Disposable and role flags | The address matches a known pattern | High for the pattern | A role address such as info@ can be a live team inbox |
Bottom line: Trust the structural checks on Microsoft 365 domains. Treat the mailbox check as conditional on the tenant.
Why does Microsoft 365 verification give less clear answers?
Most verifiers check a mailbox by asking the receiving server whether it would accept mail for that address. Microsoft applies anti-abuse controls that limit unsolicited recipient probing, and each tenant sets its own rules. The answer reflects configuration and reputation as much as the address itself.
How the SMTP mailbox check works
The verifier connects to the domain's mail server, issues MAIL FROM and RCPT TO commands, reads the reply, and disconnects without sending a message. The protocol is defined in RFC 5321. Replies carry enhanced status codes defined in RFC 3463. A 250 means the server accepts the recipient at this stage. A 4xx means try later. A 5xx means refused. The 5.1.1 code signals a bad destination mailbox.
Four Microsoft-specific complications
- Edge rejection can give a clean answer. Microsoft documents Directory Based Edge Blocking, which can reject unknown recipients during the SMTP session with
550 5.1.10for tenants that enable it. A rejection there is a strong invalid signal, and the setting is the reason some tenants are easy to verify. - Probes get throttled. Repeated recipient checks from one source can trigger temporary
4xxdeferrals or refused connections. A deferral is not an answer. A verifier that reports it as uncertain is being accurate about its own limits. - Catch-all tenants accept everything. An administrator can configure a domain to accept mail for any local part. Every probe then returns
250, which says nothing about whether the individual person exists. - Gateways change the signal. Some organisations place a filtering service in front of Microsoft 365. The gateway may accept the probe and decide later, so a
250means less than it would on a bare tenant.
For SaaS teams running email verification for ecommerce and SaaS workflows, these gaps matter most in B2B lists, where Microsoft 365 is a common mail platform. A few points of misclassification across 10,000 addresses is hundreds of contacts.
Bottom line: These are configuration choices and defences, not bugs in one tool. That is why accuracy varies by domain, not only by vendor.
Which Microsoft 365 address types can you trust?
The table sorts common Microsoft 365 address types by how much weight a verifier result can bear. These are patterns that follow from documented behaviour and common tenant setups. They are not measured results from our own tests.
| Address type | What the mail system typically does | What a verifier often returns | Reliability | Recommended action |
|---|---|---|---|---|
| Named business mailbox, tenant rejects unknown recipients | Accepts real mailboxes; refuses missing ones with a 5.1.x code |
Valid or Invalid | High | Use the result |
| Named business mailbox behind a third-party gateway | Gateway may accept the probe and decide later | Valid or Risky | Medium | Deep-verify, then check engagement |
| Catch-all business domain | Accepts every address | Risky | Low for individual verdicts | Treat as unknown; gate by engagement |
| Outlook.com, Hotmail, Live or MSN consumer address | Often throttled or inconclusive | Risky, frequently | Low to medium | Deep-verify, then check engagement |
| Shared mailbox | Accepts mail and delivers it to a team | Valid | High for existence, low for personal reach | Keep, but don't count it as a personal contact |
| Distribution list or Microsoft 365 group | Accepts mail and fans it out to members | Valid | High for existence, low for personal reach | Remove from person-level sends |
Consumer addresses deserve a separate note. They run on Microsoft's consumer infrastructure rather than per-tenant settings, so you can't tune them. A verifier can only report what Microsoft returns, which is why Gmail and Outlook accuracy often differs.
Bottom line: Trust results most on tenants that reject unknown recipients, and least on catch-all and consumer domains.
What do Valid, Risky and Invalid mean for a Microsoft 365 address?
Valid means the mailbox passed the checks at that moment. Invalid means the server permanently refused the address, usually with a 5.1.x code. Risky means the verifier could not reach a definitive answer. Catch-all domains, deferrals, gateways, role addresses and disposable domains all land here.
Unlimited Verifier sorts every address into Valid, Risky or Invalid, and flags catch-all, disposable and role-based addresses. Some other tools add an Unknown category. Check how each tool maps Unknown before comparing results. If Unknown is folded into Valid, your Microsoft 365 numbers will look better than they are. Why different verifiers give different results explains the most common mapping differences.
Bottom line: Risky is the honest answer for many Microsoft 365 addresses. Treat it as a cost to manage, not an error to hide.
How do you measure a verifier's accuracy on your own Microsoft 365 list?
Vendor accuracy figures come from the vendor's own test data. They are rarely broken out by mail provider, so you need your own measurement. Start by defining your errors, because vendors use the term "false positive" in different ways.
Define the two errors by outcome.
- Dead address marked Valid: this damages sender reputation, and it is the error that matters most for bounces. Our guide to what a false positive is in email verification covers the terminology.
- Live address marked Invalid: you lose real contacts, usually without noticing.
Build a control set. Create 50 mailboxes on a Microsoft 365 test tenant you control (expect Valid). Add 50 non-existent addresses on a domain you control with catch-all switched off (expect Invalid). Add a few addresses on a catch-all test domain (expect Risky). This is a smoke test. Your own tenant may behave differently from a customer's tenant, so it shows whether the verifier reads the answer correctly, not how customer tenants will respond.
Size the real sample. The standard formula for a proportion, n = z² × p × (1 − p) ÷ e², with z = 1.96 and p = 0.5, gives 385 for a ±5% margin and 1,068 for ±3%. Some guides round to 1,067 or 1,070, which makes little practical difference. Where sources differ, we recommend 1,068 per segment for any decision. Sample consumer and business domains separately so results don't blend. For more on sample design, read how many emails to use when testing a verifier.
Check the Valid bucket by sending. Send a small mailing only to addresses marked Valid. Bounces on that send give an upper-bound estimate of dead addresses marked Valid. Don't mail the Invalid bucket, because that damages reputation. Instead, re-check a sample of Invalid addresses with a second method, such as a second verifier or a review of the rejection codes.
Report the Risky share as its own line. Risky addresses aren't wrong, but they are the cost of your list. Track them separately so the Valid figure stays honest.
Bottom line: Test with ground truth you control, and read the Valid and Invalid buckets separately.
How do you verify a Microsoft 365 list, step by step?
This workflow assumes you have a CSV export from your email platform and no technical background beyond copying commands.
- Export your contacts as a CSV with the email column and at least one engagement field, such as last open or last click. You'll need the engagement field in step 9. Sign up for a free account if you don't have one.
- Find the Microsoft 365 domains. List the unique domains in your file. For each business domain, look up its MX record:
A standard Microsoft 365 setup returns a host ending indig +short MX example.commail.protection.outlook.com. If the MX points to a third-party gateway, label that domain "gateway" in your notes, because it needs the cautious treatment described above. - Split the file into segments. Create three files: business Microsoft 365 domains, consumer domains (outlook.com, hotmail.com, live.com, msn.com), and everything else. Separate files keep results comparable.
- Upload each file. Use the upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Pro lists can hold up to 25,000 addresses each.
- Run standard verification. Standard verification is unlimited on every plan, including Free, so re-running a file after a fix costs no extra per-email fee.
- Sort the Risky bucket by flag. Filter by the catch-all, disposable and role flags. Anything left without a flag is unresolved, which is where the deep check in the next step helps.
- Run deep verification on uncertain addresses. Deep verifications are capped monthly, at 750 on Free and 25,000 on Pro, so spend them on the Risky consumer and business addresses that matter. For single spot-checks, the free email checker is useful.
- Export before results expire. Results are kept for 24 hours on Free and 30 days on Pro. Export as CSV, Excel or JSON on the day you run the check.
- Route each bucket. Valid addresses go to your main segment, but only after an engagement filter. Invalid addresses go to your suppression list. Risky addresses go to a held segment.
- Re-import or automate. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so you re-import the CSV manually. For recurring checks, the email verification API accepts single addresses and batches of up to 10,000 emails per request. Teams building scheduled jobs can follow the email verification API and automation approach. For sign-up forms, see real-time email validation.
Bottom line: Segment by domain type before you verify, then spend deep checks on the uncertain buckets.
What does a worked example look like for a 40,000-contact list?
The figures below are illustrative. The arithmetic and plan limits are real.
Setup: A B2B software company holds 40,000 contacts, of which 12,000 are Microsoft 365 addresses:
- 7,500 named business mailboxes on tenants that reject unknown recipients
- 1,500 addresses on catch-all business domains
- 3,000 consumer Outlook, Hotmail and Live addresses
First pass (standard verification, illustrative results):
| Segment | Addresses | Valid | Risky | Invalid |
|---|---|---|---|---|
| Named business mailboxes | 7,500 | 6,825 (91%) | 375 (5%) | 300 (4%) |
| Catch-all business domains | 1,500 | 0 (0%) | 1,500 (100%) | 0 (0%) |
| Consumer Microsoft | 3,000 | 1,800 (60%) | 900 (30%) | 300 (10%) |
| Total | 12,000 | 8,625 (71.9%) | 2,775 (23.1%) | 600 (5.0%) |
Check: 8,625 + 2,775 + 600 = 12,000.
Deep pass: Deep verification resolves 400 of the 900 consumer Risky addresses to Valid, leaving 500 Risky. The 1,500 catch-all addresses can't be resolved by SMTP, so they stay Risky.
Final position:
- Valid: 8,625 + 400 = 9,025 (75.2%)
- Risky: 2,775 − 400 = 2,375 (19.8%)
- Invalid: 600 (5.0%)
Check: 9,025 + 2,375 + 600 = 12,000.
Cost: The 12,000 addresses fit in one Pro list, under the 25,000-address cap. The 900 deep checks sit within Pro's 25,000 monthly deep allowance. Free wouldn't work here. Its 750 monthly deep checks fall short of 900, and 12,000 ÷ 150 = 80 lists, against a Free limit of 25 lists a month. Pro costs $29 a month, or $25 a month billed annually. To compare vendors on the same basis, use email verification pricing as your measure, not the headline rate.
What to do with the numbers:
- Send to the 9,025 Valid addresses, starting with those who engaged recently.
- Hold the 2,375 Risky addresses. Mail the consumer ones only after a small engagement-based test.
- Sample the 600 Invalid addresses. If 3% prove live, that is 18 real contacts, which is worth knowing before you delete them.
Bottom line: A quarter of this segment needs a decision, not a verdict. The plan turns the Risky bucket into a managed segment.
How should you handle Risky Microsoft 365 addresses?
Risky addresses need a rule, not a guess. This framework works for most list owners.
- Sort Risky by reason. Separate catch-all, consumer, gateway, role and unresolved results. Each group needs a different fix.
- Run deep verification on consumer and gateway addresses. Keep only the results that resolve to Valid or Invalid. Leave the rest in Risky.
- Gate catch-all addresses with engagement. Mail them only if they opened, clicked or purchased within a set window. We suggest 90 days as a starting point, since many teams use 90 to 180. Send a small test first and watch the bounce rate.
- Confirm what still can't be resolved. A double opt-in confirmation is the reliable route for addresses that remain unresolved. Verification can't prove consent, so email verification compliance and hygiene depends on opt-in records as well as clean addresses.
- Re-verify monthly. Catch-all status changes when administrators reconfigure a tenant, and consumer behaviour changes without notice. Email list maintenance best practices covers how to schedule this.
For a deeper look at why results go unresolved, read why does my verifier return so many unknowns.
Bottom line: Risky is a segment you manage with engagement and confirmation, not a list you delete or mail blindly.
Does a Valid Microsoft 365 result mean the email will be delivered and read?
No. A Valid result means the mailbox accepted the check at that moment. It doesn't guarantee delivery, because the message may still be filtered or quarantined. It also doesn't mean a person reads the message. Shared mailboxes and distribution lists accept mail for a team, and a mailbox can exist while nobody monitors it. Both return Valid.
For a fuller explanation, see does a valid result mean the email will be delivered.
Bottom line: Use Valid as evidence the address exists, and use engagement data to judge whether anyone reads the mail.
Are vendor accuracy claims for Microsoft 365 trustworthy?
Treat them as claims to test. Most headline figures come from a vendor's own dataset, often without a breakdown by provider and without a definition of "accuracy". Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, and it isn't split by Microsoft 365 tenant type. Our article on whether 99% accuracy claims hold up explains how to read such numbers.
When you compare the best email verification tools, ask every vendor for the same details:
- Accuracy broken out by domain provider, especially Microsoft 365 and consumer Outlook.
- Whether "accuracy" means precision (Valid results that are correct), recall (dead addresses caught), or both.
- The sample size, the test date and the mix of addresses used.
- How Unknown or deferred results are counted.
A vendor that can't answer these questions hasn't shown you anything either way. For a broader view of these claims, read are vendor accuracy claims for email verifiers trustworthy, and for independent comparisons see our independent email verifier accuracy benchmark. The how to choose an email verifier checklist turns these questions into a buying process.
Bottom line: A single accuracy number across all providers tells you little about Microsoft 365.
What are the common mistakes with Microsoft 365 verification?
- Deleting every Risky address. In the worked example, that removes 2,775 addresses, including 1,500 that may be real contacts on catch-all domains.
- Trusting one headline figure for every provider. Accuracy on a closed corporate tenant can differ sharply from accuracy on Outlook.com.
- Reading throttling as invalidity. A burst of probes from one source can produce deferrals that look like failures. Spread checks out and retry deferred addresses later.
- Testing with a handful of addresses you know. A few mailboxes can't show a population-level error rate. Use the sample sizes above.
- Mailing catch-all addresses at full volume. A
250can't confirm that the person exists, so gate them with engagement. - Missing the expiry window. Free results last 24 hours and Pro results last 30 days. Export on the day you run the check, or you'll have to run it again and spend deep checks from your monthly quota.
- Ignoring gateways. A domain behind a filter can look Valid on the first pass and bounce later. Track its bounces separately.
- Using a consumer Outlook address as proof of a business contact. It proves the mailbox exists, not that the person still works where your record says.
Bottom line: Most Microsoft 365 verification mistakes come from reading a Risky or Valid result as more certain than it is.
How we compared (and limitations)
This article is based on public documentation: the SMTP and enhanced status code specifications in RFC 5321 and RFC 3463, Microsoft Learn's Exchange documentation, and Google's bulk sender guidelines, which show what mailbox providers expect from bulk senders. The sender-practice guidance from M3AAWG, the messaging industry's technical body, informs the list-hygiene recommendations. We haven't run controlled tests against Microsoft's servers, and we haven't benchmarked any competitor's accuracy.
The worked-example percentages are illustrative. Microsoft's tenant defaults, consumer behaviour and sender requirements change over time, so check current documentation before acting on any specific code or threshold. Unlimited Verifier's 99.5% deep-verification figure is the company's stated number, not an independent result. The sample sizes come from the standard formula for estimating a proportion. You can inspect how the SMTP checks work in the open-source verification engine on GitHub.
Bottom line: Run your own control set on your own Microsoft 365 domains before relying on any accuracy figure, including ours.
Worked example: mixed Microsoft 365 segment
| Segment | Addresses | Valid | Risky | Invalid |
|---|---|---|---|---|
| Business tenants (reject unknown) | 7,000 | 6,450 | 280 | 270 |
| Catch-all business domains | 3,000 | 1,900 | 900 | 200 |
| Outlook.com / Hotmail / Live | 2,000 | 1,100 | 580 | 320 |
| Total | 12,000 | 9,450 | 1,760 | 790 |
Risky share: 1,760 / 12,000 = about 15%. Illustrative figures only; your own mix will differ. Sample each row separately before deciding how to act.
Frequently asked questions
Are email verifiers accurate for Outlook.com addresses?
Email verifiers are less reliable on consumer Outlook.com and Hotmail addresses than on business tenants. Microsoft's anti-abuse controls limit how servers answer mailbox probes, so many results come back inconclusive. Syntax and domain checks still work well, but treat mailbox-level Valid results with caution and confirm with engagement data.
What does Risky mean in an email verification result?
Risky means the verifier could not confirm the mailbox either way. Common causes include catch-all domains that accept any address, throttled servers, and greylisting. Risky addresses may be valid, so they should be resolved with deeper verification or engagement history rather than deleted or mailed at full volume.
Why does a catch-all domain make verification harder?
A catch-all domain accepts mail for any address, so a positive SMTP response does not prove that a specific mailbox exists. The verifier can detect the catch-all setting but cannot judge one mailbox from the server reply alone, which is why such addresses often land in Risky.
How many addresses should I sample to test verifier accuracy?
A random sample of 385 addresses gives a margin of error of about ±5% at 95% confidence. For ±3% at the same confidence, sample 1,068. Sample each segment separately, such as business domains versus consumer Outlook addresses, so one group does not hide problems in another.
Does a Microsoft 365 MX record prove a mailbox exists?
No. A default Microsoft 365 MX record ending in mail.protection.outlook.com confirms that the domain routes mail to Microsoft 365. It does not confirm that a particular mailbox exists or will accept mail. Only the mailbox check, with its tenant-level limits, addresses that question.
Should I remove Risky addresses from my list?
Not automatically. Risky addresses should be held back from full-volume sending and resolved first. Use deep verification where available, check recent engagement, and send a low-volume re-engagement message. Remove addresses that remain unresolved after a set period with no engagement.
Is there an official published accuracy rate for Microsoft 365 verification?
No widely published, provider-level accuracy figure for Microsoft 365 mailbox verification exists that we can verify. Treat any single headline percentage as a claim to test on your own data, and compare verifiers using the same sample and the same definitions of Valid, Risky and Invalid.
What is the difference between a syntax check and an SMTP check?
A syntax check confirms the address is correctly formatted, such as one @ sign and a valid domain pattern. An SMTP check connects to the receiving server and asks whether it would accept mail for that recipient, without sending a message. Syntax is highly dependable; SMTP results depend on server configuration.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.