Email Counter — Count Unique Emails, Domains & TLDs

The numbers that actually describe a list

Raw line counts lie. They include duplicates, header rows, blank lines, N/A placeholders and role addresses that will never engage. The counter reports the figures stakeholders should see instead: total syntactically valid matches including duplicates, unique count after collapsing, duplicates removed (the exact difference), distinct domains and TLDs, plus quality counters for role accounts and disposable providers with a full per-domain breakdown table.

Those six numbers answer the only question that matters at intake — how big is this list, really? — and they do it from raw pasted text in one step, no prior extraction pass needed. Paste anything from a chat log to a scraped page; the counter extracts, normalizes and tallies together.

Total vs. unique vs. deliverable

Total counts every valid-shaped match including repeats — the ceiling. Unique collapses case-insensitive duplicates — the working size. Deliverable is uniques minus invalid, disposable and role addresses you choose to exclude — the sendable size. Reporting total as list size overstates reach; reporting deliverable without showing the math hides quality work. Report all three with the duplicate rate attached.

A healthy content-download list might show 5–10% duplicates and under 3% disposables. Merged legacy exports routinely show 20–30% duplicates; purchased or scraped lists invert the quality counters entirely. The per-domain table then shows whether the uniques concentrate on a few domains (key-account leverage) or scatter across hundreds (broad-market reach).

• Total → ceiling, includes every repeat
• Unique → working size after collapsing
• Deliverable → uniques minus risky and invalid
• Duplicate rate → data-pipeline health signal

Using counts to find pipeline bugs

Track duplicate rate over time, not just per list. A sudden jump from 4% to 18% after a site change points at a double-firing form or a sync loop — fixing the source beats re-counting forever. A disposable share climbing after a giveaway means the incentive attracted throwaways; quarantine that cohort before it drags engagement rates.

TLD spread adds a second diagnostic: an unexpected surge in an unusual TLD often marks bot signups or a mis-targeted campaign spilling across regions. The counter surfaces it in seconds, locally, before the bad cohort reaches your mail platform's billing and reputation systems.

Counting without uploading

Counts feel harmless until the thing being counted is a sensitive HR export or a client roster. Here extraction and tallying happen in a Web Worker inside your tab with no artificial cap beyond browser memory and the 30 MB per-file guard — large enough for serious lists, private enough for serious data. Export the breakdown as CSV when stakeholders want the table, not just the headline.

Keep reading