Independent research. A clearer software perspective.
Business SoftwareConsensus Index

PROVIDER FIT REVIEWMarketing Automation & Email Marketing Software

Amazon SES Review: High-Volume Email Deliverability

Amazon SES is evaluated for high-volume email deliverability, covering buyer fit, pricing, strengths, limitations, and purchase considerations.

STUDY SNAPSHOTRecorded recommendations · not product testing
Research date
October 2, 2026
Usable AI responses
7
Consensus position
#4
Source URLs in evidence
42

RECOMMENDATION COVERAGE

Amazon SES

Recommended by 3 of 7 AI platforms in this study.

42.9%Consensus coverage · not a customer rating

The research in brief

Amazon SES is a good fit for a technically capable company sending more than 500,000 marketing emails per month, provided it can operate authentication, list hygiene, reputation monitoring, warming, and suppression workflows in-house. Three of seven platforms named Amazon SES during the ranking stage, with an average listed rank of 4.0 and a best rank of 3. The strongest reason to consider it is low-cost, high-throughput sending infrastructure with dedicated IP options and 2026 deliverability monitoring improvements. The main limitation is that SES is infrastructure, not a turnkey deliverability solution: it offers no inbox-placement guarantee, no native list validation, and no included human deliverability consulting.

Research Snapshot

FieldFinding
Platform mentions in ranking stage3 of 7 platforms (DeepSeek, Gemini, Grok)
Share of included platform responses42.9%
Average listed rank4.0
Best listed rank3
Software offeringAmazon SES with production access and dedicated IPs (managed or standard), plus Virtual Deliverability Manager
Overall use-case fitGood for technical high-volume senders; mixed for teams needing managed deliverability
Research date2026-10-02

Why Amazon SES Qualified for This Study

Questions explored

  • Is Amazon SES a good choice for high-volume email deliverability at 500,000 or more emails per month?
  • Why did AI platforms include Amazon SES in a high-volume email deliverability ranking?

Amazon SES qualified because it meets the study's core criteria as sending infrastructure: dedicated IP availability, sender reputation monitoring, suppression tooling, and adjustable high-volume quotas. Three of seven platforms named it during ranking discovery, and all seven platforms evaluated its fit for this use case. Its fit ratings split four "good" (ChatGPT, Claude, DeepSeek, Perplexity) against three "mixed" (Gemini, Grok, Kimi), which reflects the central tension: strong infrastructure, weak managed services.

The category criteria for this study were inbox placement track record, dedicated IP availability, sender reputation monitoring, list hygiene tools, and ISP relationship strength. SES scores clearly on dedicated IPs and reputation monitoring, partially on list hygiene, and weakly on independently verified placement track records and disclosed ISP relationships. That profile is why it qualified as a finalist but did not rank first.

The software offering in focus

Questions explored

  • Which Amazon SES configuration should a buyer choose for sending 500,000 marketing emails per month?
  • Is Amazon SES with managed dedicated IPs better than standard dedicated IPs for a high-volume sender?

The relevant configuration is Amazon SES with production access plus dedicated IPs, preferably Dedicated IPs (managed), with Virtual Deliverability Manager enabled. Every platform that named a plan pointed to dedicated IPs and production access at high volume [8].

SES offers two dedicated IP forms. Dedicated IPs (standard) are manually configured and warmed, while Dedicated IPs (managed) warm automatically by ISP and scale dynamically with sending patterns; both isolate the sender's reputation from the shared pool [8]. Managed dedicated IPs automate warm-up and optimize sending schedules per ISP [8]. Standard dedicated IPs have an additional monthly fee and no minimum commitment [7].

Production access is a prerequisite. New accounts begin in a regional sandbox limited to verified recipients, 200 messages per 24 hours, and 1 message per second, and the buyer must request production access and may need separate quota increases per Region [12]. Sending quotas and rates are regional, adjustable, and subject to account-specific limits [10].

What the AI Platforms Agreed About

Questions explored

  • What do AI platforms agree Amazon SES does well for high-volume email deliverability?
  • Does Amazon SES provide dedicated IPs and sender reputation monitoring for large senders?

Platforms agreed unanimously on several points. All seven described SES as low-cost, high-throughput sending infrastructure suitable for large volumes. All seven identified dedicated IP options as the primary deliverability control. All seven flagged the operational burden as the main tradeoff.

