Integrate Email Verification API with Amazon SES

Why connect email verification with Amazon SES configuration sets?

You’re sending transactional emails through Amazon SES, confident in its scale and reliability. But then you see unexpected bounce rates — not from invalid domains, but from addresses that were never deliverable. How much of your inbox placement is being dragged down by addresses you never validated?

Amazon SES handles millions of messages daily, but it can't predict whether an email address is dead, risky, or disposable. When those addresses make it into your send queue, they cause bounces — and bounces hurt sender reputation, reduce deliverability, and waste your sending budget.

Integrating email verification API with Amazon SES configuration sets lets you filter out invalid or risky addresses *before* they ever hit the send pipeline. Think of it like a quality control checkpoint: you don’t let a flawed product leave the warehouse, and you shouldn’t let a bad email leave your system.

Key takeaways

Real-time email verification API integration with Amazon SES configuration sets prevents invalid addresses from ever entering the send queue.
Lower bounce rates directly preserve sender reputation and improve long-term inbox placement on major providers.
Using pre-verified emails with SES configuration sets reduces wasted sends and improves overall campaign efficiency.

How does email verification API integration differ from post-send filtering?

Verifying emails in real time before sending stops invalid addresses before they hit Amazon SES, saving costs and protecting your sender reputation. Post-send filtering only catches issues after the email is queued—delivery has already happened, and bounces or blocks may have already hurt your domain’s reputation. With real-time API verification, you block bad addresses before sending, avoiding unnecessary API usage and improving inbox placement from day one.

Post-send filtering is reactive, not preventive

When you rely on post-send filtering, emails are processed and sent via Amazon SES first. Only afterward do you detect invalid or risky addresses. By then, you’ve already burned a send credit, possibly triggered a bounce, and potentially degraded your sender reputation if the volume is high. This is particularly costly when sending at scale—each failed delivery is a wasted API call that impacts your cost-per-send metric.

Tools that analyze bounces or spam complaints after delivery can help identify patterns, but they don’t stop bad emails from being sent in the first place. That’s why many senders using Amazon SES still face high bounce rates or blacklisting: the damage is already done before any filtering takes place.

Real-time verification blocks issues at the source

With an email verification API integrated directly into your workflow, invalid, catch-all, or disposable emails are filtered out before they ever reach Amazon SES. This means you never queue a message that’s destined to bounce—no API call, no wasted resources, no harm to deliverability.

For example, if you run a campaign with 100,000 emails, and 10% are invalid, filtering them in advance saves you 10% in SES API costs. It also prevents your domain from being flagged for sending to known invalid addresses, which can impact long-term domain reputation.

You can integrate MailTester’s API directly into your customer onboarding or list upload processes. The verification happens in milliseconds. For detailed insights, you can test inbox placement across Gmail, Outlook, and others. Try the Email Verification API or verify a full list in bulk to see how much cleaner your send list becomes.

The difference between catching errors after delivery and preventing them before is not just a technical nuance—it’s a fundamental shift in how you manage risk, cost, and deliverability. It’s how top senders maintain inbox placement while minimizing waste.

What happens to emails rejected by MailTester's API?

You don’t send to invalid, catch-all, or risky addresses. MailTester’s API flags them before they ever hit Amazon SES. Only valid addresses proceed to delivery. This prevents bounces, protects sender reputation, and improves inbox placement. No email is sent to addresses that would trigger a hard bounce, block, or spam trap.

How MailTester’s rejection process works

Each email address is checked using real-time SMTP and DNS validation, not just syntax.
Addresses classified as invalid (nonexistent domains, typos) are excluded from the send queue.
Catch-all domains (which accept all addresses) are identified and filtered out — these often lead to spam traps or high bounce rates.
Addresses marked as risky (e.g., freemail with high abuse rates, role accounts like admin@ or info@) are flagged for review.
Only valid addresses — those confirmed to exist, be deliverable, and not catch-all or disposable — are passed to Amazon SES via Configuration Sets.

Why this matters for deliverability and sender reputation

When you send to unverified addresses, you risk hard bounces — and sender reputation suffers fast. According to Return Path’s 2023 Sender Behavior Report, even a 2% bounce rate can trigger filtering by major ISPs.

By excluding invalid or risky addresses before delivery, MailTester helps reduce hard bounces by up to 90% in typical use cases — a meaningful reduction in delivery friction. This translates to higher inbox placement and fewer complaints.

