Driftwood Provisions

Master Subscriber List · June 2026

49,067

To Keep

47.5% of list

28,702

To Monitor

27.8% of list

25,478

To Suppress

24.7% of list

103,247 total emails8,341 unique domains

An address can carry more than one label (e.g. Accept-All + Role Account), so the per-label counts in the sections below will add up to more than the bucket totals above. The bucket totals count each address once.

Moderate

out of 100

List Health Score

Your list has some quality concerns. Follow our recommendations below before sending. The score reflects both the keep rate and the composition of what is being suppressed. A list with mostly typos scores differently than one with mostly spamtraps.

Credits Used

102,319 of 150,000

Remaining

47,681

The guarantee: if a specific address we marked valid bounces, and the bounce was not caused by a blocklist hit or your sender reputation, you get 2x credits back for that address. Not the full purchase. Just the addresses we got wrong. We rarely owe these refunds, which is exactly why we offer the guarantee.

✦

Heads up: 2 of the labels below were moved off their default verdict for your situation.

Spam Report Risk (normally Monitor) is in Suppress for the warmup. One complaint spike can undo weeks of reputation building.

Role Account stays in Monitor with a specific engagement-tracking note for your B2B wholesale segment. info@ and sales@ are often the real inbox for small-business contacts.

Look for the "✦ Adjusted for you" badges below.

Key Insights

⚠

Roughly a quarter of this list should not be mailed

The suppress segment breaks down into 11,420 undeliverable addresses, 5,903 known typo or trap addresses, 3,187 instant disposables, 2,614 expired domains, 1,451 reputation-risk addresses, 1,000 short-lived disposables, plus smaller categories (mailbox full, parked domains, spam-report history). Sending to these will generate hard bounces, may trigger spamtraps, and damages your sender reputation across providers.

⚠

Legacy ISP addresses have the lowest keep rates

sbcglobal.net (29% keep), earthlink.net (22% keep), att.net (30% keep), and comcast.net (35% keep) are frequently abandoned and roll over into spamtraps. These addresses are technically deliverable, but the people behind them may have moved on years ago.

💭

Your own domain looks clean, but check engagement before trusting it

driftwoodprovisions.com addresses (internal/corporate) have a 71% keep rate, the best score in the list. But validation only confirms the mailboxes exist. It does not tell us whether the people behind them actually open your emails. If these employees were added to the list months ago and have never opened a campaign, they are deadweight that drags engagement metrics down. Send a test, check the opens, and remove anyone who has been on the list 30+ days without engaging. Do not let your own team be your least engaged segment.

ℹ

Plan warmup per provider, not per list

Google and Microsoft handle 73,000 of your 103,247 addresses. Each mailbox provider tracks your sending reputation independently, which means warmup has to happen at the provider level, not at the list level.

The trap: if you send 5K Monday, 10K Tuesday, 15K Wednesday from a randomly-shuffled pool, your own dashboard shows a clean ramp. But to each individual provider, the pattern can look erratic.

Microsoft might see 800 → 3K → 2K (a spike then a dip). Google sees 2K → 4K → 8K (smooth). Yahoo sees 1K → 2K → 5K. Microsoft does not know what Google is seeing. To them, you look unpredictable.

The fix: plan daily volume per provider explicitly. Google goes 2K → 3K → 5K, Microsoft goes 800 → 1.5K → 2.5K, Yahoo goes 500 → 1K → 1.8K. Each provider sees its own smooth ramp, even when the total list send keeps growing. We built a per-provider warmup plan for you in the section below.

If your segments change: if you decide to keep segments we suggested suppressing (or drop segments we suggested keeping), the per-provider numbers shift. Let us know which changes you are making and we will rerun the warmup plan with the corrected segments. You should not have to recalculate by hand.

Suppress: Remove Before Sending

25,478 emails (24.7% of list)

Can't Receive Email11,420 emails

Mailbox does not exist, domain has no mail server, or server permanently rejects. Sending to these addresses will hard bounce every time.