On dedicated IPs, platforms converged: SES offers standard and managed dedicated IPs, both isolating reputation from the shared pool, with managed IPs automating warm-up and scaling [8]. On reputation monitoring, platforms agreed SES exposes account and configuration-set bounce and complaint metrics through the console, CloudWatch, and APIs, and that standard dedicated IP users can view Outlook SNDS data through CloudWatch [6].

On 2026 improvements, multiple platforms cited AWS's announcement of inbox-placement metrics, content testing, and blocklist monitoring for SES [1]. Platforms consistently framed these as monitoring and diagnostic capabilities, not a placement guarantee.

On cost, platforms agreed SES is materially cheaper per email than managed marketing platforms at high volume. One independent review estimated roughly $113 per month at 500,000 emails with one standard dedicated IP and Virtual Deliverability Manager enabled [29].

Where the AI Platforms Disagreed or Were Uncertain

Questions explored

  • Is Amazon SES's inbox placement track record independently verified for high-volume senders?
  • How much does an Amazon SES standard dedicated IP actually cost per month in 2026?

Fit ratings diverged. Four platforms rated SES a good fit (ChatGPT, Claude, DeepSeek, Perplexity) and three rated it mixed (Gemini, Grok, Kimi). The split tracks how much weight each platform placed on the buyer's declining-placement problem versus raw infrastructure capability.

Inbox placement evidence is the sharpest conflict. No authoritative public source reviewed provided an independent, comparable inbox-placement benchmark for Amazon SES versus competing providers (ChatGPT). One independent report cited 19% primary inbox placement for SES, varying by sender practices [34]. A company case study reported 99%+ inbox placement and a 97/100 reputation score after migrating to Amazon SES, but that is a company-owned case study, is undated in the supplied material, and reflects one sender's practices rather than typical results [3].

Dedicated IP pricing conflicts. Multiple 2026 sources cite $24.95 per month per standard dedicated IP [33], while one source updated August 2026 reports $100 per month for new standard dedicated IP allocations after a 2025 rate change [26]. Google's platform reported that official AWS documentation confirms $24.95 and characterized the $100 figure as a conflicting third-party claim [25]. Buyers should confirm the applicable rate in the AWS console before budgeting.

Virtual Deliverability Manager pricing also conflicts: one source reported $1.00 per 1,000 emails while others consistently reported $0.07 per 1,000 [38]. The $0.07 figure appears in multiple June 2026 sources and is the more current of the two.

ISP relationship strength is unresolved. AWS operates large shared sending infrastructure and provides ISP-oriented tools such as Outlook SNDS metrics and ISP-specific managed-IP warming, but public evidence reviewed does not establish a guaranteed preferential inbox-placement relationship with Gmail, Microsoft, Yahoo, or other ISPs [8]. One platform noted AWS documents abuse and complaint handling but does not publicly disclose direct ISP feedback-loop relationships or preferential placement arrangements [18].

Features for this workload

Questions explored

  • Does Amazon SES include list hygiene and suppression tools for high-volume senders?
  • What deliverability monitoring does Amazon SES provide through Virtual Deliverability Manager?

SES covers dedicated IPs, reputation monitoring, and suppression well, and covers list hygiene and placement guarantees poorly. The table below maps capabilities to the study's five criteria.

CriterionSES capabilityAssessment
Inbox placement track record
2026 sampled inbox-placement metrics, content testing, blocklist monitoring; no placement guarantee
Monitoring only, not a guarantee [1]
Dedicated IP availability
Standard (manual warm-up) and managed (auto warm-up, ISP-level scaling)
Strong [8]
Sender reputation monitoring
Account and configuration-set bounce/complaint metrics via console, CloudWatch, APIs; Outlook SNDS for standard dedicated IPs
Strong [6]
List hygiene tools
Suppression lists, bounce/complaint notifications, mailbox simulator; no native validation or deduplication
Partial [13]
ISP relationship strength
ISP-specific managed-IP warming and feedback loops; no disclosed preferential placement
Unclear [8]

On suppression, SES maintains three layers: global (automatic, uncontrollable), account-level (manual query, add, remove), and tenant-level isolation introduced June 2026 [15]. The account-level suppression list automatically captures hard bounces and complaints, preventing repeat sends [28]. SES does not include native email verification or list cleaning; external tools are required [38].