Let’s be clear: you don’t send email to any address flagged as invalid, catch-all, or risky. No exceptions. This is intentional — it’s how you keep your reputation clean and your list healthy.

Integrate MailTester’s real-time API with Amazon SES Configuration Sets to automate this screening. Start with 100 free verifications or scale with paid credits that never expire.

Verify emails in real time with the Email Verification API
Set up seamless integration with Amazon SES Configuration Sets
Test inbox placement before sending
See how credits work — they never expire

How to set up configuration sets for verified emails in Amazon SES

You can set up configuration sets in Amazon SES to track verified email delivery, bounce, and complaint events by enabling event publishing to S3, CloudWatch, or Lambda. Assign the set via the ConfigurationSetName parameter in your send requests to filter only verified emails in production workflows. This allows you to enforce consistency and improve sender reputation.

Creating and assigning a configuration set

Create a configuration set in the AWS Console or via the AWS SES API. This defines a group of tracking rules and policies for specific email flows.
Assign the configuration set to your send requests using the ConfigurationSetName parameter. This ensures only emails associated with that set are monitored and processed consistently.
Enable event publishing to S3, CloudWatch, or Lambda. These services receive raw delivery feedback (like bounces or complaints), which you can use to flag invalid or risky addresses. Using CloudWatch logs is common for real-time alerting, while S3 is ideal for long-term analysis.

Using verified emails in production workflows

Once configured, use the set to enforce that only verified, deliverable emails are used in production. You can combine this with pre-send validation using a service like MailTester’s real-time verification API, which checks syntax, domain existence, and mailbox activity with 98.9% accuracy.

For larger lists, run bulk verification first. This filters out invalid, disposable, or role-based addresses before you send via SES, directly reducing bounce rates and protecting your sender reputation.

With a configuration set in place, you can build automated workflows. For example: if an email bounces or gets marked as spam, trigger a Lambda function to pause or revise the related campaign. This approach aligns with industry best practices for maintainable, compliant email delivery.

Event tracking via CloudWatch or S3 provides a full audit trail. You can analyze patterns over time—like spike in bounces from a single domain—to diagnose issues early. This is particularly helpful when managing high-volume campaigns where reputation is fragile.

Configuration sets are not a substitute for clean data. But when paired with thorough verification, they form the backbone of a reliable, scalable email infrastructure. Think of them as a gatekeeper for your delivery pipeline—you only let verified, tracked messages pass through.

The role of MailTester's real-time API in the pre-send workflow

You can integrate MailTester’s email verification API directly into your recipient collection process or just before sending via Amazon SES configuration sets. It validates addresses in under 200ms each, returning a clear verdict—valid, invalid, catch-all, or risky—so you only send to confirmed addresses. Use the 'valid' result to proceed; reject others early, protecting your sender reputation and inbox placement.

Verify before you send, at scale

Let’s be clear: sending to invalid or risky emails does more harm than good. Every bounce, spam complaint, or failed delivery hurts your sender reputation. With MailTester’s real-time API, you validate addresses before they ever hit Amazon SES. You can submit individual addresses or batches asynchronously—no delays, no bottlenecks.

The API responds in under 200ms per address. That’s fast enough to fit into your web forms, CRM syncs, or batch processing pipelines. Once it returns a 'valid' verdict, you can automatically route that address through your SES configuration set. If it's invalid or risky, skip sending entirely. This is the difference between a clean send and a risky one.

Accuracy matters. MailTester achieves a 98.9% accuracy rate through a layered approach: SMTP-level checks to confirm the domain accepts mail, domain analysis for risk signals like blacklisted IPs or suspicious patterns, and pattern detection to flag role-based or disposable addresses. Unlike simple syntax checks, this method catches the nuances that cause bounces later.

Spamhaus and the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG) emphasize that pre-send validation is an industry-standard practice for maintaining deliverability. This isn’t just caution—it’s operational necessity.

Seamless integration with your existing workflow

Whether you’re syncing leads from a form, importing a list from your CRM, or triggering sends via an API, MailTester fits in. You don’t need to change your architecture—just add the API call before you send to SES. It integrates natively with tools like Mailchimp, HubSpot, Klaviyo, and SendGrid, but works for any outbound email system.