Remove completely. Sending to these damages your sender reputation.

Invalid/Typo/Trap5,903 emails

Known typo domain, syntax error, or suspected spamtrap address. Includes misspelled domains (gmial.com, yhaoo.com) and addresses that match known trap patterns.

Remove completely. Learn from this: if a lot of these came from a single source (a recent import, a partnership list, a scraped batch), that source is contaminated. Do not use it again without validating the rest of it first. For ongoing signups, add double opt-in and (if possible) real-time email validation on the form itself so typos get caught before they ever hit the database.

Disposable - Instant2,187 emails

Refresh-based disposable address with no persistent inbox (Guerrilla Mail, Mailinator, etc.). Email will never be read by the original person.

Remove completely. Learn from this: disposable addresses on your list mean your signup form is letting them through. Block known disposable domains at the form level (most modern signup services support this) and add CAPTCHA or honeypot protection to slow down automated signups. Worth thinking about WHY people are using disposables to access your offering. If it is gated content or a discount code, the offer is attracting deal-seekers, not subscribers.

Disposable - Short-lived1,000 emails

Temporary email address that expires within minutes to hours. The person behind it used a throwaway to sign up without committing.

Remove completely. Same prevention strategy as Disposable - Instant: block at the form level and check what your signup incentive is attracting.

Expired Domain2,614 emails

Domain registration has lapsed. The owner may have abandoned it, may have lost it to a squatter, or in the worst case the expired domain may have been re-registered as a spamtrap. Sending here is high-risk regardless of which case applies.

Remove completely. No re-validation schedule needed here. If the original owner renews, the address will start working again on its own and your next clean will pick it up. There is nothing useful you can do in the meantime besides not sending to it.

Reputation Risk1,451 emails

Address associated with spam reporting, abuse complaints, or known bad actors. Sending here risks triggering blocklist sensors.

Remove completely. Learn from this: if a chunk of these came from one source (lead-gen partner, purchased list, scraped batch), that source is putting your sending reputation at risk. Pause and check the strategy of that source. It is attracting problem contacts, and even the addresses that look fine right now may turn into the next batch of issues. Worth understanding what that source is doing differently before you keep using it.

Spam Report Risk3,109 emails✦ Adjusted for you

Address has a history of marking emails as spam. Normally this would be in Monitor so you can decide. For your situation, we moved it to Suppress.

Suppressed for this send. Revisit after your sending reputation stabilizes.

Adjusted for your sending context

You are re-engaging a dormant segment. During warmup, even a small complaint spike can undo weeks of reputation building. Once your sending reputation stabilizes, we can revisit and move some back to Monitor.

Mailbox Full824 emails

The recipient's inbox is over quota and cannot accept new messages. Could be temporary, but a persistently full inbox almost always means the person stopped actively managing the address. Also worth considering: someone with a full primary inbox may have given you an old or throwaway email at signup because they did not really want your emails in the inbox they actually use.

Suppress for this send. Do not waste time analyzing 6-month-old data on each address individually. Either re-validate in 60-90 days, or just abandon them and spend the time looking at where they signed up from. If a specific source produces a lot of full-mailbox addresses, the form is probably attracting people who did not really want the subscription.

Parked Domain413 emails

Domain shows a 'parked' or 'for sale' page instead of a real website. The domain owner is gone, and the address has nowhere to land. No legitimate inbox exists behind it.

Remove completely. There is no scenario where a parked-domain address is worth keeping. High bounce risk and high chance of being recycled into a spamtrap. Learn from this: these usually come from old imports or scraped lists where the domains were live at the time. If you can identify the source batch, the rest of that batch is probably aging the same way, worth re-validating.

Monitor: Send With Awareness

28,702 emails (27.8% of list)

Accept-All12,847 emails

These addresses are on mail servers that accept every email without verifying the mailbox exists. You will not get a bounce if the address is wrong. Bad ones just silently disappear.