On authentication, Easy DKIM generates auto-rotating CNAME records, and custom MAIL FROM SPF/DMARC alignment is supported but requires manual setup [32]. The default SES setup uses the amazonses.com domain, which fails SPF/DMARC alignment until a custom MAIL FROM subdomain is configured [24]. SPF and DKIM alignment with DMARC is required for ISP trust and proper authentication [14].

On enforcement thresholds, AWS recommends a bounce rate below 5% and a complaint rate below 0.1%, and accounts pause at 10% bounce or 0.5% complaint [37]. One platform reported suspension thresholds at 5% bounce or 0.1% complaint with no built-in remediation workflow [29]. These figures conflict and should be confirmed with AWS directly.

Pricing, renewal terms, and ongoing costs

Questions explored

  • How much does Amazon SES cost per month for 500,000 emails, and are there setup or cancellation fees?
  • Does Amazon SES require a long-term contract or minimum commitment for high-volume sending?

SES uses pay-as-you-go pricing with no long-term contract required for the core service, plus optional dedicated IP and deliverability add-on fees. À-la-carte outbound email is listed at $0.10 per 1,000 emails, excluding applicable additional charges [4]. A 2026 Pro plan is listed at $0.22 per 1,000 emails for 0–10 million monthly emails plus $105 per account per Region per month [4]. One platform reported that new AWS SES accounts default to an Essentials plan priced at $0.16 per 1,000 emails, with the option to transition to à-la-carte rates [31].

Cost componentListed priceSource
À-la-carte outbound email
$0.10 per 1,000 emails
Pro plan
$0.22 per 1,000 emails (0–10M/month) + $105 per account per Region per month
Standard dedicated IP
$24.95 per IP per month (conflicting report: $100/month for new allocations)
Managed dedicated IP
$15 per account per month + $0.08 per 1,000 emails (0–10M), declining at higher tiers
Virtual Deliverability Manager
$0.07 per 1,000 emails (conflicting report: $1.00 per 1,000)
Attachment data transfer
$0.12 per GB

One independent estimate put all-in monthly cost at roughly $113 for 500,000 emails with one standard dedicated IP and Virtual Deliverability Manager enabled, and roughly $202 per month at 1 million emails [29]. Another independent estimate for 500,000 emails was $115–160 total [33]. These are third-party calculations, not AWS quotes.

On contract terms, AWS states that SES has no contract negotiations, upfront commitments, or mandatory service usage for à-la-carte pricing (ChatGPT). Standard dedicated IPs have no minimum commitment and can be relinquished through AWS Support [7]. Releasing and re-provisioning a dedicated IP resets reputation and warm-up (DeepSeek). Exact cancellation, plan-switching, and refund treatment for 2026 pricing plans should be confirmed in the AWS billing console or customer agreement (ChatGPT).

Additional costs may include separate AWS charges for attachment data, data transfer, CloudWatch, SNS, Lambda, validation, multi-Region sending, and other integrated services (ChatGPT). One platform noted AWS Support plans at $29–$100+ per month for technical support beyond basic [29].

Best Suited For

Questions explored

  • Who gets the most value from Amazon SES for high-volume email deliverability?
  • Is Amazon SES a good fit for a company already running infrastructure on AWS?

SES is best suited to technically mature, High-Volume Senders that will own their deliverability program. Platforms converged on this profile.

The strongest fit is a company sending 500,000 or more marketing emails per month with in-house email or deliverability engineering that can manage authentication, list hygiene, reputation operations, warming, monitoring, and suppression workflows (ChatGPT). One platform described the ideal buyer as a technical team at a SaaS company or enterprise sending 500,000 to 10 million or more marketing emails monthly with strong list hygiene and compliance resources (Claude).

A second strong fit is an organization already operating in AWS that wants integrated sending with Lambda, SNS, S3, and CloudWatch (Claude, DeepSeek). A third is a cost-sensitive sender with consistent volume that can justify warming and sustaining dedicated IP reputation (DeepSeek, Grok). One platform noted that senders on dedicated IPs must build and maintain their own sender reputation directly with ISPs [25].

Probably Not Best Suited For

Questions explored

  • Who should not choose Amazon SES for high-volume email deliverability?
  • Is Amazon SES a bad fit for a marketing team without email engineering resources?