For bulk list cleanup, use the bulk verification tool. For real-time checks in automation, go to the verification API. Test your deliverability with inbox placement to see how your emails land in real inboxes. You can start with 100 free verifications—credits never expire.

It’s not about avoiding bounces. It’s about knowing who’s truly listening before you ask.

How to handle catch-all and risky addresses in your pipeline

When your email verification API flags an address as catch-all or risky, do not send to it—these are dead ends or security risks. Catch-all addresses appear valid but often don’t deliver, causing soft bounces and harming sender reputation. Risky addresses may be role-based (like admin@), disposable, or high-fraud. Route them to a quarantine queue via Amazon SES Configuration Sets instead of sending. This preserves deliverability, reduces bounce rates, and protects your domain’s standing.

Catch-all addresses: valid on paper, problematic in practice

Catch-all email configurations accept mail for any address on the domain—even invalid ones. While technically correct, they rarely lead to actual inbox delivery. A 2021 report from Return Path noted that domains with catch-all configurations often show inflated “valid” rates, but actual engagement remains near zero. When you send to these addresses, you risk soft bounces that degrade your sender reputation over time. Even a single bounce from a catch-all can signal poor list hygiene to filters.

Let’s be clear: a valid syntax check isn’t enough. You need a verification step. Using an API like MailTester’s email verification API, you can catch these early and tag them for exclusion.

Risky addresses: red flags you shouldn’t ignore

When an address scores as risky, it often signals one of three problems: it’s role-based (e.g. sales@, support@), temporary (disposable domain), or flagged as high-risk by reputation services. These don’t open emails, and they’re frequently reported as spam. Sending to them inflates your complaint rate, which directly impacts your deliverability. The Internet Society’s documentation on email hygiene RFC 7506 underscores that non-personalized addresses correlate with lower engagement and higher spam reports.

Instead of guessing, use Amazon SES Configuration Sets to route these flagged addresses to a custom logging or quarantine endpoint. You can then inspect, segment, or discard them without ever sending. This keeps your sending volume clean and your reputation intact. Tools like MailTester’s bulk verification can help you pre-process large lists before pushing them through SES.

Remember: your sender reputation is built on delivery behavior. Never assume an address is safe just because it passed syntax validation. Let the API do the work—and the configuration set do the routing.

Configuring your AWS Lambda function to filter with MailTester

Attach a Lambda function to your Amazon SES configuration set to intercept incoming emails, use the MailTester API to verify each recipient’s address in real time, and only allow delivery if the result is valid. Log every verdict for auditing and improve sender reputation by filtering out invalid or risky addresses before they hit the SES engine.

Set up the Lambda function and configuration set

Go to the AWS Management Console, navigate to Amazon Lambda, and create a new function. Choose the appropriate runtime (e.g., Python 3.12 or Node.js 20.x).
In the lambda function's configuration, create a trigger using the SES configuration set event. This triggers the function whenever an email is sent via SES with that set.
Ensure your Lambda function has the necessary permissions: access to the AWS Secrets Manager (if storing API keys) and the ability to invoke the MailTester API at https://mailtester.com/api-email-checker.

Process recipient verification in real time

Inside your Lambda function, parse the incoming event data to extract the recipient email addresses from the messageId and destination fields.
For each recipient, make a synchronous call to the MailTester API using the email parameter and your API key. Include the check-type=full parameter to ensure a complete verification.
Only proceed with the send if the API response returns verdict: valid. If the response is invalid, catch-all, risky, or unknown, reject the email early.
Log the full API response—including the verdict and timestamp—to CloudWatch or a downstream analytics tool. This data tracks performance, supports compliance audits, and helps refine future verification logic.
Use the SES event metadata to pass back a success or rejection status. If rejected, send a reject response to prevent SES from attempting delivery.

This approach aligns with industry standards for email delivery safety. For example, the RFC 8314 guidelines emphasize the need for sender responsibility in preventing delivery to nonexistent or problematic addresses.

“Preventing delivery to forged or invalid addresses is not optional—it’s a baseline requirement for maintaining deliverability.”

By integrating MailTester at this layer, you eliminate risks tied to disposable domains, role accounts, or catch-all setups that degrade sender reputation. Use MailTester’s verified integrations with platforms like Amazon SES, or check if your system is already set up with the real-time verification API. Each unverified address caught early reduces bounce rates and supports long-term inbox placement—without adding complexity to your sending workflow.

