Skip to content

How to Analyze an Email List by Domain and Provider

Break any list into provider share, top domains, TLD spread and quality signals — then turn the breakdown into segments that behave predictably.

By the Email Extractor Team · Published Sep 5, 2026 · Updated Sep 6, 2026

Two lists of 5,000 addresses can behave nothing alike: one is 80% Gmail, the other spread across 400 company domains. Provider and domain mix shapes deliverability, filtering and engagement — so analyze before you act.

1. Get the breakdown

Open the Email Analyzer and paste your list or drop a file. Analysis runs entirely on-device — provider market share, most common domains, TLD distribution, average local-part length and quality signals (role accounts, disposables, plus-tags) are computed in a local Web Worker and nothing leaves your tab.

2. Interpret the three distributions

  • Provider share — consumer-heavy lists (Gmail, Outlook, Yahoo) face different spam filtering and engagement windows than business-domain lists. Heavy consumer share argues for stricter validation; heavy corporate share argues for company-level segmentation.
  • Top domains — a handful of domains with huge counts means a few organizations dominate your list. Pull the ranked table with the Domain Extractor (subdomains optionally folded to registrable form) and consider per-company messaging or per-domain send pacing.
  • TLD spread — unusual TLD concentrations can signal scraped or generated addresses. Cross-check with the Email Validator: syntax and disposable-provider flags catch the worst of it, though static checks can’t confirm a mailbox exists.

3. Segment, then execute

Turn insight into structure: sort by domain to group each segment physically, convert each group to the format its destination expects (CSV with domain column for spreadsheets, JSON for scripts), and recount with the Email Counter to confirm segment sizes. Analysis tells you what the list is; segmentation decides what happens next.

Common mistakes to avoid

Analyzing a raw, uncleaned list. Invalid rows, pasted headers, and stray text fragments inflate distinct-domain and TLD counts. One malformed line like contact@acme without a TLD can appear as its own domain and distort the long tail. Always pass the source through the Email Cleaner first, then analyze the cleaned output so provider share and top-domain rankings reflect real mailboxes.

Counting subdomains as separate companies. Without folding, mail.acme.com, uk.acme.com, and acme.com show up as three domains, which fragments account-level counts and hides concentration risk. Enable subdomain folding in the Domain Extractor when your question is “how many people per company,” and disable it only when you are debugging routing or regional subdomains specifically.

Treating provider share as a deliverability verdict. A list that is 70% Gmail does not automatically mean poor inbox placement, and a corporate-heavy list is not automatically safe. Provider mix tells you which filters and engagement patterns to prepare for; actual risk comes from role accounts, disposables, stale addresses, and complaint history. Pair every analysis pass with the Email Validator and the hygiene checklist in Email List Hygiene & Validation.

Analyzing once and never re-checking. Lists drift every time sources are merged, events are appended, or old exports are reused. A domain breakdown from last quarter will not catch this month’s disposable spike or a newly dominant client domain. Re-run the Email Analyzer after each merge, import, or cleanup pass and compare provider share over time.

Pro tips and workflow recipes

Recipe 1: B2B versus B2C split in ten minutes. Paste the list into the Email Analyzer and note the consumer-provider share. Then open the Domain Extractor to pull the ranked domain table with counts. Copy Gmail, Outlook, Yahoo, and iCloud addresses into one segment and everything else into a second segment, sort by domain to group each half, and confirm sizes with the Email Counter. You now have two lists with different copy, cadence, and success metrics.

Recipe 2: Pre-send risk triage. Run the analyzer and record three numbers: disposable count, role-account count, and unusual-TLD concentration. Send any segment where disposables exceed 1–2% through the Email Validator and review Disposable Temporary Email Detection. Quarantine role addresses using the guidance in Role-Based Email Addresses & Outreach, then clean and recount before scheduling.

Recipe 3: Per-domain pacing export. After analysis shows three or four dominant corporate domains, sort the list by domain so each company’s addresses sit together. Use the Email Converter with CSV output and the domain column enabled to produce a spreadsheet where each row carries its address and domain. Filter per company, stagger sends per domain to avoid triggering per-domain rate limits, and keep a control segment for the long tail.

Troubleshooting

  • Symptom: one giant “unknown” or “other” provider bucket. Cause: pasted headers, URLs, or malformed rows are being parsed as domains. Fix: run the list through the Email Cleaner to drop invalid lines, then re-analyze the cleaned output only.
  • Symptom: top-domain counts do not match spreadsheet pivot counts. Cause: case differences (Acme.com versus acme.com), trailing dots, or unfolded subdomains. Fix: normalize with the Email Deduplicator on case-insensitive mode, enable subdomain folding in the Domain Extractor, and recount.
  • Symptom: sudden spike in rare TLDs. Cause: newly appended scraped source or generated addresses. Fix: isolate that source batch, validate it separately with the Email Validator, and check it against the steps in Reduce Email Bounce Rate before merging.
  • Symptom: analysis looks different on every run. Cause: you are analyzing a different input each time — pre-clean versus post-clean, or full list versus a filtered copy. Fix: freeze a simple pipeline: extract, clean, dedupe, analyze, then save the analyzed file. Verify counts with the Email Counter so each run starts from the same baseline. All processing stays in-browser in a Web Worker, so re-running is free and private — confirm in DevTools Network tab that nothing is uploaded.

FAQ

How do I check what percentage of my email list is Gmail, Outlook, or Yahoo?

Paste the list into the Email Analyzer. Provider market share is computed locally and shows consumer versus corporate split in seconds. For an exact per-domain count, pull the ranked table from the Domain Extractor and divide each provider’s count by the unique total from the Email Counter.

How do I find the top domains in a large email list?

Use the Domain Extractor to generate a unique-domain table with occurrence counts, then sort descending. Enable subdomain folding to group mail.company.com under company.com. Export the table or convert it to CSV with a domain column for pivot analysis in Excel or Sheets.

Why does my email list have hundreds of domains with only one address each?

A long single-occurrence tail is typical of event signups, scraped sources, or multi-year merges. It is not automatically bad, but it deserves validation because typo domains and throwaway addresses hide there. Run the tail through the Email Validator and follow Email List Hygiene & Validation before mailing it.

Can I analyze email domains without uploading my list anywhere?

Yes. This site’s analyzer, extractor, and counter all run 100% in-browser using a local Web Worker. Your addresses never leave the tab, which you can verify by opening DevTools, watching the Network tab during analysis, and seeing zero uploads. That makes domain analysis safe for client lists and internal CRM exports.

What to do next

Turn the breakdown into sends: pull company segments with the Domain Extractor, group them with the Email Sorter, and verify segment sizes with the Email Counter. Then deepen the workflow with Find Company Emails by Domain in a List and Email List Hygiene & Validation.

Last reviewed: Sep 6, 2026 · About our testing

Put it into practice

Run today's steps yourself — free, private, no signup.

Open the Email Analyzer →