SES is probably not the best choice for marketing teams seeking a turnkey platform, senders with irregular volume, or buyers expecting a placement guarantee. Platforms agreed on these exclusions.

Marketing teams seeking a turnkey campaign platform with built-in list management, content tooling, and deliverability services are a poor fit (ChatGPT). One platform noted SES requires moderate-to-high technical skills for API/SMTP integration and monitoring, versus low-to-moderate for managed ESPs [30]. Another stated that marketing teams cannot use SES without developer support (Claude).

Senders with highly irregular or unpredictable volume are also a poor fit, because shared IP pools perform better below consistent high daily volume and dedicated IPs require sustained sending to maintain reputation (Claude, Grok). Managed dedicated IPs may be removed and traffic may be routed through the shared pool when sending volume is insufficient [5].

Buyers expecting Amazon to provide a universal inbox-placement guarantee or fully managed ISP relationships should look elsewhere (ChatGPT). Cold, purchased, or poorly maintained lists are explicitly unsuitable (ChatGPT). Teams without AWS operational maturity or the ability to invest initial engineering time are also flagged as poor fits (Kimi).

When Another Option May Be Better

Questions explored

  • What is a better alternative to Amazon SES for a buyer who needs managed deliverability support?
  • When should a high-volume sender choose a managed ESP instead of Amazon SES?

A managed email service provider may be better when the buyer needs vendor-managed deliverability, built-in list hygiene, or rapid remediation. Platforms described several such scenarios.

Choose a managed email-marketing or email-delivery provider when the buyer lacks dedicated deliverability engineering resources (ChatGPT). Choose a platform with stronger campaign, segmentation, suppression, validation, and placement-testing workflows when operational simplicity matters more than lowest infrastructure cost (ChatGPT). Consider a provider with specialized deliverability consulting or managed reputation services when declining placement requires hands-on remediation rather than raw sending capacity (ChatGPT).

One platform recommended managed ESPs such as SendGrid, Mailgun, or Klaviyo for non-technical teams or those needing rapid deployment, noting SES configuration takes two to four weeks with IP warm-up (Claude). Another noted that if the buyer needs remediation support or rapid reputation recovery, a managed ESP with included deliverability services is likely better despite higher base cost (Kimi). A third recommended a provider with built-in list hygiene and inbox-placement testing in one platform rather than assembling components (DeepSeek).

Speed to remediation is a recurring theme. SES sandbox graduation and manual warm-up add weeks, which matters when placement is already declining (Kimi). One platform noted SES offers no grace period for compliance issues, unlike managed ESPs, and that reputation recovery stabilizes over 10–14 days minimum [41].

Questions to ask before choosing a provider

Questions explored

  • What should a buyer confirm with Amazon SES before committing to a high-volume sending contract?
  • Which Amazon SES quotas, IP allocations, and fees should be verified in the AWS console before purchase?

The following questions come from the platforms' own verification lists and should be resolved before committing.

  • What production daily quota and per-second sending rate will AWS approve for each required U.S. Region (ChatGPT)?
  • Will managed dedicated IPs remain allocated at the buyer's expected minimum and peak volume, and under what conditions will traffic use shared IPs (ChatGPT)?
  • How many dedicated IPs or IP pools are needed for the buyer's traffic pattern and marketing/transactional separation (ChatGPT, Claude)?
  • What is the exact current pricing for standard dedicated IPs, and does $24.95 or $100 per month apply to the buyer's account [26]?
  • What are the exact 2026 charges for the selected plan, managed-IP usage, Email Validation, Global Endpoints, CloudWatch, and data transfer (ChatGPT)?
  • Does Virtual Deliverability Manager provide sufficient mailbox-provider coverage and sampling for the buyer's target audience (ChatGPT)?
  • Which list-validation, suppression, segmentation, and campaign-management tools will be used alongside SES (ChatGPT)?
  • What authentication configuration is required for SPF, DKIM, DMARC, custom MAIL FROM, tracking domains, and alignment [32]?
  • What bounce, complaint, unsubscribe, engagement, and spam-trap thresholds will trigger AWS warnings, throttling, or suspension [37]?
  • Can the buyer obtain references or a controlled pilot showing placement at Gmail, Outlook, Yahoo, and other dominant recipient domains (ChatGPT)?
  • What support escalation and deliverability assistance are included in the selected AWS account or pricing plan (ChatGPT)?
  • What is the buyer's current list quality baseline, measured as hard bounce rate and complaint rate, before migrating (Claude)?
  • Does the buyer have a two-to-four-week timeline to implement SES, configure DNS, warm up IPs, and stabilize reputation (Claude)?
  • What is the buyer's realistic engineering bandwidth for initial setup plus ongoing SNS, Lambda, and CloudWatch pipeline maintenance (Kimi)?