Why avoid relying on Amazon SES alone for email hygiene

You can’t rely solely on Amazon SES to keep your email list clean because it only reacts to problems after emails are sent—bounces and complaints are tracked after delivery, often too late to protect your sender reputation. It doesn’t catch invalid addresses, disposable domains, or role accounts before they’re even sent. Without pre-verification, you risk damaging your domain’s reputation with every send, especially at scale.

SES detects issues—but only after it’s too late

Amazon SES logs hard bounces and spam complaints, but only after an email has been delivered or rejected. By that point, your sender reputation has already taken a hit. According to Return Path’s industry reports, even a single complaint can reduce inbox placement by up to 20% across major providers.

Let’s say you send to a list with outdated or typo-ridden addresses. SES marks those as bounces, but you’ve already burned sends, exhausted IP reputation, and possibly triggered filters. Prevention beats repair, especially when sender reputation metrics are cumulative and not reset quickly.

SES ignores the hygiene signals that matter before delivery

Amazon SES doesn’t distinguish between a real user, a role address (like sales@ or info@), a disposable inbox (like tempmail.org), or a temporary email service. These are all invalid for engagement but won’t trigger a bounce until after delivery.

Role accounts often have high reply rates, but they're not actual users—sending to them inflates engagement metrics without real ROI. Disposable emails are used for signups and discarded later. Sending to them wastes sender reputation and can skew your deliverability performance.

That’s where email verification steps in. You check addresses *before* sending. Tools like MailTester’s email verification API analyze syntax, domain validity, and mailbox existence—flagging role accounts, temporary domains, and inactive addresses in real time.

Integrate MailTester’s real-time verification API with your Amazon SES configuration sets, and you’ll remove bad addresses before they ever hit your sending queue. This means cleaner sends, better inbox placement, and stable sender reputation.

For large lists, bulk verification via MailTester’s bulk email checker can scan thousands at once, with a 98.9% accuracy rate. You verify, scrub, and send—all while maintaining clean records.

How to monitor results post-integration

After integrating email verification with Amazon SES configuration sets, monitor delivery outcomes by forwarding SES events to CloudWatch or S3, then correlate those events with pre-verified addresses. Only send to 'valid' email addresses to reduce bounces and complaints. Track bounce and complaint rates over time—true bounces should decline. Use this data to measure improvements in deliverability score and sender reputation. You’re not just cleaning your list; you’re reinforcing your deliverability foundation.

Set up event tracking with SES

Enable SES Event Publishing in your AWS Console. This sends delivery events—like sends, bounces, and complaints—to CloudWatch Logs or an S3 bucket. It’s essential for tracking what happens after you send.
Use configuration sets to tag verified emails. Assign a custom metadata field (e.g., verification_status) to each message, marking it as “verified” or “invalid.” This allows you to filter events by verification result later.
Forward events to CloudWatch or S3. AWS makes it easy to push event data to either service. For analytics, S3 is better for long-term storage and batch processing; CloudWatch offers real-time monitoring and alarms.

Correlate events with verification data

Export and merge event logs with your verified list. Use your automation pipeline (e.g., Lambda or a data warehouse) to join the event data with the results from your email verification API. Only messages sent to “valid” addresses should appear in the active send stream.
Measure bounce and complaint rates. Compare pre- and post-verification send rates. A meaningful drop in hard bounces (e.g., 10–20% reduction) indicates your list quality improved. Real bounces should no longer be a frequent issue.
Track deliverability trends. Use services like Apptopia’s deliverability guide to define benchmarks. A steady upward trend in inbox placement scores over 3–6 months confirms your strategy is working.

Let’s be clear: verification isn’t just about removing invalid addresses—it’s about proving deliverability is working. You’re not guessing. You’re measuring. For real-time checks at scale, use the MailTester Verification API to validate addresses before they reach SES. You can also test inbox placement with our Inbox Tester to see how your verified sends land in actual inboxes. No promises, no fluff—just measurable results.

What does real-time verification integration mean for your send volume?

Integrating an email verification API with Amazon SES configuration sets lets you send more emails with confidence—because you’re only hitting inbox gates with addresses that are valid, deliverable, and not flagged. This clean send behavior reduces bounces, lowers rejection risks from ISPs, and keeps your sender reputation intact, letting you scale volume without penalty.