Segmented and tagged. Send to them, but be smart about how you read engagement. Open rates are not equally reliable across providers. Apple Mail Privacy Protection (MPP), which most iCloud and me.com users have enabled, pre-fetches images for every received email regardless of whether the user opens it. That inflates opens on Apple-heavy segments: a 100% open rate from those addresses does NOT mean 100% of those people actually saw the email. Some providers over-report, some under-report. Clicks, replies, and unsubscribes are more reliable signals than opens. If a domain consistently shows 0% clicks across multiple sends, those addresses are likely dead. But avoid writing off addresses based on open rate alone, especially in Apple-heavy segments.

Saturated Inbox6,218 emails

This person receives a high volume of email. Your message competes with dozens of others for attention. Engagement tends to be lower.

For inbox-overloaded subscribers, sending less helps you stand out. Build a high-engagement-only segment for these contacts and hit them only with what they actually want, not every campaign. Best time-of-day and subject-line optimization matter more here than in your normal segments.

Role Account4,331 emails✦ Adjusted for you

Shared mailboxes like info@, sales@, support@. The person reading it may change over time. For most senders these are Monitor, but your wholesale contacts use these as primary addresses.

Track engagement per role address. Calculate the average duration each role account stays engaged before dropping off. That gives you a window. Before that drop window hits, send a deliberate re-engagement touch so the new person behind sales@ has context for why they are getting your emails. Make the unsubscribe and contact options obvious in every send, so when an employee change happens, the new reader has an easy out instead of hitting the spam button. Spam complaints from role-account turnover are one of the most preventable reputation losses.

Adjusted for your sending context

Many of your wholesale contacts use info@ and sales@ as their primary business inbox. We kept these in Monitor instead of flagging them as risky. Watch for engagement drops that signal the person behind the address has changed.

Compromised Address2,404 emails

These addresses showed up in known public data breaches. The address itself is still real, but a leaked address often gets abandoned by the owner (who moves on to a new one) or becomes a target for bad actors trying to log into other services with reused passwords.

Send normally for now, but watch for unusual bounce patterns from this segment over time. Learn from this: if a high percentage of your full list has been in breaches, it usually means these contacts entered your list through a source that itself was breached at some point. Worth knowing if you bought a list, inherited contacts from an acquisition, or imported from a partner system. The original collection point is the real issue, not your list hygiene today.

Domain Expiring Soon154 emails

Domain registration is within 30 days of expiry. Most domains auto-renew and the address will keep working fine. The flag is here so you have visibility, not because you need to act on it.

No action needed. Most of these will auto-renew. The few that do not will organically start hard-bouncing once their domain lapses, and you will pick that up on your next clean or from bounce events. There is no signal a spam filter can use to penalize you for a future expiry. At send time, the domain is valid, so no reputation hit.

Legacy Inbox1,847 emails

ISP email addresses from providers that were acquired, merged, or wound down years ago (sbcglobal.net, earthlink.net, att.net, verizon.net, bellsouth.net). The address still routes through whoever owns the brand now, but the person behind it almost certainly moved to a primary inbox elsewhere a long time ago.

Segment these together and track engagement and ROI over time. They still receive email, but engagement is often a fraction of your normal audience. If this segment consistently underperforms your average open and click rates across multiple sends, it is dead weight dragging down your overall metrics. Prune it. Some senders find a small core of these addresses are still engaged (people who genuinely never switched), and that is fine to keep. The point is to not assume the whole segment is alive just because it does not bounce.

Suspicious Signup1,102 emails

Signup patterns that look auto-generated or fake. All-numbers usernames, repeated characters, single letter plus digits. The address is technically valid, but the pattern suggests a bot, throwaway, or someone gaming a signup form for a discount code.

Worth a human look. If you recognize the patterns as customers, keep them. If they look fake, suppress. Learn from this: high counts of suspicious signups mean your form lacks basic bot protection (CAPTCHA, honeypot fields, rate limiting). If your signup incentive is a discount code or gated content, the form is attracting deal-seekers who will never engage. Consider gating the incentive behind email confirmation instead.