The consensus assessment

Amazon SES is a good fit for a technically capable company sending more than 500,000 marketing emails per month that can operate its own deliverability program. Four of seven platforms rated it a good fit; three rated it mixed. The consensus strongest reason to choose it is low-cost, high-throughput infrastructure with dedicated IP options and 2026 deliverability monitoring improvements. The consensus main limitation is that SES is infrastructure, not a managed deliverability solution: no placement guarantee, no native list validation, no included human consulting, and approval-gated production access.

The verdict is conditional rather than universal. For a buyer already experiencing declining inbox placement without in-house deliverability expertise, the per-email savings may be consumed by deliverability incidents and external consultant fees (Kimi). For a buyer with AWS maturity, strong list quality, and consistent volume, SES delivers strong value and control (Claude, DeepSeek, Perplexity). AI-platform agreement on these points reflects shared reading of the same public documentation and does not prove product quality or placement outcomes.

How This Review Was Produced

This review was produced from seven AI-platform research responses collected for the high-volume email deliverability use case, using the research date 2026-10-02 as the study date. Each platform independently evaluated Amazon SES against the category criteria: inbox placement track record, dedicated IP availability, sender reputation monitoring, list hygiene tools, and ISP relationship strength. Three of seven platforms named Amazon SES during ranking discovery; all seven evaluated its fit. Fit ratings were four "good" and three "mixed." The article preserves platform-reported pricing, capability claims, and conflicts without resolving them by guessing. All citations are platform-reported evidence, not independently verified facts.

Research limitations

Several limitations apply. Platform-reported research dates differ from the authoritative run date: DeepSeek reported 2026-06-12 while the other six platforms reported 2026-10-02. Platform-reported dates are provenance metadata and do not independently prove freshness. Deepseek's response was produced with search disabled, so its claims require explicit verification before being described as current facts.

The supplied URLs were collected from platform responses and were not independently validated by the writer stage. Citations are platform-reported evidence, not independently verified facts. No authoritative public source reviewed provided an independent, comparable inbox-placement benchmark for Amazon SES versus competing providers. AWS's 2026 pricing page, announcement, and documentation describe newly introduced pricing plans and features; final account-specific pricing, feature availability, and regional eligibility should be confirmed in the AWS console. Public AWS materials describe inbox-placement metrics as based on representative industry samples and do not establish that the measurements equal the buyer's actual recipient-level inbox placement. The exact sending quota, sending rate, dedicated-IP allocation, and production-access outcome are account- and Region-specific. Dedicated IP pricing, Virtual Deliverability Manager pricing, and enforcement thresholds conflict across sources and remain unresolved. The supplied official website URL is an AWS SES control-page URL rather than the principal pricing or documentation page; assessment relied on linked AWS documentation and pricing sources.

Explore more marketing automation and email marketing software guidance in the category directory.

Sources

Company-Owned Sources

  1. Amazon SES now offers inbox placement metrics and blocklist monitoring: https://aws.amazon.com/about-aws/whats-new/2026/05/amazon-ses-global-deliverability/
  2. Requesting and relinquishing dedicated IP addresses: https://docs.aws.amazon.com/ses/latest/dg/dedicated-ip-case.html
  3. Sending test emails in Amazon SES with the simulator: https://docs.aws.amazon.com/ses/latest/dg/send-an-email-from-console.html
  4. Complying with DMARC authentication protocol in Amazon SES - Amazon Simple Email Service: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dmarc.html
  5. Using the Amazon SES account-level suppression list - Amazon Simple Email Service: https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html
  6. Amazon SES Virtual Deliverability Manager: https://docs.aws.amazon.com/ses/latest/dg/vdm.html
  7. Amazon SES Product Documentation / Developer Guide: https://docs.aws.amazon.com/ses/latest/dg/Welcome.html
  8. Official pricing and terms source: https://aws.amazon.com/pricing/?nc2=h_pr_hub
  9. Official pricing and terms source: https://aws.amazon.com/savingsplans/?nc2=h_pr_sp

