How many addresses are on the Validity seed list?
Published 16 Jun 2026
Updated 23 Oct 2026
10 min read
Summarize with

Updated on 23 Oct 2026: We clarified the seed-count estimates, added complete-list testing requirements, and corrected the authentication checks.
Email Geeks reports from February 2026 put some Validity seed lists at roughly 370 addresses, with an anecdotal range of 300-450. These figures are not an official current total. The exact count depends on the account's selected monitoring regions and seed-list settings.
Treat 500 as an example of an internal planning allowance, not a Validity limit or a guaranteed ceiling. Size imports and campaign QA runs against the complete current list, even when it exceeds 500. A seed list is a controlled set of inboxes used to check where a message lands, but the count alone does not show whether real subscribers receive mail in the inbox.
Direct answer
Confirm the current account list before setting import limits or estimating test volume.
- Peer-reported estimate: About 370 seed addresses in those anecdotes.
- Reported range: Roughly 300-450 addresses in those reports, not a universal range.
- Planning allowance: 500 is an example, not a safe hard cap for every account.
- Exact count: Count unique addresses in the current account list, including reference addresses.
How to confirm the current seed count
In the Everest interface, go to In-Flight > Inbox Placement > Manage Seed List. Review the selected regions, then use Actions to download CSV or One Per Line. Count unique email addresses, excluding CSV headers and blank rows. Validity's seed-list instructions describe these export options.
Everest's inbox-placement capabilities are now part of Validity Engage. The Everest name remains in help articles and the API, so use the navigation available in your account. See Validity's product naming update for the current naming.
|
|
|
|---|---|---|
Peer snapshot | Anecdotal estimate | About 370 |
Peer-reported range | February 2026 reports | 300-450 |
Example allowance | Configurable, not a ceiling | 500 |
Exact account total | Count the current export or API response | All unique addresses |
Distinguish anecdotal counts from the current account total.
If the account has API access, request GET /api/2.0/inbox/seeds with its API key, then count the returned unique addresses. The Everest API documentation defines this as the full list for an account. Include reference addresses in the import total; placement-report denominators are a separate measurement.
Why the number changes
Seed lists are not static address books. A provider changes them when mailbox coverage changes, when a region is added, when an address stops behaving like a normal mailbox, or when a customer chooses a different monitoring footprint. Validity's account configuration includes region selection and seed-list optimization settings, so geography alone does not determine the active address set.
A brand sending only to the United States does not need the same seed mix as a global sender testing North America, Europe, Australia, and Asia-Pacific. B2B coverage also includes hosting and filtering providers. Check the actual list after changing regions or optimization settings.

Illustration of Validity Everest seed-list results with regional filters.
Fixed-count thinking
- Assumption: Every account has the same seed count.
- Risk: Imports fail when a customer has more addresses.
- Problem: Hard-coded logic hides regional variation.
- Result: Seed tests become noisy when counts change.
Regional-count thinking
- Assumption: The active count depends on regions and seed-list settings.
- Planning: Set import capacity above the current complete list and keep it configurable.
- Data: Store the actual imported count per test.
- Result: Reports handle provider changes cleanly.
Separate the maximum allowed seed count from the observed seed count. The maximum is a configurable product control that must accommodate the complete list. The observed count is a test-level attribute that belongs in reporting and QA notes.
Keep the full seed list in every test
The import count matters only if every required address receives the test. Validity's sending instructions require the complete list, including four account-specific reference addresses used to identify campaigns.
- Include all four account-specific reference addresses in the import count and recipient list.
- Send the complete configured list for each test. Do not truncate it to fit a 500-address limit.
- For A/B testing, send each variant to the full list instead of dividing the seeds between variants.
- Refresh stored addresses when the account list changes, and check that suppression rules have not excluded required seeds.
If results are missing, Validity's troubleshooting instructions recommend checking the full seed list and reference addresses, suppression rules, bounce logs, and whether processing has finished. Missing results alone do not prove a blocklist (blacklist) listing.
How to use the number in planning
For planning tasks, count the current list, leave configurable capacity above that total, and record the active count for each test. Validate upload format and duplicates separately; an arbitrary address cap does not identify a malformed upload.
Do not use the seed-list count as a quality signal. A 370-address list is not automatically better or worse than a 300-address list. The useful question is whether the seed mix covers the mailbox providers and regions that match the real audience.
Seed-list import settingstext
seed_address_limit_source=current_account_list_plus_headroom seed_address_limit_configurable=true store_actual_seed_count=true store_region_set=true deduplicate_addresses=true preserve_reference_addresses=true require_test_id=true
For a single diagnostic message before a full seed-list campaign, Suped's email tester can catch authentication, header, content, and DNS issues before a send to hundreds of seed inboxes. It does not measure placement across the seed list.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Use a simple sequence for campaign QA. Send one diagnostic message, check authentication and domain health, run the seed-list test, then compare the placement result with prior tests that used the same region set.
- Validate: Confirm email authentication passes before seed testing.
- Segment: Track the region set used in each seed campaign.
- Compare: Compare tests with similar content and the same sending IPs and domains, provider coverage, and reporting weights.
- Investigate: Treat sudden provider-specific drops as a reason to inspect authentication and reputation.
What seed lists can and cannot tell you
Seed lists are controlled inbox placement tests. They show how a specific message performed at monitored mailbox providers at a specific time. They do not measure subscriber engagement, personal inbox history, user-level filtering, or every local rule inside a mailbox provider. Inbox placement is separate from delivery acceptance: a message accepted by a mailbox server can still land in spam.
Treat seed results as one signal among several. If a seed test shows spam-folder placement at one provider, check authentication, recent volume changes, complaint indicators, and blocklist or blacklist status before changing the sending strategy.
Avoid seed-heavy warm-up sends
Seed inboxes do not produce normal subscriber engagement. During IP or domain warm-up, build reputation with opted-in, engaged recipients. If the full seed list would dominate a small send, postpone that test rather than sending a partial list.