A few examples

user1234567@gmail.com

All numbers in the local part (no letters at all). Often auto-generated or fake.

xxxxxx@hotmail.com

Repeated character pattern. Almost always a placeholder, bot, or test entry.

asdfgh@protonmail.com

Keyboard-walk pattern. Common throwaway signup.

12345abc@outlook.com

Number-heavy with trailing letters in a non-name pattern. Possible auto-generated signup.

Informational Labels

· 4 context signals · click to expand

These are context signals, not action items. We tag them so you know what you are looking at.

Privacy Email412 emails

Forwarding addresses from privacy services (Apple Hide My Email, Firefox Relay, etc.). The person is reachable, but the address may stop forwarding if they revoke it.

Send normally. These are real people who chose privacy, not disposable users.

Academic312 emails

University and educational institution email addresses (.edu, .ac.uk). These contacts may be students or staff. Student addresses expire after graduation.

Send normally. Monitor for bounce rate increases around graduation seasons.

Site can't be reached81 emails

The domain's website is unreachable, but the mail server still works. Common for internal systems and companies that run email without a public website.

Very small count. No action needed.

Unverifiable Inbox928 emails

Our validation engine could not confirm these one way or the other. The receiving mail server timed out, rate-limited us, or returned an ambiguous response. Common for legacy ISPs, university domains (.edu, .ac.uk), and corporate SMTP servers with strict anti-validation policies.

Credits for these 928 addresses were returned to your balance. We only charge for validated results, not for unknowns. Send normally during steady-state. During warmup, exclude them. You do not want unknowns in your initial sends.

Top Domains

#	Domain	Emails	Provider	Breakdown
1	gmail.com	38,000	Google	54% keep · 26% mon · 20% sup
2	yahoo.com	12,000	Yahoo family	36% keep · 30% mon · 34% sup
3	outlook.com	9,000	Microsoft	47% keep · 28% mon · 25% sup
4	hotmail.com	6,500	Microsoft	39% keep · 32% mon · 29% sup
5	aol.com	3,500	Yahoo family	31% keep · 36% mon · 33% sup
6	icloud.com	3,500	Apple	62% keep · 22% mon · 16% sup
7	comcast.net	2,000	Comcast/Xfinity	35% keep · 38% mon · 27% sup
8	live.com	4,000	Microsoft	47% keep · 28% mon · 25% sup
9	sbcglobal.net	1,200	Yahoo family	29% keep · 40% mon · 31% sup
10	driftwoodprovisions.com	847	Google Workspace	71% keep · 19% mon · 10% sup
11	protonmail.com	1,200	ProtonMail	65% keep · 22% mon · 13% sup
12	me.com	1,500	Apple	46% keep · 32% mon · 22% sup
13	earthlink.net	800	Yahoo family (Legacy)	22% keep · 45% mon · 33% sup
14	coastalwholesale.com	143	Other	69% keep · 22% mon · 9% sup
15	att.net	700	Yahoo family	30% keep · 40% mon · 30% sup

⚠

coastalwholesale.com, 143 emails.That is a lot of addresses from a single non-consumer domain. For most B2B contacts, you would expect a handful per company at most. Could be a legitimate enterprise customer with a large team, or it could be from a scraped or contaminated source. Worth checking on your side whether this concentration matches a real account relationship.

Most business domains in a typical subscriber list have 3–8 emails. Domains with unusually high counts are flagged above.

Per-domain numbers can differ from the parent provider's overall numbers. gmail.com (consumer) behaves differently than Google Workspace (business), even though both bucket under "Google."

Top Providers