Independent Sources

  1. AWS SES Monitoring: Delivery, Bounce, Complaint, and Reputation Metrics: https://cubeapm.com/faqs/aws-ses-monitoring-delivery-rates-bounce-metrics/
  2. Setup Amazon SES DMARC, DKIM, SPF Records for Domain Authentication: https://dmarcdkim.com/setup/amazon-ses-dmarc-dkim-spf-records
  3. Amazon SES Pricing: The Complete Cost Breakdown for 2026: https://emailplatformreview.com/amazon-ses-pricing/
  4. Amazon SES Dedicated IP Standard Cost Per Month in 2026: https://mailtester.com/blog/amazon-ses-dedicated-ip-cost-per-month/
  5. Amazon SES Review (2026): Trial Data + Verdict: https://powermtaproviders.com/providers/amazon-ses.html
  6. Amazon SES Cost in 2026: What You Really Pay at Scale: https://smtpedia.com/amazon-ses-guide/
  7. AWS SES Pricing Calculator & Cost Estimator: https://wraps.dev/tools/aws-ses-pricing-calculator
  8. Amazon SES: Complete DNS Configuration (DKIM, SPF, DMARC: https://www.captaindns.com/en/blog/amazon-ses-transactional-email-technical-guide
  9. Amazon SES Pricing Official 2026: Full Cost Breakdown: https://www.emailplatformreview.com/blog/amazon-ses-pricing-official-2026/
  10. Amazon SES Deliverability 2026: 19% Inbox Placement: https://www.inboxeagle.com/esp-insights/aws-ses/
  11. What Is Amazon SES? Setup Guide and Pricing: https://www.magicbell.com/blog/what-is-amazon-ses-guide
  12. Amazon SES Dedicated IP: When You Need One: https://www.mailblast.io/blog/ses/amazon-ses-dedicated-ip
  13. Amazon SES Deliverability Guide: Warm-Up, Bounces, and Reputation Management: https://www.mailblast.io/blog/ses/amazon-ses-deliverability
  14. Amazon SES for Email Marketing: Setup, Pricing & Best Tools (2026: https://www.mailblast.io/blog/ses/amazon-ses-email-marketing
  15. Amazon SES Spam Fix: Recover Inbox Placement with MailReach: https://www.mailreach.co/blog/amazon-ses-spam-how-to-fix-deliverability
  16. AWS SES Reputation Monitoring: Keeping Your Sending in Good Standing: https://www.vigilare.cloud/blog/aws-ses-reputation-monitoring/
  17. AWS SES review, pricing, and verified intelligence: https://www.zendikt.com/product/aws-ses

TRANSPARENCY BY DESIGN

The evidence behind this study

Research is a dated snapshot of AI recommendations and their supporting sources. Use the original evidence and methodology to understand what these findings can and cannot tell you.

Independent source records
20
Provider-owned source records
22
Direct support records
18

AI platforms in the study

ChatGPTClaudeDeepSeekGrokPerplexityKimiGemini

Study limitations

  • The study date identifies this research snapshot; dates reported by AI platforms do not independently establish source freshness.
  • Recommendation counts measure mentions during the ranking stage. Later fit assessments do not increase those counts.
  • Product names, costs, and features can differ across sources. Confirm conflicting details directly with the provider.
  • Source URLs came from AI platform responses and were not independently validated during report preparation.
  • Some dates reported by AI platforms differ from the study date. Those dates do not independently establish that the information is current.
  • Citations are platform-reported evidence, not independently verified facts. No-search model claims require explicit verification before being described as current facts.

Affiliate & commercial disclosure

We may receive compensation when you follow certain links, subscribe to a software plan, or take another qualifying action through a commercial partner. These relationships create a potential financial conflict, but do not influence recorded AI recommendations or ranking calculations. Partner availability, pricing, features, and service terms can vary.

Read the full Affiliate Disclosure for compensation, tracking, partner availability, and research independence details, or contact us with a disclosure question.

Verify the source snapshot

SHA-256: d1988c345727393dc594ec1e0023cf94e709ed068cbb76a67adb687a970e9417