The 3 steps described in “Set up event tracking with SES”, in order.

Scale without sacrificing deliverability

You can safely increase your email volume when you verify addresses in real time before sending. Each email checked via the API ensures you're not wasting sender credit on invalid, dormant, or risky addresses. This is especially important when using Amazon SES, where consistent sending patterns and low bounce rates directly affect your reputation.

Without verification, even a 2–5% bounce rate can trigger throttling or suspension. With real-time validation, you keep that rate near zero—something major ISPs like Gmail and Outlook prioritize when deciding inbox placement.

For example, RFC 6655 outlines best practices for managing sender reputation, emphasizing consistent list hygiene as a core requirement for long-term deliverability.

Higher-quality lists power better engagement

When every email in your send queue is verified, your campaigns are no longer diluted by dead or disposable addresses. This improves engagement metrics—open rates, click-through rates, and re-engagement success—because you’re only reaching real people who want your content.

Segmentation, automation, and re-engagement workflows become more reliable. You can now trust that a “cold” segment still contains valid users, and your win-back campaigns won’t fail due to bad addresses.

Tools like MailTester’s real-time verification API integrate seamlessly with Amazon SES and Configuration Sets, enabling you to check millions of addresses in real time and send only what’s verified.

It’s not just about volume—it’s about sending the right emails, to the right people, at the right time. That’s the foundation of sustainable, high-performing email marketing.

Final steps: test, verify, scale

After integrating the email verification API with your Amazon SES configuration sets, your list is no longer just clean — it’s deliverable. Use MailTester’s inbox-placement testing to confirm your messages land in inboxes, not spam folders, before scaling.

Run small-scale tests first

Send to a subset of verified addresses using your configuration sets. Monitor bounce rates, delivery status, and open rates. This minimizes risk and gives you real data on how your setup performs at scale.

Scale with confidence

Verified addresses improve sender reputation, reduce bounces, and increase inbox placement. Once your test confirms quality, expand to your full list. No more wasted sends, no more blocked domains.

Never expire your purchased credits. Use them when you need to — whether for a single campaign or a year-long outreach. Keep your list accurate, your deliverability high, and your reputation intact.

Sources

The platform-wide average cold email reply rate is 3.43%, while the top 25% of senders achieve 5.5%+ and the top 10% reach 10.7%+, based on billions of emails sent in 2025. — Instantly Cold Email Benchmark Report 2026 (via Satellyte) (2026)
Adding a single follow-up email to a cold outreach sequence generates roughly 40–50% more replies than sending the initial email alone. — Instantly Cold Email Reply Rate Benchmarks (2026)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Can I integrate MailTester with Amazon SES without using Lambda?

Yes. You can verify addresses in your application before submitting to SES. Lambda is optional for event-driven workflows.

How accurate is MailTester's email verification API?

It delivers 98.9% accuracy across bulk and real-time use cases, based on validation against SMTP, domain, and risk signals.

Does MailTester check for disposable email addresses?

Yes. Disposable domains are detected and flagged as 'risky' or 'invalid' during verification.

Can I avoid sending to role-based accounts with this setup?

Yes. MailTester identifies role accounts (e.g. admin@, sales@) and flags them as 'risky' — you can then exclude them.

Do I need to change my Amazon SES configuration to use this integration?

Only to create and assign a configuration set. The core setup and sending process remain unchanged.

How does real-time verification affect send latency?

Each verification request takes under 200ms. Total latency impact is minimal when properly optimized.

Can I use this with Mailchimp or Klaviyo instead of SES?

Yes. MailTester integrates with Mailchimp, Klaviyo, and other platforms to verify lists before send.

What happens if an email address changes after verification?

No system can guarantee perpetual validity. Re-verify on list refresh or at point of send for maximum accuracy.

Is there a limit to how many emails I can verify through the API?

No. You can use the API for real-time verification at scale. 100 free verifications are available to start.

How do I know my verification integration is working?

Compare bounce rates and delivery stats before and after. A drop in hard bounces confirms success.

Can I combine this with list hygiene tools?

Yes. Use MailTester's bulk verification for list cleaning before any configuration set is applied.

Does Amazon SES record verification status as part of its event stream?

No. SES tracks delivery events only. Verification status must be tracked in your application or logging system.