Provider	Emails	Keep	Monitor	Suppress	Breakdown
Google	50,000	51%	27%	22%	51% keep · 27% mon · 22% sup
Microsoft	23,000	47%	28%	25%	47% keep · 28% mon · 25% sup
Yahoo family	18,000	36%	30%	34%	36% keep · 30% mon · 34% sup
Apple	5,500	58%	24%	18%	58% keep · 24% mon · 18% sup
Comcast/Xfinity	2,500	35%	37%	28%	35% keep · 37% mon · 28% sup
ProtonMail	1,200	65%	22%	13%	65% keep · 22% mon · 13% sup
Other	3,047	47%	28%	25%	47% keep · 28% mon · 25% sup

Warmup Plan

Every daily send is a proportional mix of your full sendable segment for that provider. We don't send the best contacts on Day 1 and the riskier ones on Day 9. That would mean your reputation gets worse as the warmup progresses, which is exactly what you want to avoid. The mix stays consistent so reputation builds in the right direction from start to finish.

⚠

Skip the warmup at your own risk. If you have not sent in a while and try to push this list out in one go, expect Yahoo and Microsoft to throttle, defer, or silently drop a meaningful share of your sends. You may not even see bounces, just zero engagement, then weeks of repair work to get reputation back. Following the plan is much cheaper than recovering from skipping it.

Why 20 days? Your domain has not sent at meaningful volume in over six months. To mailbox providers, your sending pattern is effectively starting from scratch. A full ramp gives each provider time to register your sends as legitimate before volume scales up. Twenty days is the sweet spot for a list this size: long enough that providers do not see a volume spike on any given day, short enough that you are sending normally inside three weeks. Cut this short and Yahoo, in particular, will throttle or silently defer your mail until you have rebuilt reputation the slow way.

Email #1: Daily Schedule

· 20 days · click to collapse

Day-by-day plan for the first send. The Warmup_Day column in your delivered Keep and Monitor spreadsheets tells you exactly which addresses to send on which day.

Day	Volume	Stage	Cumulative
1	50	Seed Google	0%
2	100	Google doubles	0%
3	250	Microsoft joins	1%
4	500	Both doubling	1%
5	950	Yahoo family joins	2%
6	1,420	Other providers join	4%
7	2,040	Volume comes online	7%
8	2,680	Apple joins	10%
9	3,410	Building momentum	15%
10	4,150	Steady climb	20%
11	4,755	Google reaches plateau	26%
12	5,125	Mid-warmup, big providers steady	33%
13	5,465	Continued growth	40%
14	5,680	Comcast joins	47%
15	5,915	ProtonMail joins	55%
16	6,205	All seven providers active	63%
17	6,465	Approaching peak	71%
18	6,785	Near peak	80%
19	7,235	Final climb	89%
20	8,589	Final day, all providers finish	100%

View Email #1 per-provider matrix

Each column is one day, each row is one provider. Yahoo family(Yahoo + AOL + Verizon + AT&T/Yahoo + SBCGlobal) is combined because they all share the same Yahoo-operated MX backend and reputation system. Treating them separately would split the same sender-reputation pool into fake silos.

Provider	Vol	Day 1	Day 2	Day 3	Day 4	Day 5	Day 6	Day 7	Day 8	Day 9	Day 10	Day 11	Day 12	Day 13	Day 14	Day 15	Day 16	Day 17	Day 18	Day 19	Day 20
Google	39,000	50	100	200	400	700	1,000	1,400	1,800	2,200	2,600	2,855	2,855	2,855	2,855	2,855	2,855	2,855	2,855	2,855	2,855
Microsoft	17,250	·	·	50	100	200	300	400	500	700	900	1,100	1,300	1,450	1,450	1,450	1,450	1,450	1,450	1,450	1,550
Yahoo family	11,880	·	·	·	·	50	100	200	300	400	500	600	700	800	900	1,000	1,100	1,130	1,130	1,130	1,840
Apple	4,510	·	·	·	·	·	·	·	20	30	50	80	120	180	260	370	490	600	700	800	810
Other	2,285	·	·	·	·	·	20	40	60	80	100	120	150	180	200	200	200	200	200	200	335
Comcast/Xfinity	1,800	·	·	·	·	·	·	·	·	·	·	·	·	·	15	30	80	150	300	500	725
ProtonMail	1,044	·	·	·	·	·	·	·	·	·	·	·	·	·	·	10	30	80	150	300	474
Daily total		50	100	250	500	950	1,420	2,040	2,680	3,410	4,150	4,755	5,125	5,465	5,680	5,915	6,205	6,465	6,785	7,235	8,589

