Article
Email Verifier Accuracy on Gmail vs Outlook Addresses: What to Measure
By Unlimited Verifier Team ·

Summary
Email verifiers are usually more reliable on Gmail addresses than on Outlook.com, Hotmail, Live and Microsoft 365 addresses, because providers answer mailbox probes differently and custom domains are configured by their admins. The gap varies by tool, so measure false positives separately for each provider group using roughly 1,500 Valid-labelled addresses per group.Email verifiers usually give more dependable results on Gmail addresses than on Outlook.com, Hotmail, Live and Microsoft 365 addresses, because Google and Microsoft answer mailbox probes differently and configure their domains differently. The size of the gap varies by tool, so measure false positives provider by provider, using about 1,500 Valid-labelled addresses per group.
This is the Gmail-and-Outlook deep dive from our email verifier accuracy pillar. It explains why the results differ, how to measure the gap on your own list, and what to do with each result.
Quick answer
- Gmail consumer addresses are usually the easiest group to verify with confidence. Outlook.com, Hotmail, Live and MSN addresses more often produce deferrals and ambiguous answers. The gap varies by tool, so test it.
- Domain setup matters as much as brand. Google Workspace and Microsoft 365 custom domains can be configured to accept mail for any address (catch-all), so a Valid-looking result there may prove nothing about the mailbox.
- Measure false positives per group, not blended. About 1,500 Valid-labelled addresses per group gives a 1% false-positive estimate within ±0.5 points.
- Blended accuracy hides the gap. In the illustrative example below, Outlook-family addresses are 20% of the list but about 42% of expected bounces from Valid results.
- Unlimited Verifier sorts results into Valid, Risky and Invalid, with unlimited standard verification on every plan and 25,000 deep verifications a month on Pro for the uncertain subset.
Why do email verifiers get different results for Gmail and Outlook addresses?
Most verifiers check a mailbox by opening an SMTP conversation with the recipient's server and asking whether it will accept a recipient (the RCPT TO step). RFC 5321 defines this exchange and lets servers limit what they reveal about which addresses exist. Providers have good reason to limit that answer, because harvesting valid addresses is a common spam tactic.
Three layers combine to create the difference:
- The provider's probe response. A server may accept, reject with a permanent
5xxcode, or defer with a temporary4xxcode. Permanent rejections carry enhanced status codes such as5.1.1(bad destination mailbox), defined in RFC 3463. - The domain's configuration. gmail.com and outlook.com mailboxes are run by the provider. Custom domains on Google Workspace or Microsoft 365 are run by the customer's admin, who decides whether unknown addresses are rejected or silently accepted.
- The verifier's own behaviour. Concurrency, retry logic and the reputation of the probing IP all shape what a provider returns. Probing hard from one IP can trigger throttling that looks like a mailbox problem, so the same list can score differently on two runs. Why different email verifiers give different results explores this in more depth.
Bottom line: The gap comes from how providers answer probes and how each domain is configured, and a verifier's own probing can widen it.
What does accuracy mean for an email verifier?
Accuracy has three parts, and a blended percentage hides the one that matters most for sending.
- False positive: the verifier says Valid, but the address bounces. This is the costly error because it damages sender reputation. What a false positive is in email verification covers the measurement.
- False negative: the verifier says Invalid, but the address would have received mail. This costs reach rather than reputation.
- Inconclusive: the verifier cannot reach a confident answer, often because of a deferral. Tools label these differently, so check how yours handles them.
Blending misleads in a predictable way. Suppose a tool is tested on 40,000 addresses, 32,000 Gmail and 8,000 Outlook, and is correct 99% of the time on Gmail and 88% of the time on Outlook (both figures hypothetical). Overall accuracy is (0.99 × 32,000 + 0.88 × 8,000) ÷ 40,000 = 96.8%. That headline looks strong, yet it conceals an 11-point gap on the Outlook addresses. For the broader picture, read how accurate email verification is in general.
Bottom line: Report accuracy per provider group and per error type. One blended percentage will mislead you.
How do Gmail and Outlook addresses differ in practice?
The table below summarises common patterns from public documentation and practitioner reports. Providers change their systems without notice, so treat it as a hypothesis to test.
| Address type | Typical probe behaviour (reported) | Main accuracy risk | What to do |
|---|---|---|---|
| Gmail consumer (@gmail.com, @googlemail.com) | Usually a clear accept or reject at normal volumes; heavy probing can trigger deferrals | Deferrals misread as unknown | Lower concurrency; retry deferred addresses later |
| Google Workspace custom domain | Depends on the admin's configuration | Catch-all domains accept any address, so a probe proves nothing about the mailbox | Check the catch-all flag; use a small send test |
| Outlook.com, Hotmail, Live, MSN | Microsoft's anti-abuse systems can defer or throttle repeated connections | More inconclusive results and occasional false Valid | Retry; run a per-group false-positive test |
| Microsoft 365 custom domain | Depends on the tenant's settings; some accept mail for any address | Catch-all tenants look Valid | Check the catch-all flag; treat as Risky for first sends |
The dot and plus rules are Gmail-specific. Gmail ignores periods in the username and anything after a + for delivery, so j.smith+news@gmail.com and jsmith@gmail.com reach the same inbox. Normalise Gmail addresses before verifying, or one mailbox gets counted twice and your rates shift. Don't apply the same rule to Outlook-family addresses without checking first.
Catch-all is the silent distortion. A catch-all domain accepts every address, so a Valid answer on it confirms nothing about the individual mailbox. That is why catch-all detection is a separate check from mailbox confirmation. The Catch-all email verification page covers how Unlimited Verifier flags these domains. For the hosted case in more depth, see our Microsoft 365 accuracy guide.
Bottom line: Consumer Gmail is usually the most straightforward group. Consumer Outlook and catch-all custom domains need separate treatment.
Which is more accurate, Gmail or Outlook?
There is no universal answer. Most teams find Gmail consumer addresses easier to verify with confidence, and Outlook-family addresses produce more inconclusive results and more false Valid results. The size of the difference depends on your tool, how it probes and what your list contains.
Be cautious with headline numbers. Vendors often publish a single blended accuracy figure, and the test sets behind it are rarely disclosed. Our guides on whether 99% accuracy claims hold up and whether vendor accuracy claims are trustworthy explain what to ask for. An independent email verifier accuracy benchmark can help you shortlist tools, but check whether it reports provider splits, because many do not.
When you compare products, the best email verification tools roundup and our buyer's checklist give a framework.
Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, and it is not broken down by provider. Test it on your Gmail and Outlook addresses before relying on it. The open-source verification engine on GitHub lets you read how its checks are implemented, which helps you judge what a probe can and cannot prove.
Bottom line: Expect Gmail to be the easier group and Outlook to carry more risk, then confirm it with a per-provider test on your own data.
How do I measure Gmail and Outlook accuracy separately?
Start with ground truth, because a verifier cannot grade its own answers. Choose the source that gives you real outcomes.
| Ground-truth source | What it tells you | Main limitation | Best use |
|---|---|---|---|
| ESP bounce and delivery logs | Which addresses actually hard-bounced or delivered | Covers only addresses you have mailed | Primary source for false-positive and false-negative rates |
| Seed mailboxes you control | Known exists or doesn't-exist outcomes | Tiny sample; provider treatment of test accounts may differ | Sanity-checking one provider's responses |
| Vendor accuracy claim | A headline figure | Test set, provider mix and error split are usually undisclosed | Starting hypothesis only |
| Independent benchmark | A third-party test under stated conditions | May predate provider changes | Shortlisting before your own test |
Then follow this framework. Each step produces a number you can act on.
- Build outcomes from your send history. Use addresses you have already mailed. Your ESP logs show which hard-bounced (often
5.1.1) and which delivered. Addresses you have never mailed have no outcome, so they cannot measure accuracy. - Split by provider group. Create Gmail consumer, Outlook-family, custom domain and other groups. Normalise Gmail first.
- Size each group. The standard formula is n = z² × p(1 − p) ÷ E². At 95% confidence, a 50% rate measured to ±2 points needs about 2,400 addresses. A 1% false-positive rate to ±0.5 points needs about 1,520 Valid-labelled addresses per group, and a 2% rate to ±1 point needs about 750. How many emails to use when testing a verifier covers the trade-offs.
- Use identical settings for every group. If you change concurrency or retry rules between groups, you measure your settings rather than the providers.
- Calculate three rates per group.
- False-positive rate = bounced ÷ Valid.
- False-negative rate = previously delivered addresses now marked Invalid ÷ previously delivered addresses. This uses history you already have, so you never need to send to an address the verifier called Invalid.
- Risky share = Risky ÷ total, reported separately.
- Set a sending rule per group. Gmail Valid can enter your ramp directly, while Outlook Valid enters a smaller first wave.
Bounce data measures reputation risk, not inbox placement. A delivered message is not proof of where it landed, so read whether a Valid result means the email will be delivered before equating the two.
Bottom line: Measure false positives per group against your own bounce history, with a sample large enough to trust.
How do I run a Gmail vs Outlook accuracy test in Unlimited Verifier?
Allow about an hour for a list of a few thousand rows.
Export your ground-truth file. Create one CSV with the email column, an ESP outcome column (Bounced or Delivered) and a provider-group column.
Create an account. Sign up on the Free plan for a pilot. Free allows 25 lists a month of up to 150 emails each, so one 1,500-address group fits as ten 150-address lists. Three groups of that size (30 lists) would exceed the 25-list allowance, so a full test needs Pro, which allows unlimited lists of up to 25,000 emails each. Check email verification pricing on the plans page before you commit.
Split the file by group. Filter the sheet to each provider group and save one CSV per group. Keep the outcome column in a master file so you can join results back later.
Upload each file. Upload and verify a list accepts CSV or Excel files up to 10MB and detects the email column automatically.
Read the three buckets. Valid addresses form your false-positive test set. Invalid addresses are removed from sending. Risky addresses (catch-all, disposable and role-based) are held for separate testing.
Export the results the same day. Export as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro, so don't wait for a later download.
Join results to outcomes. In your master file, look up each address's verdict, then compute the Outlook false-positive rate. Column A is the group, column C the verdict and column D the ESP outcome:
=COUNTIFS(A:A,"Outlook",C:C,"Valid",D:D,"Bounced")/COUNTIFS(A:A,"Outlook",C:C,"Valid")Change "Outlook" to "Gmail" for the Gmail rate.
Repeat for each group, then script it. Record each group's rates. For recurring checks, the Email verification API lets you run the same test from your own scripts. API access is included on Pro, at 100,000 emails a month.
For a quick read on one address, such as a VIP contact returned as Risky, the free email checker gives an immediate answer.
Bottom line: Split by provider, verify with identical settings, export the same day, and compute false positives per group from your own outcomes.
Worked example: a 60,000-address list split by provider
This example is illustrative. The domain counts, verdict splits and false-positive rates are assumed for the arithmetic, not measured from any tool. The plan limits and prices are real.
The scenario: A SaaS company holds a 60,000-address list for a product-update campaign. Its ESP logs show Outlook-family addresses bounce more often than Gmail ones, so it wants the gap quantified before sending. Teams running email verification for ecommerce and SaaS programs often face this same split.
Step 1: Split the list. Each file stays under Pro's 25,000-email cap:
| File | Addresses | Valid | Risky | Invalid |
|---|---|---|---|---|
| Gmail consumer | 24,000 | 20,400 (85%) | 2,400 (10%) | 1,200 (5%) |
| Outlook-family consumer | 12,000 | 8,400 (70%) | 2,400 (20%) | 1,200 (10%) |
| Custom domains and other | 24,000 | 16,800 (70%) | 4,800 (20%) | 2,400 (10%) |
| Total | 60,000 | 45,600 | 9,600 | 4,800 |
Step 2: Estimate expected bounces from Valid results. Assume the test measured these false-positive rates:
- Gmail: 0.6%, so 20,400 × 0.006 ≈ 122 bounces
- Outlook: 2.2%, so 8,400 × 0.022 ≈ 185 bounces
- Custom domains: 0.8%, so 16,800 × 0.008 ≈ 134 bounces
The total is about 441 bounces from 45,600 Valid addresses, or roughly 0.97%. Outlook is 20% of the list but about 42% of those bounces (185 ÷ 441). Its false-positive rate is about 3.7 times the Gmail rate. A blended test would show the 0.97% total and miss that concentration entirely.
Step 3: Spend deep verifications where they matter. Pro includes 25,000 deep verifications a month. The company deep-verifies the 12,000 Outlook-family addresses plus 6,000 Microsoft 365 custom-domain addresses from the third file, which is 18,000 and leaves 7,000 for re-tests. Standard verification of all 60,000 is included on every plan.
Step 4: Cost. One month of Pro at $29 covers the job. That is $29 ÷ 60 thousand addresses ≈ $0.48 per 1,000. Pro billed annually is $25 a month, but a one-off clean-up doesn't need a year's commitment.
Step 5: Plan the send.
- Gmail Valid (20,400) enters the engagement-ranked ramp first.
- Outlook Valid (8,400) enters a smaller first wave, with bounce checks after each send.
- Risky (9,600) waits until catch-all and disposable addresses have been re-tested or excluded.
- Invalid (4,800) is suppressed permanently.
Bottom line: A 60,000-row list can be split, verified and planned for about $0.48 per 1,000 addresses, and the split reveals a risk that a blended figure hides.
What should you do with each Gmail and Outlook result?
Each result maps to one action. Use this table as your decision guide.
| Result | Typical cause | Action |
|---|---|---|
| Valid, Gmail consumer | Clear accept from the provider | Send in your engagement-ranked ramp |
| Valid, Outlook-family | Clear accept, but a higher false-positive rate in your test | Smaller first wave; check bounces after each send |
| Risky, catch-all custom domain | Domain accepts any address, so the mailbox can't be confirmed | Hold for a small test send or exclude |
| Risky, disposable or role-based | Category flagged by the verifier | Hold back; exclude role addresses like info@ from personal campaigns |
| Inconclusive after retries | Persistent deferral or throttling, depending on your tool's labels | Retry after a delay; hold if still unresolved. See why verifiers return so many unknowns |
| Invalid | Mailbox does not exist | Suppress permanently |
Keeping these rates stable takes ongoing work. Email list maintenance best practices covers the schedule, and real-time validation at signup catches bad addresses before they enter your list. Ongoing email verification compliance and hygiene also keeps your records defensible. Teams that want this logic inside their own systems can follow email verification API and automation patterns.
Bottom line: Each result maps to one action, and the riskiest groups get the smallest first sends.
What are the most common mistakes when comparing Gmail and Outlook accuracy?
- Relying on a blended accuracy figure. As the 96.8% example showed, a headline number can hide an 11-point gap.
- Testing with too few Outlook addresses. To estimate a 2% false-positive rate within ±1 point, you need about 750 Valid-labelled addresses in that group. Fifty addresses give you a guess.
- Treating inconclusive results as invalid. Many are temporary deferrals, so retry before you remove an address.
- Probing too fast. High concurrency from one IP can trigger throttling and skew results on any provider.
- Forgetting custom domains. Google Workspace and Microsoft 365 addresses can look Valid while accepting every address, so check the catch-all flag.
- Skipping Gmail normalisation. Counting
j.smith+news@gmail.comandjsmith@gmail.comseparately inflates your sample and muddies the rates. - Using addresses you have never mailed as ground truth. They have no outcome, so they cannot measure accuracy.
- Sending to Invalid addresses to test the verifier. That damages your reputation for a measurement you can take from history instead.
- Equating Valid with inbox placement. A Valid result is a mailbox answer, not a promise about where mail lands.
Bottom line: Most errors come from blended metrics, rushed probing and ground truth that doesn't exist.
How we compared (and limitations)
This article draws on public documentation: the SMTP standards in RFC 5321 and RFC 3463, and the bulk-sender guidance in Google's sender guidelines. For data on your own mail sent to Gmail, Google Postmaster Tools is the place to look, and for industry practice on mail abuse, see the guidelines from M3AAWG. We also drew on widely reported practitioner patterns. We have not run controlled tests against Gmail or Microsoft's systems, and we have not benchmarked any verifier across providers.
The worked example uses hypothetical domain counts, assumed false-positive rates and illustrative verdict splits, so its numbers show the arithmetic rather than real results. Provider behaviour changes without notice. Vendor figures, including Unlimited Verifier's 99.5% deep-verification accuracy, are the company's own claims until you check them against your data.
Bottom line: Treat the patterns as hypotheses to test, and let your own per-provider measurements decide.
Worked example: blended accuracy hides the gap
| Group | Share of list | Share of expected bounces from Valid results |
|---|---|---|
| Gmail consumer | 50% | 25% |
| Outlook family | 20% | 42% |
| Custom domains | 30% | 33% |
Illustrative only. Outlook-family addresses are 20% of the list but about 42% of expected bounces from Valid results, so a blended accuracy figure would conceal the main risk. Measure each group separately with roughly 1,500 Valid-labelled addresses per group.
Frequently asked questions
Are email verifiers more accurate for Gmail than Outlook?
Usually yes. Gmail consumer addresses tend to return clearer answers, while Outlook.com, Hotmail and Microsoft 365 addresses more often produce deferrals or ambiguous results. The size of the gap depends on the tool, so test it on your own list rather than relying on a general claim.
Why does my verifier mark Outlook addresses as Risky?
Outlook-family servers frequently answer probes with temporary 4xx deferrals or refuse to confirm specific mailboxes. The verifier cannot get a definitive answer, so it labels the address Risky. Retrying later or running a deeper check on that subset usually resolves more of these results.
What is a catch-all domain and why does it affect verification?
A catch-all domain accepts mail for any address, whether or not the mailbox exists. A verifier probing such a domain gets a positive answer for everything, so a Valid result proves little. Google Workspace and Microsoft 365 domains can be set up this way by their admins.
How many addresses do I need to measure false positives?
Around 1,500 Valid-labelled addresses per provider group gives a false-positive estimate within about ±0.5 percentage points at a 1% rate. Smaller samples work for a rough check but leave wider margins of error.
What is a false positive in email verification?
A false positive is when the verifier labels an address Valid but it bounces on send. It is the costly error because it damages sender reputation and wastes sending capacity, so it matters more than overall accuracy percentages.
Why does the same list give different results on different days?
Verifier concurrency, retry logic and the reputation of the probing IP all affect what providers return. Probing aggressively can trigger throttling that looks like a mailbox problem, so results can shift between runs. Spacing requests and retrying deferred addresses reduces this.
Should I remove all Risky addresses before sending?
Not automatically. Risky means the verifier could not confirm the mailbox. Many teams send to Risky addresses cautiously or run them through a deeper verification pass, then decide based on engagement history and the cost of a bounce for that segment.
Does RFC 5321 let servers hide whether a mailbox exists?
Yes. RFC 5321 defines the SMTP recipient check but allows servers to limit what they reveal, and many providers do so to reduce address harvesting. This is one reason verifiers cannot always confirm a mailbox with certainty.
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.