Inbox placement testing alongside email authentication, sender reputation, and subscriber engagement.
Good for
- Placement: Checking whether test mail lands in inbox or spam.
- Provider view: Spotting differences across major mailbox providers.
- Pre-send QA: Catching problems before a campaign reaches subscribers.
- Regression checks: Comparing a campaign against a similar prior send.
Weak for
- Subscriber truth: Predicting every real inbox for every recipient.
- Engagement: Measuring opens, replies, clicks, complaints, and deletes.
- Root cause: Explaining why filtering happened without other data.
- Long trends: Showing reputation movement without stable test inputs.
For reputation checks, seed results should sit beside blocklist monitoring, DMARC reporting, and real engagement signals. A blocklist or blacklist listing is context, not proof of why a seed message was filtered. Check SMTP responses and provider-specific results before attributing a delivery failure to a listing.
To decide which lists matter, start with a practical overview of blocklists and then prioritize the important blocklists that affect the sending environment.
How seed list count relates to authentication
Seed-list size does not fix authentication. A larger seed list will not repair an SPF authorization error or broken DKIM signing. Under RFC 9989, a message passes DMARC when SPF or DKIM passes and the authenticated domain meets DMARC's matching requirements for the visible From domain. A p=none policy requests no DMARC enforcement; it does not turn a failed result into a pass.
Suped is our DMARC reporting and email authentication platform. Use Suped to review aggregate report sources, find SPF or DKIM domain-matching failures, and monitor authentication changes before interpreting a seed placement result. Aggregate reports help identify authentication problems; they do not show whether messages reached the inbox or spam folder.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
Before a full seed-list test, check the sending domain with a domain health check. Fix authentication failures first. Otherwise, the seed test measures a preventable configuration problem instead of isolating inbox placement.
Basic DMARC monitoring recorddns
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Do this before seed testing
Configure both SPF and DKIM for legitimate senders. For an individual message to pass DMARC, at least one must pass with the required domain match.
- SPF: Check the sending IP authorization and the MAIL FROM domain used for DMARC.
- DKIM: Check signature validation and whether the d= signing domain meets DMARC's matching requirements.
- DMARC: Verify the message result and review aggregate reports; a published record alone does not prove a pass.
- Reputation: Check domain and IP status when investigating placement problems.
Handling regional and provider coverage
The count matters less than the coverage. A seed list is useful when its providers and regions match the real audience. A larger list can still be weak if it adds irrelevant regions or misses mailbox providers that carry meaningful subscriber volume.
Separate volume questions from coverage questions when reviewing a seed-list plan. Volume asks how many seed messages will be sent. Coverage asks whether the seed list tests the places where the real audience receives mail.
|
|
|
|---|---|---|
Regions | Where? | Match audience |
Providers | Which? | Prioritize volume |
Cadence | When? | Keep stable |
Count | How many? | Verify current list |
Plan coverage against the real audience and keep test settings comparable.
A region change also changes trend interpretation. If last week's test used 320 seeds and this week's test used 372, part of any placement-rate change can come from the different list. Store both the count and selected regions next to every result. Also record optimization settings and reporting weights, because a weighted placement percentage is not simply the share of all seed addresses.
Practical rule
Make reporting depend on the actual seed list used in each test, with stable provider coverage and reporting weights. Store those settings so a configuration change is not mistaken for a change in inbox placement.
Views from the trenches
These Email Geeks reports are dated February 2026. They are anecdotal snapshots, not current measurements or official Validity limits. Use the current account list for operational counts.
Best practices
Size import capacity against the complete current list, with configurable room for changes.
Check both regions and optimization settings, because they determine the active seed list.
Separate seed placement data from authentication data before making deliverability fixes.
Keep seed testing cadence stable so count changes do not look like performance swings.
Common pitfalls
Assuming every customer has the same seed count leads to bad batching and list logic.
Using seed placement alone misses DMARC failures, blocklist hits, and real engagement.
Treating 500 as a fixed Validity limit can cause failures when account coverage changes.
Sending seeds with different content than campaigns produces clean but weak signals.
Expert tips
Refresh the account list before sizing imports, and preserve every required reference address.
Track region choices beside each test so a count change has a clear operational cause.
Pair seed testing with inbox authentication checks before changing sending patterns.
Review blocklist and blacklist status when seeds show sudden provider-specific drops.
Marketer view
Marketer from Email Geeks says a typical Validity seed list has been around 370 addresses, with the count increasing during the year.
2026-02-12 - Email Geeks
Marketer view
Marketer from Email Geeks says many seed lists they have seen sit around 300-450 addresses, so that range is useful for planning.
2026-02-13 - Email Geeks
Frequently asked questions
Email Geeks reports from February 2026 cite about 370 addresses and a 300-450 range. These are anecdotal snapshots, not an official current count. Count the complete current list in the account for an exact answer.
No. It is an example of a planning allowance, not a documented Validity ceiling. Set a configurable limit above the current complete list, and increase it when needed. Do not truncate the list to fit the limit.
Download the current seed list from Manage Seed List in the Everest interface, or use GET /api/2.0/inbox/seeds if the account has API access. Count unique addresses, including all four reference addresses, and exclude CSV headers and blank rows.
No. A larger seed list gives more observations, but relevant provider coverage and stable test inputs matter more. Real subscriber engagement is still needed to interpret deliverability.
Selected monitoring regions and seed-list optimization settings affect the active address set. Accounts testing business recipients also need relevant hosting and filtering provider coverage.
Check email authentication first. If it fails, seed testing shows placement symptoms without resolving the sending-domain problem.