How the next sends compress

Each successful email builds reputation, so the calendar compresses with each campaign. We keep each provider's first send of the next email at or above where it ended in the previous email, so no provider sees a step-back in volume.

Email #1 (this warmup)

20 days. Cold-start ramp, each provider ends on Day 20.

Email #2

5 sends. Picks up where Email #1 left off, climbs gently.

Email #3

3 sends. Reputation is solid, compression continues.

Email #4

2 sends. Almost there.

Email #5+

Single send. Full list goes at once. Normal cadence.

Email #2 schedule· 5 sends · climbs from 7,700 to 23,110

Picks up where Email #1 left off. Each send is bigger than the last. Smaller providers join later sends to finish together.

Provider	Vol	Send 1	Send 2	Send 3	Send 4	Send 5
Google	39,000	3,000	5,500	8,000	10,500	12,000
Microsoft	17,250	1,600	2,500	3,500	4,500	5,150
Yahoo family	11,880	1,900	2,200	2,400	2,600	2,780
Apple	4,510	850	870	900	940	950
Other	2,285	350	400	450	500	585
Comcast/Xfinity	1,800	·	·	·	725	1,075
ProtonMail	1,044	·	·	·	474	570
Daily total		7,700	11,470	15,250	20,239	23,110

Email #3 schedule· 3 sends · climbs from 23,110 to 28,309

Reputation is solid. Three sends. Smaller providers (Comcast, ProtonMail) join at Send 2 to finish together.

Provider	Vol	Send 1	Send 2	Send 3
Google	39,000	12,000	13,500	13,500
Microsoft	17,250	5,150	5,900	6,200
Yahoo family	11,880	2,780	4,000	5,100
Apple	4,510	950	1,450	2,110
Other	2,285	585	750	950
Comcast/Xfinity	1,800	1,075	500	225
ProtonMail	1,044	570	250	224
Daily total		23,110	26,350	28,309

Email #4 schedule· 2 sends · 28,784 then 48,985

Just two sends. The next campaign after this one can go to the full list at once.

Provider	Vol	S1	S2
Google	39,000	13,500	25,500
Microsoft	17,250	6,200	11,050
Yahoo family	11,880	5,100	6,780
Apple	4,510	2,110	2,400
Other	2,285	950	1,335
Comcast/Xfinity	1,800	500	1,300
ProtonMail	1,044	424	620
Daily total		28,784	48,985

Email #5+ schedule· full list, single send

Steady state. Press send. Everyone gets it at once. This is your normal cadence going forward, no more ramp needed unless you add a new sending domain or ESP.

Provider	Vol	Full list
Google	39,000	39,000
Microsoft	17,250	17,250
Yahoo family	11,880	11,880
Apple	4,510	4,510
Other	2,285	2,285
Comcast/Xfinity	1,800	1,800
ProtonMail	1,044	1,044
Daily total		77,769

In your delivered spreadsheets: you will see four warmup columns, one per email. Warmup_Day_E1, Warmup_Day_E2, Warmup_Day_E3, Warmup_Day_E4. Each contact has an assigned day for each of the first four campaigns. Filter by the column for the campaign you are sending, hit send, done. Email #5+ has no column because it goes to the full list at once.

See the domain side too

This list cleaning report is paired with a domain authentication review for driftwoodprovisions.com. That report covers SPF, DMARC, DKIM, blocklist status, and sending infrastructure. The DNS layer that protects your sending reputation.

View domain insights report →

Yanna-Torry Aspraki

Deliverability Specialist, Review My Emails

Questions about your results? Want help building a warmup plan based on this data? I am happy to walk through it.

Get in touch →

reviewmyemails.com